Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A retail company is deploying a new e-commerce application on Google Cloud for customers located within a single geographic area. The architecture team has established the following availability and performance requirements:
Which infrastructure strategy should the company implement to meet these requirements?
A single-zone deployment places all compute and storage resources within one zone inside a region, providing ultra-low latency and high bandwidth between compute nodes without cross-zone traffic. Standard Tier networking is a network service tier that routes user traffic over the public internet via third-party transit internet service providers (ISPs) rather than Google's private global network.
This approach would be appropriate if the company were building a non-critical development and testing environment or running batch computing workloads that require high-bandwidth, low-latency connections between compute nodes and can tolerate downtime during a zone outage.
While bandwidth measures the maximum volume of data transferred over a connection in a given time, high intra-zone bandwidth between backend servers does not reduce the external network latency experienced by end users connecting over the internet.
Points of Presence (POPs) and network edge locations are specialized peering and caching facilities where Google's network interconnects with external internet service providers (ISPs) and where Cloud CDN caches content. A zone is a specific deployment area within a Google Cloud region where foundational infrastructure resources like Compute Engine virtual machines (VMs) are provisioned.
There is no scenario where Compute Engine virtual machines are deployed inside edge POPs, nor where a single-zone deployment protects against zonal failure. However, leveraging POPs as an entry point to route traffic to a regional managed instance group (MIG) with regional storage backups would be a valid architecture.
A common misconception is treating network edge data centers (POPs) and regions as interchangeable compute locations. In Google Cloud's hierarchy, user requests enter at an edge POP, travel across Google's private network, and are processed by VMs residing in a zone within a region.
In Google Cloud, a region is an independent geographic area composed of three or more zones, where each zone acts as an isolated single failure domain. Points of Presence (POPs) are network edge locations distributed globally where end-user traffic first enters Google's private network, allowing services like Cloud Load Balancing and Cloud CDN to handle requests close to the user.
Compared to single-zone or multi-region architectures, a single-region, multi-zone deployment paired with edge caching strikes the ideal balance between resilience, performance, and simplicity. It satisfies high availability requirements within a geographic area while leveraging network edge locations to minimize latency for end users.
A multi-region deployment distributes both the application frontend and backend across multiple independent geographic regions. This architecture allows every region to process user requests locally, providing low region latency for a globally dispersed user base and resilience against the loss of an entire region.
A multi-region frontend and backend deployment would be the right choice if the company were launching a mission-critical global application—such as a real-time multiplayer game—that requires survival during an entire regional disaster and local database reads across continents using a globally distributed database like Spanner.
Even for applications with high performance demands, single-region deployments combined with Cloud Load Balancing and Cloud CDN are often preferred over multi-region architectures because edge optimizations reduce visible user latency without requiring global database replication.
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