Question-8: Epic is one of the most well-known and well-respected vendors of electronic health record (EHR) software, and it is extremely popular among large healthcare organizations. It gives medical practises access to a user-friendly patient portal, through which they are able to communicate information regarding prescriptions, appointment reminders, and any other notes related to a patient's visit. Please see the case study on EHR Healthcare for more information on this topic. It is necessary for you to establish the technological architecture for hybrid connection between the on-premises systems of the EHR and Google Cloud. It is important that you adhere to the best practises that Google suggests for production-level apps. What steps should you take, keeping in mind the business and technological needs of the EHR Healthcare system?
A. It is necessary to configure two different Partner Interconnect connections within the same metropolitan area (City), and you must also ensure that the Interconnect connections are located in separate metropolitan zones.
B. Set up two virtual private network connections (VPNs) between your on-premises network and Google Cloud, and make sure that the VPN devices on your network are housed in separate racks.
C. Direct Peering between EHR Healthcare and Google Cloud needs to be configured, and you must ensure that you are peering with at least two different Google locations.
D. You need to configure two Dedicated Interconnect connections in one metro (City) and two connections in another metro. Additionally, you need to make sure that the Interconnect connections are located in different metro zones.
Correct Answer
Get All 340 Questions and Answer for Google Professional Cloud Architect
: 4 Explanation: According to the need of a safe and high-performance link between the systems running on-premises and those running in Google Cloud. Direct Connect EHR has the potential to achieve bandwidths ranging from 10 GBS to 100 GBS, making it an attractive alternative to VPN in scenarios where data must go over the internet and where bandwidth is a concern. Direct Peering is more often used for Workspace than it is for Google Cloud). The following are the business requirements for this scenario: Ensure that all customer-facing systems are available for at least 99.9% of the time. Ensure that a secure and high-performance connection can be established between on-premises systems and Google Cloud. Option 1: Constructs for us a partner connection with a 99.9% service level agreement, meeting all of our organization's needs. Option 2: The business needs do not lend themselves well to the use of a virtual private network. Option 3: Direct peering is utilized for the workspace rather than a DMZ, which is, once again, not an appropriate solution. Option 4: Constructs for us a dedicated connection that has a 99.99% service level agreement and meets all of our company's needs. The question that asks, You wish to follow Google's recommended practices for production-level apps, contains the information you need to determine whether you should go with Option 1 or Option 4. For production-level applications, Google suggests using the 99.99% SLA connection (dedicated or partner), as indicated here: