Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise is designing a hybrid network architecture to connect its on-premises data center to Google Cloud Virtual Private Cloud (VPC) networks. The organization has identified the following requirements and operational constraints:
Which connectivity solution should the enterprise choose?
Cross-Site Interconnect is a Cloud Interconnect feature designed to provide high-bandwidth, transparent Layer 2 transport between multiple external on-premises network sites across Google's global fiber backbone.
The goal was to connect multiple distributed on-premises data centers to each other across Google's global backbone without routing through intermediate VPCs.
Partner Interconnect provides private, enterprise-grade Layer 3 or Layer 2 connectivity between an on-premises network and Google Cloud Virtual Private Cloud (VPC) through a supported service provider. It allows organizations whose networks do not physically meet Google's network at a colocation facility to bridge the gap using the service provider's network.
Partner Interconnect satisfies both the physical constraint (absence from Google colocation facilities) and the bandwidth requirement (sub-10 Gbps) far more economically and operationally efficiently than Dedicated Interconnect.
Dedicated Interconnect provides direct, private physical connections between an organization's on-premises network and Google's network inside a supported Google colocation facility.
The enterprise already maintained physical network infrastructure in a supported Google colocation facility and required dedicated bandwidth exceeding 10 Gbps or 100 Gbps.
Google Distributed Cloud connected (formerly Google Distributed Cloud Edge) is a dedicated hardware deployment (rack or server) provided and maintained by Google or a certified partner that runs on-premises to host local Google Kubernetes Engine (GKE) clusters.
The primary requirement was running containerized GKE workloads locally on customer premises with strict data residency regulations or microsecond local processing needs.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated