Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization is deploying a mission-critical multicloud application spanning Google Cloud (us-east4 and us-central1) and Microsoft Azure. You must provision dedicated physical Cross-Cloud Interconnect links using the gcloud CLI to meet these requirements:
How should you evaluate locations and provision the physical Cross-Cloud Interconnect ports?
zone1 of the first metro and one in zone2 of the second metro—using Google Cloud's remote location names, and obtain Google-issued LOA-CFAs to submit to Azure.This option deploys only two 100-Gbps Cross-Cloud Interconnect ports total, placing a single link in one metro (zone1) and a single link in a second metro (zone2), while attempting to use a Google-generated LOA-CFA to coordinate physical cabling with Microsoft Azure.
zone1 and zone2) in each of two separate metropolitan areas. Having only one link per metro fails to meet even the 99.9% SLA criteria.zone1 and zone2 only within the same metropolitan area. Maintenance windows are not coordinated across different metros, meaning zone1 in Metro A and zone2 in Metro B can undergo simultaneous maintenance, causing a total outage.zone1 + zone2); 99.99% multi-region SLA requires at least four connections across two metros.zone1, zone2) provide maintenance isolation strictly within a single metro boundary.This approach would still not qualify for an SLA with only two cross-metro ports; it would need to expand to four ports (two per metro across zone1 and zone2) and reverse the LOA direction so that Azure-issued LOAs are sent to Google.
zone1 in two different colocation facilities per metro, using Azure's ExpressRoute peering location names in your gcloud commands.This approach attempts to build a four-port, multi-metro Cross-Cloud Interconnect topology using 400-Gbps physical circuits and facility-level diversity within a single edge availability domain (zone1), while referencing Microsoft Azure peering location names directly in Google Cloud commands.
zone1 across two different colocation facilities within the same metropolitan area places both links in the same edge availability domain. Because Google Cloud schedules maintenance per edge availability domain rather than per physical building, both connections in that metro can experience simultaneous planned downtime.gcloud compute interconnects remote-locations list), rather than Azure's internal ExpressRoute location name.zone1 and zone2, which are never scheduled for maintenance simultaneously.gcloud CLI requires explicit selection of both zone1 and zone2 locations.This topology would only be valid if the target provider were AWS or OCI (supporting 400-Gbps ports), each metro paired zone1 with zone2 instead of using zone1 twice, and Google Cloud's remote location identifiers were supplied.
us-east4 workloads (one in zone1 and one in zone2), then deploy your own physical routers in the colocation facility to bridge the links to Azure ExpressRoute.This option combines a single-metro two-port topology with customer-managed physical routing equipment inside a colocation facility, which blends concepts from Cross-Cloud Interconnect and Dedicated Interconnect through a common Point of Presence (PoP).
zone1 and zone2) in a single metropolitan area only satisfies the 99.9% (non-critical production) SLA, leaving workloads vulnerable to regional or metro-wide disruptions. Achieving 99.99% multi-region availability across us-east4 and us-central1 requires four connections distributed as pairs across two separate metropolitan areas.us-east4 leaves us-central1 dependent on cross-region backbone transit without regional interconnect redundancy.This configuration would be appropriate (without deploying customer routers) only if the organization could tolerate a 99.9% availability SLA for non-critical workloads in a single region, or if the organization intentionally chose Dedicated Interconnect over Cross-Cloud Interconnect to bridge existing colocation equipment to multiple clouds and an on-premises network.
zone1 and zone2 edge availability domains in each metro and Google Cloud's remote location names, then submit the Azure-issued LOAs to Google.Cross-Cloud Interconnect provides dedicated, high-bandwidth physical connections provisioned directly by Google between the Google Cloud network and supported external cloud service providers (CSPs) such as Microsoft Azure. By placing redundant port pairs across multiple metropolitan areas and pairing them with matching CSP ports, organizations establish private, low-latency multicloud connectivity without deploying colocation hardware.
us-east4 and us-central1) and global dynamic routing.zone1 and zone2 edge availability domains within each metro via the gcloud CLI guarantees that Google Cloud will never take both links in a metropolitan area offline for scheduled maintenance at the same time.us-east4 and us-central1 regions using gcloud compute interconnects remote-locations list.zone1 and one port in zone2 for each of the two selected metros.Unlike a single-metro two-port design (which only delivers a 99.9% SLA), two-port cross-metro designs (which fail SLA rules due to uncoordinated cross-metro maintenance), or managing routers in a colocation facility, this four-port dual-metro topology maximizes availability, throughput, and operational simplicity.
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