Professional Cloud Architect Free Practice Questions
This practice bank exercises your ability to make key architectural decisions across compute, storage, networking, security, and operations. You evaluate trade-offs such as managed vs. unmanaged services, regional vs. multi-regional storage, and synchronous vs. asynchronous communication. You apply principles like least privilege, infrastructure as code, and designing for disaster recovery with RTO/RPO. You also choose appropriate Google Cloud services for stateful workloads, secret management, and cost control. Mastery requires understanding when to use each service and how to align choices with business requirements like compliance, availability, and scalability.
What this PCA practice set measures
This is an analysis of the practice bank, not a claim about the vendor's live exam blueprint. Use it to identify the knowledge, judgment, and recall patterns exercised here, then verify your coverage against the current official exam guide.
Compute and Serverless Services
This section covers decisions around managed Kubernetes, Cloud Functions, and managed instance groups. Key considerations include whether to use a fully managed Kubernetes service (reducing operational overhead) versus self-managed, and when to use serverless functions versus managed VMs. The practice bank reinforces that managed Kubernetes still requires user node management, Cloud Functions automatically scales for event-driven workloads, and managed instance groups are ideal for stateless, identical application instances.
- Managed Kubernetes reduces control plane management but users still handle nodes and applications.
- Cloud Functions auto-scale for event-driven workloads; not suitable for persistent connections.
- Managed instance groups automate scaling and health checks for identical VMs.
Security and Access Control
This section focuses on service account security, network traffic control, and secret management. The practice bank emphasizes granting minimum permissions (least privilege), using firewall rules to restrict inbound traffic, and storing sensitive data like API keys in Secret Manager. These practices enforce access boundaries and protect against unauthorized exposure. Key decisions involve choosing appropriate roles and avoiding hardcoded or overly permissive configurations.
- Grant only necessary permissions to service accounts to minimize risk.
- Firewall rules restrict traffic by protocol, port, and source IP.
- Use Secret Manager to centralize and secure sensitive application data.
Networking and High Availability
This section covers load balancing, Cloud Pub/Sub, and Cloud Audit Logs. Load balancers distribute traffic to improve availability and responsiveness, while Cloud Pub/Sub decouples event producers and consumers for resilient architectures. Cloud Audit Logs provides a history of configuration changes, supporting auditing and troubleshooting. The practice bank illustrates that these services work together to create scalable, observable, and highly available systems.
- Load balancers spread traffic and perform health checks to enhance availability.
- Cloud Pub/Sub enables asynchronous, independent scaling of producers and consumers.
- Cloud Audit Logs records administrative and data access activities for governance.
Data Storage and Disaster Recovery
This section addresses data residency compliance, storage class selection, disaster recovery planning, and fully managed stateful databases. The practice bank shows how to align storage choices with access patterns and latency needs, and how to define RTO/RPO for disaster recovery. It also highlights Cloud Spanner as a service for strongly consistent, globally distributed stateful workloads. These decisions directly affect cost, performance, and business continuity.
- Data residency requires storing data in regions that comply with local laws.
- Regional storage offers lower latency; multi-regional provides broader geographic access.
- RTO and RPO define acceptable downtime and data loss for disaster recovery.
- Cloud Spanner provides strong consistency and high availability at global scale.
Practice Professional Cloud Architect with real flashcards
Read the prompt, commit to an answer, then flip the card. Move through the deck at your own pace and repeat any topic that does not come back quickly.
Card 1 of 20
1 reviewed this session
Static practice bank
Start the 15-question diagnostic
The complete question bank is embedded in this pre-rendered page. There is no database request or second content download when you begin.
What is a primary benefit of using a managed Kubernetes service on Google Cloud?
Show hint
Evaluate managed services trade-offs
Study workflow
Turn one PCA attempt into a study plan
- 1
Choose Between Managed and Unmanaged Compute
Evaluate workload requirements: if you want to reduce control plane management tasks, choose managed Kubernetes; for event-driven, short-lived logic, use Cloud Functions; for identical stateless VMs that auto-scale, use managed instance groups. Avoid managed services for workloads needing custom configurations or persistent connections.
- 2
Apply Least Privilege to Service Accounts
Identify the minimum permissions required for each service account to perform its tasks. Use predefined roles that align with job functions. Avoid granting broad roles like Owner or Editor. Regularly review and audit permissions using IAM Recommender to remove unused privileges.
- 3
Select Storage Classes Based on Access Patterns
Analyze data access frequency and geographic distribution. For low-latency access within a single region, use regional storage. For data accessed globally or requiring geo-redundancy, use multi-regional storage. Consider lifecycle policies to transition data to colder classes for cost savings.
- 4
Implement Disaster Recovery with RTO/RPO
Define Recovery Time Objective (maximum acceptable downtime) and Recovery Point Objective (maximum acceptable data loss). Choose a strategy (e.g., backup, standby, multi-region) that meets these targets. Regularly test failover procedures and document recovery steps.
- 5
Set Up Cost Budgets and Alerts
Create budgets at the project or billing account level to monitor spending. Set alert thresholds (e.g., 50%, 90%, 100%) to notify via email or Pub/Sub when usage exceeds predictions. Review budget reports regularly and adjust resource sizes or use committed use discounts to optimize costs.
FAQ
Questions about this PCA practice page
Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.
What is the difference between regional and multi-regional storage classes?+
Regional storage replicates data within a single region, offering lower latency for users in that region. Multi-regional storage replicates across multiple regions, providing broader geographic access and higher durability. Choose based on where your users are and latency requirements.
When should I use Cloud Pub/Sub instead of direct HTTP calls?+
Use Cloud Pub/Sub when you need to decouple event producers from consumers for resilience and independent scaling. It is ideal for asynchronous workloads, such as order processing or log streaming, where immediate response is not required. Direct HTTP calls suit synchronous request-reply patterns.
How do I manage service account keys securely?+
Avoid creating long-lived keys when possible; use workload identity federation or attach service accounts to resources. If keys are necessary, rotate them regularly, restrict usage with conditions, and store them in Secret Manager. Monitor key usage with Cloud Audit Logs.
What is the role of RTO and RPO in disaster recovery planning?+
Recovery Time Objective (RTO) defines the maximum acceptable downtime after a disaster. Recovery Point Objective (RPO) defines the maximum acceptable data loss measured in time. Together they guide the selection and configuration of backup, replication, and failover strategies.
What are best practices for designing a multi-region deployment?+
Consider data residency constraints and choose regions that comply with laws. Use Cloud Spanner or Cloud Bigtable for globally distributed data. Implement load balancing across regions and use Cloud CDN for static content. Plan for failover and test disaster recovery procedures regularly.
Build the next review session
Browse another free bank or use the study strategy guide to turn your misses into spaced review.