PCD Timed Practice Test 3 — 10 Questions

Question 1

A team is migrating a monolithic application to a microservices architecture on Google Kubernetes Engine (GKE). They want to ensure that failures in one microservice do not cascade to others. Which design pattern should they implement?

Accepted Answer

Implement a circuit breaker pattern that opens when failure thresholds are exceeded.. The circuit breaker pattern is the correct choice because it prevents cascading failures by monitoring inter-service calls and opening the circuit when failures exceed a threshold, allowing the system to fail fast and recover gracefully. In a GKE-based microservices architecture, this pattern is typically implemented using libraries like Resilience4j or Istio's circuit breaker, which can be configured to trip after a certain number of consecutive failures, thus protecting downstream services from being overwhelmed.

Answer

Implement retry logic with exponential backoff for all inter-service calls.

Answer

Use synchronous HTTP calls with timeouts to detect failures quickly.

Answer

Use bulkheads to separate thread pools for each service.

Question 2

A developer runs the command shown in the exhibit. They need to ensure that the application running on instance-3 can be restored quickly if it fails. What should they do?

Accepted Answer

Create a managed instance group using an instance template based on instance-3's boot disk.. Option C is correct because a managed instance group (MIG) with an instance template based on instance-3's boot disk provides automated health checking, auto-healing, and managed instance replacement. If instance-3 fails, the MIG automatically recreates it from the template, ensuring rapid restoration without manual intervention. This aligns with the goal of designing highly available and reliable applications on Google Cloud.

Answer

Add instance-3 to an unmanaged instance group.

Answer

Configure Cloud DNS with a health check pointing to instance-3.

Answer

Take a snapshot of instance-3's disk and use it to create a new instance manually.

Question 3

A company running a high-traffic e-commerce platform on Google Cloud experiences occasional data loss in their Cloud SQL database during failover events. The database is configured with a failover replica in a different zone. What is the most likely cause of the data loss?

Accepted Answer

The database is using asynchronous replication to the failover replica.. Cloud SQL uses synchronous replication for failover replicas by default, ensuring that transactions are committed on both the primary and the replica before acknowledging the write. If asynchronous replication is configured, the replica may lag behind the primary, and during a failover, any transactions not yet replicated are lost. This is the most likely cause of data loss during failover events.

Answer

Automated backups are not enabled.

Answer

The failover replica is configured as a read replica instead of a failover replica.

Answer

The database is not using regional persistent disks.

Question 4

A team is designing a globally distributed application on Google Cloud that requires strong consistency for writes but can tolerate eventual consistency for reads. The application expects millions of concurrent users. Which two strategies should they implement? (Choose two.)

Accepted Answer

Use Cloud Spanner for write operations requiring strong consistency.. Cloud Spanner provides strongly consistent writes globally through synchronous replication using the TrueTime API and Paxos-based consensus. This ensures that all write operations are immediately consistent across regions, meeting the requirement for strong consistency on writes.

Answer

Use Firestore in multi-region mode for all operations.

Answer

Deploy Cloud SQL with cross-region replication for read scalability.

Answer

Use Cloud Bigtable for reading data with strong consistency.

Question 5

A developer finds the JSON key shown in the exhibit in a Cloud Storage bucket that is publicly accessible. Which security best practice was violated?

Accepted Answer

The key was stored in a publicly accessible Cloud Storage bucket.. Option D is correct because storing a JSON key (a service account private key) in a publicly accessible Cloud Storage bucket directly violates the principle of least privilege and exposes sensitive credentials to unauthorized users. Any entity with read access to the bucket can retrieve the key and impersonate the service account, potentially gaining unauthorized access to Google Cloud resources.

Answer

The key is not rotated regularly.

Answer

The key was created as a user-managed key instead of a Google-managed key.

Answer

The key was not encrypted using Cloud KMS.

Question 6

A team is migrating a monolithic application to microservices on Google Kubernetes Engine (GKE). They want to ensure that if one microservice fails, it does not cascade to other services. Which design pattern should they implement?

Accepted Answer

Circuit Breaker pattern. The Circuit Breaker pattern is correct because it prevents cascading failures by monitoring for failures in a downstream microservice and, once a threshold is exceeded, immediately failing requests to that service without attempting the call. In GKE, this can be implemented using tools like Istio or Envoy sidecar proxies, which can be configured with circuit breaker settings to stop traffic to unhealthy pods, allowing the system to recover gracefully.

Answer

Event-driven architecture

Answer

Retry with exponential backoff

Answer

Bulkhead pattern

Question 7

A company is designing a cloud-native application on Google Cloud that requires low-latency access to a global user base. The application serves static content and dynamic APIs. Which strategy best minimizes latency while maintaining high availability?

Accepted Answer

Use Cloud CDN to cache static content and deploy the API across multiple regions with global load balancing.. Option B is correct because it combines Cloud CDN for caching static content at edge locations worldwide, reducing latency for static assets, and deploys the dynamic API across multiple regions with global load balancing (using Google Cloud's global external HTTP(S) load balancer) to route users to the nearest healthy backend, minimizing latency for dynamic requests while ensuring high availability through regional redundancy.

Answer

Deploy the application in a single region and use Cloud Interconnect for global access.

Answer

Use Cloud Armor to protect the application and rely on Google's backbone for low latency.

Answer

Store all content in Cloud Storage and serve directly from there.

Question 8

An application running on Cloud Run experiences cold starts causing latency spikes. What is the most cost-effective solution to reduce cold starts?

Accepted Answer

Set a minimum number of instances. Setting a minimum number of instances ensures that Cloud Run always keeps at least one instance warm (idle) to serve incoming requests instantly, eliminating cold start latency. This is the most cost-effective solution because you only pay for the minimum instances when they are idle (at a reduced rate), whereas other options increase per-request cost or do not address the root cause of cold starts.

Answer

Increase the container's CPU allocation

Answer

Enable HTTP keep-alive connections

Answer

Use a larger container memory size

Question 9

A company is building a real-time analytics application on Google Cloud that ingests data from thousands of IoT devices. The data must be processed with sub-second latency and stored in a time-series database for querying. Which combination of services provides the best scalability and availability?

Accepted Answer

Cloud Pub/Sub, Cloud Dataflow, Cloud Bigtable. Cloud Bigtable is a fully managed, scalable NoSQL database designed for large analytical and operational workloads, offering sub-10ms latency for time-series data. Combined with Cloud Pub/Sub for ingesting high-throughput IoT data and Cloud Dataflow for stream processing, this combination provides the best scalability and availability for real-time analytics with sub-second latency requirements.

Answer

Cloud Pub/Sub, Cloud Dataflow, Cloud Datastore

Answer

Cloud Pub/Sub, Cloud Functions, Cloud SQL

Answer

Cloud Pub/Sub, Cloud Dataflow, Cloud Storage

Question 10

A company runs a stateful application on Compute Engine instances with local SSDs. They need to perform maintenance that requires stopping the instances. What is the best approach to ensure data durability and minimal downtime?

Accepted Answer

Migrate data to persistent disks and configure the application to use persistent disks. Local SSDs provide ephemeral storage that is tied to the lifecycle of the Compute Engine instance. When an instance is stopped or terminated, data on local SSDs is permanently lost. To ensure data durability during maintenance that requires stopping the instance, the application must use persistent disks, which are durable network-attached storage that persists independently of the instance. Option D is correct because migrating the application to persistent disks ensures data survives the stop and allows the instance to be restarted with the same data, minimizing downtime.

Answer

Create a snapshot of the local SSD before stopping the instance

Answer

Use instance groups with autohealing to automatically recreate instances

Answer

Enable live migration on the instance