Cloud Digital Leader Google Cloud Products and Services Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Cloud DNS

  Why it's wrong here

  Cloud DNS provides domain name resolution, translating domain names to IP addresses, but its responsibility stops after returning DNS records. It does not distribute incoming traffic based on backend health, nor does it persist any application state. For a stateful web application, Cloud DNS cannot store session data or contribute to high availability beyond enabling clients to locate the service.

• ✓

  Persistent Disk

  Why this is correct

  Persistent Disk stores durable block-level data that exists independently of the virtual machine instance. When an instance is terminated or fails, the disk can be attached to a new instance in the same zone (or across zones with regional persistent disks), allowing the application to recover all state such as user sessions and database files. This independence is exactly what makes a stateful application resilient to instance-level failures.

• ✓

  Cloud Load Balancing

  Why this is correct

  Cloud Load Balancing distributes incoming traffic across healthy instances in a managed instance group, providing horizontal scaling and fault tolerance. It performs health checks and routes requests to available backends, but it does not store session data or any application state. It complements Persistent Disk by ensuring users can reach surviving instances that share the same underlying durable storage, without itself handling persistence.

• ✗

  Cloud CDN

  Why it's wrong here

  Cloud CDN caches static and dynamic content at global edge locations to reduce latency and lower load on origin servers. It does not provide persistent storage for application state, nor does it balance traffic for reliability; in fact, it may serve stale cached responses if the origin is down. Cached objects are ephemeral and not tied to the application's durable state, so Cloud CDN cannot help maintain state across instance failures.

• ✗

  Cloud NAT

  Why it's wrong here

  Cloud NAT enables private instances without external IP addresses to make outbound connections to the internet via Source Network Address Translation. It applies only to egress traffic, so it does not handle inbound user requests, distribute load, or persist data. For a stateful web application, Cloud NAT is irrelevant to the core requirements of data persistence and traffic distribution.

Go deeper

Related to this question