
Explanation:
The question requires following Google's recommended practices for production-level applications. Based on the community discussion and Google documentation, option D is the correct choice because it implements the production-level topology with four Dedicated Interconnect connections across two metros in different metro zones, providing 99.99% availability, which exceeds the minimum 99.9% requirement and ensures high performance and redundancy. Option A (Partner Interconnect) only provides 99.9% availability and is suitable for non-critical applications, not production-level. Option B (VPN) is insecure and insufficient for high-performance needs due to internet-based traffic. Option C (Direct Peering) is intended for Google Workspace, not Google Cloud connectivity. The consensus in the discussion, supported by upvoted comments and references to Google's best practices, confirms D as optimal.
Ultimate access to all questions.
As a certified Google Professional Cloud Architect designing a hybrid connectivity solution for EHR Healthcare's on-premises systems to Google Cloud, following recommended practices for a production-level application, what is the appropriate technical architecture?
A
Configure two Partner Interconnect connections in one metro (City), and make sure the Interconnect connections are placed in different metro zones.
B
Configure two VPN connections from on-premises to Google Cloud, and make sure the VPN devices on-premises are in separate racks.
C
Configure Direct Peering between EHR Healthcare and Google Cloud, and make sure you are peering at least two Google locations.
D
Configure two Dedicated Interconnect connections in one metro (City) and two connections in another metro, and make sure the Interconnect connections are placed in different metro zones.
No comments yet.