Google Professional Cloud Architect (PR000213) Exam Questions Instant Access

Question 1

For this question, refer to the TerramEarth case study. TerramEarth has decided to store data files in Cloud Storage. You need to configure Cloud Storage lifecycle rule to store 1 year of data and minimize file storage cost.

Which two actions should you take?

ACreate a Cloud Storage lifecycle rule with Age: ''30'', Storage Class: ''Standard'', and Action: ''Set to Coldline'', and create a second GCS life-cycle rule with Age: ''365'', Storage Class: ''Coldline'', and Action: ''Delete''.

BCreate a Cloud Storage lifecycle rule with Age: ''30'', Storage Class: ''Coldline'', and Action: ''Set to Nearline'', and create a second GCS life-cycle rule with Age: ''91'', Storage Class: ''Coldline'', and Action: ''Set to Nearline''.

CCreate a Cloud Storage lifecycle rule with Age: ''90'', Storage Class: ''Standard'', and Action: ''Set to Nearline'', and create a second GCS life-cycle rule with Age: ''91'', Storage Class: ''Nearline'', and Action: ''Set to Coldline''.

DCreate a Cloud Storage lifecycle rule with Age: ''30'', Storage Class: ''Standard'', and Action: ''Set to Coldline'', and create a second GCS life-cycle rule with Age: ''365'', Storage Class: ''Nearline'', and Action: ''Delete''.

Answer : A

Question 2

You manage a highly distributed, hybrid- and multi-cloud IT environment and your developers rely heavily on Prometheus for their workflows. You need a cloud-based, highly scalable, low-maintenance enterprise solution that supports Prometheus Query Language (PromQL) queries, quick metric viewing, and efficient issue diagnosis. What should you do?

ADeploy a Prometheus operator in your existing Kubernetes and Serverless setup across multi-cloud environments.

BBuild a SaaS-based, Prometheus-compatible solution to display metrics for each cloud in a customizable way.

CEnable Google Cloud Managed Service for Prometheus to monitor and alert on your workloads at scale.

DSet up Cloud Monitoring as a single pane of glass across multi-cloud environments.

Answer : C

According to Google Cloud's Observability documentation, Google Cloud Managed Service for Prometheus (GMP) is the recommended enterprise solution for monitoring multi-cloud and hybrid environments while maintaining full PromQL compatibility.

GMP is a fully managed, multi-cloud solution that lets you monitor and alert on your workloads at scale without having to manually manage the storage, availability, or scaling of your Prometheus servers. It supports global aggregation of metrics, allowing developers to query data from multiple clusters and clouds (AWS, Azure, On-prem) using a single query interface. This satisfies the 'low-maintenance' and 'scalable' requirements while preserving the existing workflows developers are comfortable with. Option D is a general monitoring solution but doesn't offer the native, drop-in PromQL compatibility that GMP provides.

Question 3

For this question, refer to the Mountkirk Games case study

Mountkirk Games needs to create a repeatable and configurable mechanism for deploying isolated application environments. Developers and testers can access each other's environments and resources, but they cannot access staging or production resources. The staging environment needs access to some services from production.

What should you do to isolate development environments from staging and production?

ACreate a project for development and test and another for staging and production.

BCreate a network for development and test and another for staging and production.

CCreate one subnetwork for development and another for staging and production.

DCreate one project for development, a second for staging and a third for production.

Answer : D

Question 4

Your company has decided to build a backup replica of their on-premises user authentication PostgreSQL database on Google Cloud Platform. The database is 4 TB, and large updates are frequent. Replication requires private address space communication. Which networking approach should you use?

AGoogle Cloud Dedicated Interconnect

BGoogle Cloud VPN connected to the data center network

CA NAT and TLS translation gateway installed on-premises

DA Google Compute Engine instance with a VPN server installed connected to the data center network

Answer : A

https://cloud.google.com/docs/enterprise/best-practices-for-enterprise-organizations

Google Cloud Dedicated Interconnect provides direct physical connections and RFC 1918 communication between your on-premises network and Google's network. Dedicated Interconnect enables you to transfer large amounts of data between networks, which can be more cost effective than purchasing additional bandwidth over the public Internet or using VPN tunnels.

Benefits:

Traffic between your on-premises network and your VPC network doesn't traverse the public Internet. Traffic traverses a dedicated connection with fewer hops, meaning there are less points of failure where traffic might get dropped or disrupted.

Your VPC network's internal (RFC 1918) IP addresses are directly accessible from your on-premises network. You don't need to use a NAT device or VPN tunnel to reach internal IP addresses. Currently, you can only reach internal IP addresses over a dedicated connection. To reach Google external IP addresses, you must use a separate connection.

You can scale your connection to Google based on your needs. Connection capacity is delivered over one or more 10 Gbps Ethernet connections, with a maximum of eight connections (80 Gbps total per interconnect).

The cost of egress traffic from your VPC network to your on-premises network is reduced. A dedicated connection is generally the least expensive method if you have a high-volume of traffic to and from Google's network.

Question 5

Your company is planning to migrate their Windows Server 2022 from their on-premises data center to Google Cloud. You need to bring the licenses that are currently in use in on-premises virtual machines into the target cloud environment. What should you do?

A1. Create an image of the on-premises virtual machines and upload into Cloud Storage.
2. Import the image as a virtual disk on Compute Engine.

B1. Create standard instances on Compute Engine.
2. Select as the OS the same Microsoft Windows version that is currently in use in the on-premises environment.

C1. Create an image of the on-premises virtual machine.
2. Import the image as a virtual disk on Compute Engine.
3. Create a standard instance on Compute Engine, selecting as the OS the same Microsoft Windows version that is currently in use in the on-premises environment.
4. Attach a data disk that includes data that matches the created image.

D1. Create an image of the on-premises virtual machines.
2. Import the image as a virtual disk on Compute Engine using --os=windows-2022-dc-v.
3. Create a sole-tenancy instance on Compute Engine that uses the imported disk as a boot disk.

Answer : D

https://cloud.google.com/compute/docs/import/importing-virtual-disks

Question 6

For this question, refer to the Cymbal Retail case study. Cymbal wants to migrate its diverse database environment to Google Cloud while ensuring high availability and performance for online customers. The company also wants to efficiently store and access large product images These images typically stay In the catalog for more than 90 days and are accessed less and less frequently. You need to select the appropriate Google Cloud services for each database. You also need to design a storage solution for the product images that optimizes cost and performance What should you do?

AMigrate all databases to Spanner for consistency, and use Cloud Storage Standard for image storage

BMigrate all databases to self-managed instances on Compute Engino. and use a persistent disk for image storage.

CMigrate MySQL and SQL Server to Spanner. Redis to Memorystore. and MongoDB to Firestore Use Cloud Storage Standard for image storage, and move
images to Cloud Storage Nearline storage when products become less popular.

DMigrate MySQL to Cloud SQL. SQL Server to Cloud SQL. Redis to Memorystore. and MongoDB to Firestore. Use Cloud Storage Standard for image storage, and move images to Cloud Storage Coldline storage when products become less popular

Answer : D

The Google Cloud database migration path follows a 'like-for-like' managed service strategy. Cloud SQL is the recommended destination for MySQL and SQL Server workloads that do not require the massive horizontal scale of Spanner, fitting Cymbal's 'Technical Stack Modernization' goals. Memorystore is the managed service for Redis, and Firestore is the native NoSQL replacement for MongoDB.

For the image storage requirement, Cloud Storage Coldline is the mathematically correct choice for data accessed 'less and less frequently' with a retention period exceeding 90 days. According to Cloud Storage documentation, Coldline is specifically designed for data accessed at most once a quarter (90 days). Using Object Lifecycle Management to move images from Standard to Coldline allows Cymbal to 'reduce costs' while keeping images 'immediately accessible' (unlike Archive storage, which may have different trade-offs). Option C is less optimal because Nearline is intended for 30-day access patterns; given the images stay for 90+ days and usage drops significantly, the deeper savings of Coldline are preferred. Option A is over-engineered (Spanner for all) and expensive, while Option B contradicts the requirement to 'reduce costs' by increasing operational overhead

Question 7

Mountkirk Games wants you to secure the connectivity from the new gaming application platform to Google

Cloud. You want to streamline the process and follow Google-recommended practices. What should you do?

AConfigure Workload Identity and service accounts to be used by the application platform.

BUse Kubernetes Secrets, which are obfuscated by default. Configure these Secrets to be used by the
application platform.

CConfigure Kubernetes Secrets to store the secret, enable Application-Layer Secrets Encryption, and use
Cloud Key Management Service (Cloud KMS) to manage the encryption keys. Configure these Secrets to
be used by the application platform.

DConfigure HashiCorp Vault on Compute Engine, and use customer managed encryption keys and Cloud
Key Management Service (Cloud KMS) to manage the encryption keys. Configure these Secrets to be used
by the application platform.

Answer : A

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