Important Google Professional Cloud Architect (PR000213) Exam Questions

CertPrep • Google • Professional Cloud Architect (PR000213) Exam Questions

Select Certification Providers

Select Certification Exam

Get Full Version

Google Cloud Architect Professional Professional Cloud Architect (PR000213) Exam

Attempt the Google Cloud Certified practice test and solve real exam-like Professional Cloud Architect (PR000213) questions to prepare efficiently and increase your chances of success. Our Google Professional Cloud Architect (PR000213) practice questions match the actual Google Cloud Architect Professional exam format, helping you enhance confidence and improve performance. With our Professional Cloud Architect (PR000213) practice exam software, you can analyze your performance, identify weak areas, and work on them effectively to boost your final Google Cloud Certified exam score.

Vendor:	Google
Exam Name:	Google Cloud Architect Professional
Registration Code:	Professional-Cloud-Architect
Related Certification:	Google Cloud Certified Certification
Exam Audience:	Google Cloud Architects, Google Cloud Administrators,

Total Questions

346

Last Updated

05-08-2026

Exam Duration

120 MINUTES

Upgrade to Premium

GET FULL PDF

Question: 1

You are deploying a critical application with a stateless, containerized (rented on Cloud Run and a Cloud SQL tor PostgreSQL backend The application experiences unpredictable traffic spikes, and the business requires the ability to immediately roll back a failed deployment to the last known good state You need to apply a deployment strategy that aligns with Site Reliability Engineering (SRE) principles for both the application code and the database schema updates, while meeting the business's requirements What should you do?

AConfigure the CI/CD pipeline to use the: latest Last container tag for deployments, with database schema changes applied manually as needed.

BUse a single CI/CD pipeline that first applies database schema changes and then deploys the new Cloud Run revision

CSeparate CI/CD pipelines for database schema migrations from application deployments When deploying a new Cloud Run revision, use gradual traffic split.

DPackage the database schema migration script within the container to be executed on every container startup before the application process begins.

Answer: C

Explanation:

In SRE (Site Reliability Engineering), the goal is to decouple components to reduce the 'blast radius' of changes.

Separation of Concerns: Database schema migrations and application code should have separate pipelines (Option C). If a schema update is backward-compatible (a requirement for zero-downtime), the app can be rolled back independently.

Traffic Management: Cloud Run supports gradual traffic splitting, allowing you to send 5% of traffic to a new revision. If errors spike, you can immediately shift 100% of traffic back to the old revision.

Why not D? Running migrations on container startup is a common 'anti-pattern' in large-scale systems because if 100 containers start at once, they might all try to modify the schema simultaneously, leading to lock contention or database corruption.

Question: 2

You need to develop procedures to verify resilience of disaster recovery for remote recovery using GCP. Your production environment is hosted on-premises. You need to establish a secure, redundant connection between your on premises network and the GCP network.

What should you do?

AVerify that Dedicated Interconnect can replicate files to GCP. Verify that direct peering can establish a
secure connection between your networks if Dedicated Interconnect fails.

BVerify that Dedicated Interconnect can replicate files to GCP. Verify that Cloud VPN can establish a secure connection between your networks if Dedicated Interconnect fails.

CVerify that the Transfer Appliance can replicate files to GCP. Verify that direct peering can establish a
secure connection between your networks if the Transfer Appliance fails.

DVerify that the Transfer Appliance can replicate files to GCP. Verify that Cloud VPN can establish a secure connection between your networks if the Transfer Appliance fails.

Answer: B

Explanation:

https://cloud.google.com/interconnect/docs/how-to/direct-peering

Question: 3

You have deployed several instances on Compute Engine. As a security requirement, instances cannot have a public IP address. There is no VPN connection between Google Cloud and your office, and you need to connect via SSH into a specific machine without violating the security requirements. What should you do?

AConfigure Cloud NAT on the subnet where the instance is hosted. Create an SSH connection to the Cloud NAT IP address to reach the instance.

BAdd all instances to an unmanaged instance group. Configure TCP Proxy Load Balancing with the instance group as a backend. Connect to the instance using the TCP Proxy IP.

CConfigure Identity-Aware Proxy (IAP) for the instance and ensure that you have the role of IAP-secured Tunnel User. Use the gcloud command line tool to ssh into the instance.

DCreate a bastion host in the network to SSH into the bastion host from your office location. From the bastion host, SSH into the desired instance.

Answer: C

Explanation:

https://cloud.google.com/iap/docs/using-tcp-forwarding#tunneling_with_ssh

Leveraging the BeyondCorp security model. 'This January, we enhanced context-aware access capabilities in Cloud Identity-Aware Proxy (IAP) to help you protect SSH and RDP access to your virtual machines (VMs)---without needing to provide your VMs with public IP addresses, and without having to set up bastion hosts. ' https://cloud.google.com/blog/products/identity-security/cloud-iap-enables-context-aware-access-to-vms-via-ssh-and-rdp-without-bastion-hosts

Question: 4

You are designing the storage architecture for a financial analytics platform. The platform ingests and stores terabytes of transactional data daily, which is used for both real-time fraud detection and long-term historical analysis. Transaction data from the last 30 days must be accessible with very low latency for the fraud detection engine. Data older than 30 days is accessed infrequently for quarterly reports, where retrieval times of a few seconds are acceptable. All data must be retained for five years to meet compliance regulations. You need to design a solution as cost-effective as possible. What should you do?

AStore all transaction data in a Cloud Storage bucket using the Standard storage class for the entire five-year retention period.

BIngest all data into BigQuery using time-partitioned tables, and rely on BigQuery's automatic long-term storage pricing for data older than 90 days.

CConfigure a Cloud Storage bucket with an Object Lifecycle Management policy to transition data from the Standard class to the Archive class after 30 days.

DConfigure a Cloud Storage bucket with an Object Lifecycle Management policy to transition data from the Standard class to the Coldline class after 30 days.

Answer: D

Explanation:

According to Google Cloud Storage documentation, the choice of storage class depends on the access frequency and retention period.

For the first 30 days, data requires 'very low latency,' making Standard Storage necessary. For data older than 30 days that is accessed for 'quarterly reports' (roughly every 90 days) where 'retrieval times of a few seconds' are acceptable, Coldline Storage is the most cost-effective choice. Coldline is designed for data accessed at most once a quarter. Transitioning to Archive (Option C) would be too aggressive, as Archive is intended for data accessed less than once a year and may have higher retrieval costs. Option B (BigQuery) is excellent for analytics but can be significantly more expensive than Cloud Storage for simple long-term retention of terabytes of raw transaction data. Object Lifecycle Management automates this transition, ensuring cost-efficiency over the 5-year compliance window.

Question: 5

For this question, refer to the EHR Healthcare case study. You are a developer on the EHR customer portal team. Your team recently migrated the customer portal application to Google Cloud. The load has increased on the application servers, and now the application is logging many timeout errors. You recently incorporated Pub/Sub into the application architecture, and the application is not logging any Pub/Sub publishing errors. You want to improve publishing latency. What should you do?

AIncrease the Pub/Sub Total Timeout retry value.

BMove from a Pub/Sub subscriber pull model to a push model.

CTurn off Pub/Sub message batching.

DCreate a backup Pub/Sub message queue.

Answer: C

Explanation:

https://cloud.google.com/pubsub/docs/publisher?hl=en#batching

SAVE TIME & QUICKLY PREPARE WITH REAL QUESTIONS

GET FULL ACCESS