PCD Designing highly scalable, available, and reliable cloud-native applications Practice Test 4 — 15 Questions

Question 1

A developer deployed the above Cloud Run service YAML. The service deploys successfully but any request fails with a 503 error. What is the most likely cause?

Accepted Answer

The container is not listening on the expected port.. A 503 error from Cloud Run indicates that the service is failing to respond to health checks or requests. The most common cause is that the container is not listening on the port specified in the `containerPort` field of the YAML (default 8080). Cloud Run sends requests to that port, and if the application is bound to a different port (e.g., 3000 or 80), the request never reaches the application, resulting in a 503.

Answer

The service has no ingress setting.

Answer

The container image has a different entrypoint.

Answer

containerConcurrency is set too high.

Question 2

A company wants to deploy a stateless web application that needs to handle unpredictable traffic spikes with minimal operational overhead. Which Google Cloud compute service is most cost-effective and operationally simple?

Accepted Answer

Cloud Run. Cloud Run is the most cost-effective and operationally simple choice for a stateless web application with unpredictable traffic spikes because it automatically scales from zero to thousands of containers based on request load, charges only for resources used during request processing (down to 100ms increments), and eliminates infrastructure management. It supports any language or framework via container images, making it ideal for stateless HTTP workloads without the cold-start latency concerns of Cloud Functions or the cluster management overhead of GKE.

Answer

App Engine Standard

Answer

Cloud Functions

Answer

Google Kubernetes Engine (GKE)

Answer

Compute Engine with Managed Instance Group

Question 3

An e-commerce company relies on a Compute Engine backend serving content to global users. They notice high latency for users outside the primary region. Which service should they add to reduce latency by caching content at edge locations?

Accepted Answer

Cloud CDN. Cloud CDN (Content Delivery Network) uses Google's global edge cache locations to serve cached content closer to users, reducing latency for requests that would otherwise travel to the origin Compute Engine backend in a single region. By caching static or dynamic content at edge nodes, Cloud CDN minimizes round-trip time and offloads traffic from the backend instance.

Answer

Cloud Armor

Answer

Cloud NAT

Answer

Cloud Endpoints

Answer

Cloud Load Balancing

Question 4

A startup expects low and predictable traffic initially but wants to use containers with minimal operational overhead. Which compute service should they choose?

Accepted Answer

Cloud Run. Cloud Run is the correct choice because it runs containers in a fully managed, serverless environment that automatically scales from zero, requires no cluster management, and charges only for resources used during request processing. This matches the startup's need for minimal operational overhead and low, predictable traffic, as Cloud Run abstracts away infrastructure management entirely.

Answer

App Engine Flexible Environment

Answer

Google Kubernetes Engine (GKE)

Answer

Compute Engine

Answer

Cloud Functions

Question 5

A company runs a stateful microservice that requires read-after-write consistency but can tolerate some latency for writes. They are currently using a single Cloud SQL instance and want to scale read traffic. Which approach should they take?

Accepted Answer

Enable Cloud SQL read replicas. Cloud SQL read replicas are the correct choice because they provide an asynchronous read-only copy of the primary instance, which can scale read traffic without compromising the read-after-write consistency required by the stateful microservice. The primary instance handles all writes, ensuring strong consistency for writes, while replicas serve stale reads that eventually become consistent, which aligns with the tolerance for write latency.

Answer

Use Cloud Memorystore to cache reads

Answer

Shard the database manually

Answer

Use Cloud Bigtable

Answer

Migrate to Cloud Spanner

Question 6

A company uses Cloud Functions to process events from Pub/Sub. They notice that occasionally the same message is processed more than once. What can they do to ensure idempotent processing?

Accepted Answer

Make the function idempotent using a deduplication field. Making the function idempotent using a deduplication field ensures that even if the same Pub/Sub message is delivered more than once (Pub/Sub offers at-least-once delivery), the function processes it only once. By checking a unique message ID or a custom deduplication key before processing, the function can skip or safely reapply the operation, preventing duplicate side effects.

Answer

Configure retry policies to only retry once

Answer

Use Cloud Tasks instead

Answer

Use Cloud Scheduler

Answer

Increase the acknowledgement deadline for the subscription

Question 7

A company runs a batch job daily that processes large files from Cloud Storage and stores results in BigQuery. The job requires significant compute for about 10 minutes and is fault-tolerant. Which compute option is most cost-effective?

Accepted Answer

Preemptible VM. Preemptible VMs offer the same compute capacity as regular VMs at a significantly lower cost (up to 80% discount), and since the batch job runs for only 10 minutes daily and is fault-tolerant, it can handle the occasional preemption without data loss. The job's short duration and fault tolerance make preemptible instances ideal, as they can be restarted if terminated.

Answer

Cloud Run Jobs

Answer

Always-on Compute Engine VM

Answer

GKE cluster with a single node

Answer

Cloud Functions (9-minute timeout)

Question 8

A financial services company has a critical application that must survive a regional outage. They deployed on Compute Engine across multiple zones within a single region and now want to redirect traffic to a secondary region if the primary region becomes unavailable. Which load balancing solution should they use?

Accepted Answer

External HTTP(S) Load Balancer. The External HTTP(S) Load Balancer is the correct choice because it supports global load balancing across multiple regions, enabling traffic failover to a secondary region when the primary region becomes unavailable. It uses anycast IP addresses and is designed for HTTP/S traffic, making it suitable for a critical application that must survive a regional outage.

Answer

SSL Proxy Load Balancer

Answer

Proxy Network Load Balancer

Answer

Internal TCP/UDP Load Balancer

Answer

Network Load Balancer

Question 9

A company uses GKE with cluster autoscaling and node auto-upgrade. During a traffic spike, new pods are unschedulable even though the cluster autoscaler adds nodes. What is the most likely cause?

Accepted Answer

The pods have tolerations that don't match node taints. If pods have tolerations that do not match the taints on the nodes, the scheduler will not place them on those nodes, even if the cluster autoscaler has added new nodes. This mismatch prevents scheduling, leading to unschedulable pods despite sufficient node capacity.

Answer

The pods have resource requests that exceed available node capacity

Answer

The cluster autoscaler is disabled

Answer

The node pool has reached its maximum size limit

Answer

The nodes are in unhealthy status

Question 10

A company uses Cloud SQL for MySQL and wants to achieve high availability with automatic failover across zones while minimizing data loss. Which configuration should they use?

Accepted Answer

Configure a regional Cloud SQL instance with automatic failover. A regional Cloud SQL instance with automatic failover provides synchronous replication of data between two zones within the same region, ensuring zero data loss (RPO=0) and automatic failover with minimal downtime (RTO typically under 60 seconds). This meets the requirement for high availability with automatic failover across zones while minimizing data loss.

Answer

Enable read replicas in different zones

Answer

Use external read replicas with a failover script

Answer

Use Cloud SQL Enterprise Plus edition

Answer

Enable point-in-time recovery

Question 11

A company uses Cloud Spanner for a global application. They want to improve read performance for point-reads (individual row lookups). Which TWO strategies should they adopt?

Accepted Answer

Create secondary indexes. Secondary indexes in Cloud Spanner allow point-reads to be served directly from the index table, avoiding a full table scan and reducing latency. Interleaved tables store child rows physically adjacent to their parent row, enabling efficient single-row lookups without cross-node coordination.

Answer

Use read replicas

Answer

Partition the table by time

Answer

Use batch reads

Question 12

A company runs a microservices architecture on GKE with gRPC services. They want to implement traffic splitting for canary deployments. Which THREE components should they use?

Accepted Answer

Istio or Anthos Service Mesh. Istio or Anthos Service Mesh provides fine-grained traffic splitting capabilities for canary deployments in a GKE environment. It uses Envoy sidecar proxies to route a percentage of traffic to different service versions based on HTTP headers or weight, enabling controlled rollouts without modifying application code.

Answer

ClusterIP service

Answer

Headless service

Question 13

A company uses Cloud Load Balancing to distribute traffic to HTTP backends. They want to protect against application-layer DDoS attacks (e.g., HTTP flood). Which TWO services should they combine?

Accepted Answer

Cloud Armor. Cloud Armor is correct because it provides Web Application Firewall (WAF) capabilities and DDoS protection at the application layer, allowing you to create security policies that filter HTTP/HTTPS traffic based on IP addresses, geo-locations, or custom rules (e.g., rate limiting) to mitigate HTTP flood attacks. Cloud CDN is correct because it caches content at edge locations, absorbing a significant portion of malicious traffic before it reaches the backend, reducing the load on origin servers and acting as a first line of defense against volumetric application-layer attacks.

Answer

Cloud Firewall rules

Answer

Cloud NAT

Answer

Cloud Endpoints

Question 14

The developer runs the command above and sees both instances are unhealthy. The instances are running and serving traffic on port 80 when accessed directly. What is the most likely cause?

Accepted Answer

Firewall rules block the health check probe IP ranges. The most likely cause is that firewall rules are blocking the health check probe IP ranges. Google Cloud Platform (GCP) load balancers use specific, documented IP ranges for health check probes. If a firewall rule denies traffic from these ranges, the load balancer will mark the instances as unhealthy even though the instances are running and serving traffic on port 80 when accessed directly. This is a common misconfiguration because the health check probes originate from these special IP ranges, not from the load balancer's frontend IP.

Answer

The instances have been deleted

Answer

The instances are not running the specified health check port

Answer

The load balancer is misconfigured

Answer

The instances are out of memory and unable to respond

Question 15

A developer deploys this Cloud Run service. During a load test, each incoming request starts a new container instance, even though concurrency is set to 80. What is the reason?

Accepted Answer

The container is not designed to handle multiple concurrent requests (single-threaded). Cloud Run's concurrency setting controls how many requests the runtime can send to a container instance, but the container itself must be capable of handling those requests concurrently. If the application is single-threaded or uses a blocking I/O model (e.g., a simple Flask or Express server without async workers), it can only process one request at a time. Cloud Run detects that the container is busy and starts a new instance for each incoming request, effectively ignoring the concurrency setting.

Answer

The memory limit is too low

Answer

The container is CPU-bound and cannot handle multiple requests concurrently

Answer

The CPU limit is too low

Answer

The concurrency setting of 80 is too high and Cloud Run ignores it