📐 Designing and Planning a Cloud Solution Architecture - PCA Practice Questions

Design cloud architectures considering business requirements, technical requirements, and Google Cloud best practices.

11Questions Available
1Exam Domains

Practice Designing & Planning Questions Now

Start a timed practice session focusing on Designing and Planning a Cloud Solution Architecture topics from the PCA question bank.

Start PCA Practice Quiz →

PCA Designing & Planning Question Bank (11 Questions)

Browse all 11 practice questions covering Designing and Planning a Cloud Solution Architecture for the PCA certification exam. Each question includes the full answer and a detailed explanation to help you understand the concepts.

  1. Question 1Designing and Planning a Cloud Solution Architecture

    A company wants to migrate a monolithic e-commerce application to Google Cloud. They need 99.99% availability and sub-second latency globally. What architecture should you recommend?

    ASingle-region Compute Engine VMs
    BMicroservices on GKE Autopilot with multi-region deployment, Cloud Spanner for global consistency, global HTTPS load balancer, and Cloud CDN
    CApp Engine Standard in one region
    DCloud Functions for all services
    Show Answer & Explanation
    Correct Answer: B
    Explanation:

    99.99% global availability: multi-region GKE Autopilot (managed, multi-zone), Cloud Spanner (99.999% SLA, global strong consistency), global HTTPS LB (anycast IP, nearest backend), Cloud CDN (edge caching). Microservices enable independent scaling/deployment. This architecture addresses all requirements.

  2. Question 2Designing and Planning a Cloud Solution Architecture

    A company wants to avoid vendor lock-in and run workloads on both Google Cloud and AWS. What architecture approach should you recommend?

    ABuild separate architectures for each cloud
    BUse Anthos for consistent Kubernetes management across clouds, Terraform for multi-cloud IaC, and open standards (gRPC, OpenTelemetry, Kubernetes) for portability
    CUse only serverless on both clouds
    DUse VPN between the clouds
    Show Answer & Explanation
    Correct Answer: B
    Explanation:

    Multi-cloud strategy: Anthos (consistent Kubernetes management — GCP, AWS, Azure, on-prem), Terraform (single IaC tool for all clouds), open standards (Kubernetes, gRPC, OpenTelemetry, PostgreSQL). Trade-offs: increased complexity, lowest-common-denominator features. Use cloud-specific services where ROI justifies lock-in risk.

  3. Question 3Designing and Planning a Cloud Solution Architecture

    A company processes 500GB of new data daily from IoT devices and needs real-time analytics plus historical analysis. What data architecture should you design?

    AStore everything in Cloud SQL
    BIoT Core → Pub/Sub → Dataflow (real-time processing) → BigQuery (analytics warehouse) + Cloud Storage (raw data lake), with Looker for dashboards
    CStore in Compute Engine local disks
    DUse only Cloud Functions
    Show Answer & Explanation
    Correct Answer: B
    Explanation:

    IoT data pipeline: IoT Core (device management) → Pub/Sub (ingestion buffer) → Dataflow (streaming transform, enrich, validate) → dual sink: BigQuery (analytics, SQL queries, dashboards) + Cloud Storage (raw data lake, data replay, compliance). Looker/Looker Studio for dashboards. Bigtable alternative for ultra-low-latency time-series queries.

  4. Question 4Designing and Planning a Cloud Solution Architecture

    You are designing a public API that needs to handle millions of requests per day. What architecture ensures scalability and reliability?

    ASingle Compute Engine VM
    BApigee for API management + Cloud Run as backend (auto-scales) + Cloud CDN for cacheable responses + Cloud Armor for security + Pub/Sub for async processing
    CApp Engine Standard only
    DCloud Functions for everything
    Show Answer & Explanation
    Correct Answer: B
    Explanation:

    Scalable public API: Apigee (rate limiting, quotas, API keys, developer portal, analytics), Cloud Run (auto-scales to handle spikes, scale to zero during quiet), Cloud CDN (cache GET responses at edge), Cloud Armor (WAF + DDoS), Pub/Sub (offload heavy processing asynchronously). This handles millions of requests with cost efficiency.

  5. Question 5Designing for Security and Compliance

    How should you design centralized logging for a multi-project organization?

    ACheck logs in each project separately
    BCreate organization-level log sinks to export all audit logs to a dedicated security project with BigQuery for analysis and Chronicle SIEM for threat detection
    CDisable logging to save costs
    DOnly log errors
    Show Answer & Explanation
    Correct Answer: B
    Explanation:

    Centralized logging: Organization-level log sink (captures all projects) → routes to: BigQuery (SQL analysis, long retention), Cloud Storage (archive), Pub/Sub (real-time SIEM feed). Dedicated security project: restricted access (security team only). Log types: Admin Activity (always on), Data Access (enable for sensitive projects). Chronicle SIEM for threat detection, correlation, investigation.

  6. Question 6Designing and Planning a Cloud Solution Architecture

    A company wants to build a recommendation engine using their proprietary data. What Google Cloud architecture should you design?

    ABuild from scratch on VMs
    BVertex AI: Feature Store for feature management, custom training with GPUs, Model Registry for versioning, online/batch prediction endpoints, and Vertex AI Pipelines for ML ops
    CUse BigQuery only
    DUse Cloud Functions for ML
    Show Answer & Explanation
    Correct Answer: B
    Explanation:

    ML recommendation architecture: Data → BigQuery (feature computation) → Vertex AI Feature Store (serve features online/offline). Training: Vertex AI Custom Training (GPU/TPU) or AutoML. Model Registry: version, compare, promote. Prediction: online endpoints (real-time) or batch prediction. MLOps: Vertex AI Pipelines (Kubeflow-based), model monitoring for drift detection.

  7. Question 7Designing and Planning a Cloud Solution Architecture

    A legacy system processes orders synchronously, causing timeout errors during peak times. How do you redesign it for reliability?

    AAdd bigger servers
    BDecouple with Pub/Sub: accept orders synchronously (fast acknowledgment), publish to Pub/Sub for async processing, with Cloud Tasks for reliable delivery and dead-letter queues for failures
    CAdd a CDN
    DMove to a faster database
    Show Answer & Explanation
    Correct Answer: B
    Explanation:

    Decouple synchronous processing: API accepts order → writes to DB (fast) → publishes to Pub/Sub → returns 202 Accepted. Workers (Cloud Run/GKE) subscribe and process async. Benefits: no timeouts (processing decoupled from request), backpressure handling (Pub/Sub buffers), retry (DLQ for failures), independent scaling of API and workers.

  8. Question 8Designing for Security and Compliance

    You are designing a zero-trust security architecture for a company migrating to Google Cloud. Which components should you include?

    ATraditional VPN for all access
    BBeyondCorp Enterprise (IAP for app access), Workload Identity (GKE authentication), Cloud Armor (WAF), VPC Service Controls (data perimeter), and continuous verification
    COnly firewall rules
    DOnly encryption
    Show Answer & Explanation
    Correct Answer: B
    Explanation:

    Zero-trust components: BeyondCorp/IAP (identity-based app access — no VPN), Workload Identity (pod-level authentication), Cloud Armor (WAF + DDoS), VPC Service Controls (data perimeter), Binary Authorization (trusted container images), Security Command Center (posture management), Context-Aware Access (device + identity + context).

  9. Question 9Designing and Planning a Cloud Solution Architecture

    You are designing a microservices architecture where services need to communicate asynchronously. What pattern should you use?

    ADirect HTTP calls between all services
    BEvent-driven architecture using Pub/Sub for async communication, with Eventarc for routing events to Cloud Run services and Workflows for orchestration
    CShared database for all services
    DFTP file transfers
    Show Answer & Explanation
    Correct Answer: B
    Explanation:

    Async microservices: Pub/Sub (durable message queue — decouples producers/consumers), Eventarc (routes GCP events to Cloud Run/GKE/Workflows), Cloud Tasks (guaranteed task delivery with rate control), Workflows (orchestrate multi-step processes). Benefits: loose coupling, fault tolerance, independent scaling, eventual consistency.

  10. Question 10Designing and Planning a Cloud Solution Architecture

    You need to design an image processing pipeline: when a user uploads an image to Cloud Storage, it should be resized, stored, and the user notified. What architecture should you use?

    AA cron job checking for new files
    BCloud Storage event → Eventarc → Cloud Run job (resize image) → store result in Cloud Storage → Pub/Sub notification → Cloud Functions (send email/push notification)
    CManual processing
    DCompute Engine polling Cloud Storage
    Show Answer & Explanation
    Correct Answer: B
    Explanation:

    Event-driven pipeline: Cloud Storage upload triggers Eventarc (event routing) → Cloud Run job (process image — resize, compress, generate thumbnails) → write results to output bucket → Pub/Sub event → Cloud Functions or another Cloud Run service sends notification (email via SendGrid, push via FCM). Fully serverless, auto-scales, pay-per-event.

  11. Question 11Managing Implementation

    What documentation should accompany a cloud architecture design?

    AOnly diagrams
    BArchitecture Decision Records (ADRs), architecture diagrams (logical + deployment), runbooks, DR plan, security design document, cost estimates, and SLO definitions
    COnly a README file
    DNo documentation needed
    Show Answer & Explanation
    Correct Answer: B
    Explanation:

    Architecture documentation: ADRs (why decisions were made — trade-offs, alternatives considered), logical architecture diagram (services, data flow), deployment diagram (regions, zones, networks), runbooks (operational procedures), DR plan (failover steps, RTO/RPO), security doc (controls, threat model), cost model (estimates + optimization plan), SLO definitions.

Key Designing & Planning Concepts for PCA

architecturedesignplanningrequirementsmigrationhybrid cloudmulti-cloud

PCA Designing & Planning Exam Tips

Designing and Planning a Cloud Solution Architecture questions in PCA are typically scenario-based. Focus on service-level decision making aligned to official exam objectives. Priority concepts: architecture, design, planning, requirements, migration, hybrid cloud.

What PCA Expects

  • Anchor your answer in select the most practical, secure, and scalable answer for the stated scenario.
  • Designing & Planning scenarios for PCA are frequently mapped to Domain 1 (~25%), so read the objective carefully before picking controls or architecture.
  • Expect multi-service scenarios where Designing & Planning interacts with IAM, networking, storage, or observability patterns rather than appearing as an isolated service question.
  • When two options are both technically valid, prefer the choice that best aligns with the exam's operational scope (Professional) and managed-service best practices.

High-Value Designing & Planning Concepts

  • Know the core Designing & Planning building blocks cold: architecture, design, planning, requirements.
  • Review the edge-case features and limits for migration, hybrid cloud; these details are commonly used to differentiate answer choices.
  • Practice service-integration reasoning: how Designing & Planning pairs with Managing & Provisioning, Security & Compliance in real deployment patterns.
  • For PCA, explain why the chosen Designing & Planning design meets reliability, security, and cost expectations better than the alternatives.

Common PCA Traps

  • Watch for answers that partially solve the requirement but miss operational constraints.
  • Questions in Designing and Planning often include distractors that look correct for Designing & Planning but violate least-privilege, durability, or availability requirements.
  • Avoid picking options purely by feature name; validate data path, failure handling, and governance impact before answering.
  • If the prompt hints at automation or repeatability, eliminate manual-only operational answers first.

Fast Review Checklist

  • Can you compare at least two Designing & Planning implementation paths and justify which one best fits the scenario?
  • Can you map the chosen answer back to Designing and Planning (~25%) outcomes for PCA?
  • Can you explain security and access boundaries for Designing & Planning without relying on default-open assumptions?
  • Can you describe how Designing & Planning integrates with Managing & Provisioning and Security & Compliance during failure, scaling, and monitoring events?

Exam Domains Covering Designing & Planning

Related Resources

More PCA Study Resources