All practice questions

1598 questions

Question 441Question

A company wants to deploy a simple, stateless HTTP web API on Google Cloud. The service experiences unpredictable, low-volume traffic and requires scale-to-zero capabilities with zero server management overhead. Which Google Cloud compute platform is the most suitable choice for this requirement?

Show answer & explanation

Answer: Cloud Run

Answer

Cloud Run
Cloud Run is the optimal compute platform for containerized stateless HTTP microservices because it operates as a fully managed serverless solution that automatically scales instances based on incoming request volume and scales down to zero when idle.

Step-by-Step Solution

1
Analyze workload requirements
The application is a stateless HTTP API with low, unpredictable traffic requiring scale-to-zero and minimal operational maintenance.
Understanding architectural constraints narrows down suitable compute platforms.
2
Select the optimal compute option
Cloud Run provides serverless container deployment that automatically scales instances based on incoming HTTP requests, including scaling down to zero.
Cloud Run fulfills serverless stateless execution requirements without infrastructure management overhead.

Key Concept

Selecting compute platforms for stateless containerized HTTP microservices
Question 442Question

A multinational financial technology institution is migrating its core transaction history and customer records from an on-premises data center to Google Cloud. The dataset consists of 1.8 PB1.8\text{ PB} of static compliance audit logs stored on a local NAS and an active 3 TB3\text{ TB} transactional database running on MySQL. The enterprise has a single dedicated 1 Gbps1\text{ Gbps} Cloud Interconnect connection to GCP. The migration schedule dictates that all static data must be transferred within 30 days without impacting daily business traffic, while the database migration allows a maximum downtime cutover window of 4 hours4\text{ hours}. Which TWO migration strategies should the Lead Cloud Architect recommend to satisfy these operational constraints? (Select two.)

Select all that apply

Show answer & explanation

Answer: Order Google Cloud Transfer Appliance devices to transfer the 1.8 PB1.8\text{ PB} static audit logs offline to Cloud Storage.; Utilize Database Migration Service (DMS) with continuous Change Data Capture (CDC) over the Dedicated Interconnect for the transactional MySQL database prior to final cutover.

Answer

The architect should order Google Cloud Transfer Appliance devices for the petabyte-scale offline log transfer and use Database Migration Service with continuous Change Data Capture (CDC) over Dedicated Interconnect for the database cutover.
The correct strategy combines offline appliance shipment for large static data and online continuous database synchronization over the private connection. Transferring 1.8 PB1.8\text{ PB} over a 1 Gbps1\text{ Gbps} connection is mathematically impossible within 30 days, making offline Transfer Appliance mandatory. For the database, Database Migration Service (DMS) with continuous CDC allows data to sync in the background while production stays online, enabling a quick cutover within the 4-hour downtime limit.

Step-by-Step Solution

1
Calculate bandwidth throughput for the 1.8 PB1.8\text{ PB} static dataset.
At 1 Gbps1\text{ Gbps} maximum network speed, moving 1.8 PB1.8\text{ PB} requires 166 days\approx 166\text{ days}, exceeding the 30-day migration window.
Determines whether an online transfer tool (Storage Transfer Service) or offline device (Transfer Appliance) is required.
2
Select the appropriate data transfer mechanism for petabyte-scale static data.
Transfer Appliance handles multi-petabyte datasets securely offline within days.
Avoids network link saturation and meets the strict 30-day completion deadline.
3
Evaluate database size (3 TB3\text{ TB}) and downtime constraint (4 hours4\text{ hours}).
Database Migration Service (DMS) supports continuous CDC synchronization over the existing Dedicated Interconnect.
Allows bulk baseline replication while applications remain operational, keeping cutover downtime well under 4 hours4\text{ hours}.

Key Concept

Designing hybrid enterprise migration strategies balancing offline appliance bulk transfers against online continuous database replication.
Question 443Question

An enterprise IoT platform processes irregular spikes of incoming telemetry messages delivered via Cloud Pub/Sub. Each message requires a lightweight, stateless data validation step that takes approximately 200 milliseconds to execute. The system experiences long periods of zero traffic during maintenance windows, and the operations team wants to minimize both administrative overhead and baseline infrastructure cost. Which compute platform should you select to host the data validation service?

Show answer & explanation

Answer: Cloud Run configured with Pub/Sub push subscription delivery

Answer

Cloud Run configured with Pub/Sub push subscription delivery is the optimal choice because it provides serverless autoscaling down to zero instances for stateless validation logic while avoiding infrastructure management overhead.
The solution requiring Cloud Run with Pub/Sub push subscription delivery is correct because Cloud Run provides fully managed serverless execution for stateless containerized workloads. It automatically scales instances up to meet incoming request spikes and down to zero when idle, avoiding baseline compute costs and administrative overhead.

Step-by-Step Solution

1
Analyze workload characteristics and requirements
The workload consists of short, stateless validation logic triggered by Pub/Sub messages with idle periods and a strict requirement to minimize operational overhead and baseline costs.
Identifying statefulness, scaling range, and management constraints determines the appropriate compute abstraction layer.
2
Evaluate Google Cloud compute options against requirements
Cloud Run handles stateless containerized HTTP workloads with scale-to-zero capability natively via Pub/Sub push subscriptions, satisfying zero baseline cost and low management overhead requirements.
Serverless container platforms eliminate OS and cluster management while providing pay-per-use billing during execution.

Key Concept

Selecting serverless container platforms (Cloud Run) for stateless event-driven processing to minimize cost and operational overhead
Question 444Question

An enterprise is implementing a automated cloud infrastructure deployment pipeline on Google Cloud for a global transactional database and operational storage architecture. The technical requirements specify a relational database engine capable of handling multi-region transactions with external consistency across continents. Furthermore, the Infrastructure as Code (IaC) deployment pipeline using Terraform must guarantee concurrency safety and state recovery against corrupted or conflicting parallel executions. Which TWO architecture and provisioning strategies should be implemented to satisfy these requirements?

Select all that apply

Show answer & explanation

Answer: Provision a Cloud Spanner multi-region instance configuration to support globally distributed relational transactions with strong consistency.; Configure the Terraform backend using a Google Cloud Storage bucket with object versioning enabled and native state locking.

Answer

The correct architecture requires provisioning a Cloud Spanner multi-region instance for global relational ACID transactions and configuring a Cloud Storage backend with object versioning and state locking for Terraform state management.
Provisioning Cloud Spanner satisfies the requirement for multi-region relational database transactions with external consistency. Additionally, using Cloud Storage with versioning and state locking for the Terraform remote backend ensures safe concurrent deployment pipeline execution without state corruption.

Step-by-Step Solution

1
Analyze the database requirements for global multi-region transactional processing.
Identify that Cloud Spanner is required due to its native support for multi-region, strongly consistent relational transactions, whereas Cloud SQL only supports regional primary instances with read replicas.
Cloud SQL cannot support multi-region write transactions across continents.
2
Analyze Infrastructure as Code state management requirements for CI/CD safety.
Select Google Cloud Storage as the remote backend for Terraform, enabling object versioning and locking.
Remote state locking prevents concurrent pipeline runs from corrupting state, while object versioning allows rolling back state in case of corruption.

Key Concept

Multi-region database provisioning and IaC remote state locking
Estimated Time:3m 0s
Question 445Question

A multinational financial services institution is building a hybrid cloud infrastructure to connect its primary on-premises data center with Google Cloud. The architecture must satisfy three mandatory requirements: (1) achieve a 99.99% availability SLA for the underlying physical connection, (2) enforce IPsec encryption for all data in transit across the hybrid connection, and (3) enable on-premises workloads to securely communicate with a secondary backend VPC network (`vpc-partner`) through an established landing VPC network (`vpc-hub`). Which TWO architectural configurations must the cloud network architect implement to satisfy these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Provision four Dedicated Interconnect VLAN attachments distributed across two distinct metropolitan areas and two Edge Availability Domains per metro, and construct HA VPN tunnels over the Interconnect attachments.; Deploy HA VPN tunnels between `vpc-hub` and `vpc-partner` using dynamic BGP routing to overcome VPC Network Peering non-transitivity for on-premises traffic.

Answer

To meet all requirements, the architect must establish a 99.99% SLA Dedicated Interconnect topology using four VLAN attachments across two metropolitan locations and two Edge Availability Domains per metro with HA VPN over Interconnect for IPsec encryption, and deploy an HA VPN link between the landing VPC and backend VPC to handle transitive routing.
To satisfy the 99.99% SLA requirement, Google Cloud requires a 99.99% SLA topology for Dedicated Interconnect consisting of four VLAN attachments provisioned across two distinct metropolitan locations and two Edge Availability Domains per metro. Because Cloud Interconnect does not natively encrypt packets, running HA VPN over Cloud Interconnect provides the mandatory IPsec encryption. Furthermore, because VPC Network Peering does not support transitive routing for hybrid connections, on-premises traffic arriving at the landing VPC cannot reach a peered VPC directly through peering; deploying HA VPN tunnels between the landing VPC and the backend VPC provides an overlay L3 routing path to enable transitive traffic.

Step-by-Step Solution

1
Evaluate the physical hybrid connectivity requirements for 99.99% SLA and encryption.
Identified that GCP requires 4 Dedicated Interconnect VLAN attachments across 2 metros and 2 EADs per metro for 99.99% SLA, and HA VPN over Interconnect to provide IPsec encryption.
Dedicated Interconnect by itself does not encrypt traffic at rest/transit via IPsec, and single-metro or VPN-only setups cannot guarantee a 99.99% SLA.
2
Analyze multi-VPC reachability from on-premises across peered VPC networks.
Recognized that VPC Network Peering is non-transitive and cannot route on-premises traffic from `vpc-hub` into `vpc-partner`.
GCP VPC Peering explicitly prevents transit traffic originating from VPN or Interconnect links unless an overlay mechanism like HA VPN or Network Connectivity Center is configured between the VPCs.
3
Select the correct combination of architectural implementations.
Configured dual-metro 4-attachment Dedicated Interconnect with HA VPN over Interconnect, alongside an HA VPN connection between `vpc-hub` and `vpc-partner`.
This combination satisfies SLA, security/encryption, and multi-VPC transit constraints according to Google Cloud best practices.

Key Concept

Configuring 99.99% SLA Hybrid Connectivity with HA VPN over Interconnect and resolving VPC Peering Transitivity limits
Question 446Question

An enterprise organization is configuring a global Shared VPC network on Google Cloud spanning the us-central1 and europe-west1 regions. On-premises data centers are connected to us-central1 via a pair of Dedicated Interconnect attachments with BGP sessions established on regional Cloud Routers. Workloads deployed in europe-west1 require low-latency connectivity to on-premises databases, and workloads in both regions must seamlessly reach internal load balancers deployed in either region. The network administration team must ensure optimal route propagation across all regions without introducing unnecessary VPN overlays or invalid routing assumptions. Which VPC network topology configuration meets these requirements?

Show answer & explanation

Answer: Set the Shared VPC dynamic routing mode to Global, enabling Cloud Routers in us-central1 to dynamically propagate learned on-premises BGP routes across all regions to instances in europe-west1.

Answer

Setting the Shared VPC dynamic routing mode to Global allows regional Cloud Routers to automatically propagate on-premises routes globally to all subnets across regions.
Enabling Global Dynamic Routing on a GCP Virtual Private Cloud (VPC) network configures Cloud Routers to advertise and propagate learned BGP routes across all regions within that VPC. This enables instances in europe-west1 to seamlessly communicate with on-premises networks via the Dedicated Interconnect attached in us-central1 without extra tunnels or complex routing architectures.

Step-by-Step Solution

1
Analyze the network requirement for cross-region route propagation from Dedicated Interconnect.
Identified that Dedicated Interconnect BGP sessions terminate on regional Cloud Routers in us-central1.
By default, Regional Dynamic Routing limits route learning to resources in the same region as the Cloud Router.
2
Evaluate GCP VPC dynamic routing modes.
Global Dynamic Routing enables Cloud Routers to share learned routes with resources in all regions of the VPC network.
This allows workloads in europe-west1 to natively use on-premises routes learned by Cloud Routers in us-central1.
3
Verify inter-region internal load balancer access.
Global Dynamic Routing also allows internal HTTP(S) and L4 internal load balancers to be accessed globally within the same VPC network.
Global access settings combined with Global Dynamic Routing satisfy all multi-region connectivity criteria cleanly.

Key Concept

VPC Global Dynamic Routing and Route Propagation
Estimated Time:3m 0s
Question 447Question

An enterprise operations team is configuring log routing from a production Google Cloud project to a centralized security project containing a BigQuery dataset for audit compliance. After creating the project-level Cloud Logging sink with a BigQuery dataset target, log entries are not appearing in the target dataset due to permission errors. You need to resolve the ingestion failure while adhering to Google Cloud security best practices and the principle of least privilege. Which action should you take?

Show answer & explanation

Answer: Grant the BigQuery Data Editor role on the target dataset to the service account writer identity generated by the Cloud Logging sink.

Answer

Grant the BigQuery Data Editor role on the target dataset to the service account writer identity generated by the Cloud Logging sink.
When a Cloud Logging sink exports logs to a destination in another project (such as BigQuery), Cloud Logging creates a dedicated writer service account. Granting the BigQuery Data Editor role specifically on the destination dataset grants the sink the necessary permissions to write log tables while strictly honoring least-privilege security guidelines.

Step-by-Step Solution

1
Identify the writer identity associated with the Cloud Logging sink
Obtain the unique service account email generated by Cloud Logging for the sink (e.g., [email protected] or [email protected]).
Cloud Logging sinks use resource-based service accounts to authenticate log export destinations.
2
Determine the minimal IAM permissions needed on the BigQuery destination dataset
Identify that `roles/bigquery.dataEditor` provides dataset write access without exposing extra project-wide privileges.
Following least privilege ensures that the writer identity can only insert tables and stream data into the target dataset.
3
Apply the IAM role at the dataset level
Grant the writer identity the BigQuery Data Editor role directly on the target BigQuery dataset resource.
Dataset-scoped IAM access satisfies security requirements and allows the Cloud Logging sink to successfully route incoming log entries.

Key Concept

Cloud Logging Sink Writer Identity Permission Configuration
Question 448Question

A network administrator needs to connect an on-premises location to a Google Cloud Virtual Private Cloud (VPC) using an HA Cloud VPN gateway with dynamic routing over the public internet. Which TWO configuration steps or requirements are necessary to implement this solution? (Select TWO answers)

Select all that apply

Show answer & explanation

Answer: Deploy a Cloud Router in the target VPC region to exchange dynamic routes via Border Gateway Protocol (BGP).; Configure two IPsec VPN tunnels from the HA Cloud VPN gateway interfaces to the on-premises VPN device.

Answer

The correct requirements are configuring Cloud Router with BGP for dynamic routing and configuring two IPsec VPN tunnels from the HA Cloud VPN gateway interfaces.
Deploying an HA Cloud VPN requires configuring Cloud Router to manage dynamic BGP route exchanges and establishing two IPsec VPN tunnels using the dual interfaces on the HA gateway to guarantee topology redundancy and SLA compliance.

Step-by-Step Solution

1
Identify the routing requirement for HA Cloud VPN
Recognize that HA Cloud VPN strictly requires dynamic routing via Cloud Router running BGP.
HA Cloud VPN topologies rely on Cloud Router to automatically adjust route paths in case of tunnel failure.
2
Identify the gateway interface requirement for high availability
Recognize that HA Cloud VPN gateways feature two interfaces (interface 0 and interface 1), requiring two IPsec tunnels.
Two active VPN tunnels connected to an on-premises router (or twin routers) ensure SLA compliance and continuous connectivity.

Key Concept

HA Cloud VPN Topology and BGP Dynamic Routing
Question 449Question

An enterprise fintech organization is designing an automated continuous deployment pipeline using Cloud Build and Google Cloud Deploy to release microservices across multiple Google Kubernetes Engine (GKE) clusters. To comply with regulatory security auditing and zero-trust policies, the organization mandates that deployment pipelines must eliminate long-lived service account keys and adhere strictly to the principle of least privilege. The build runner service account requires authorization to execute deployment actions on behalf of a dedicated deployment service account without gaining overall administrative privileges. Which IAM configuration strategy should the cloud architect implement to fulfill these requirements securely?

Show answer & explanation

Answer: Grant the build runner service account the Service Account User role (`roles/iam.serviceAccountUser`) on the specific deployment service account to allow identity impersonation.

Answer

Grant the build runner service account the Service Account User role (`roles/iam.serviceAccountUser`) on the specific deployment service account to allow identity impersonation.
The option specifying to grant the Service Account User role (`roles/iam.serviceAccountUser`) on the specific deployment service account allows the build agent to impersonate the target deployment identity securely. This pattern avoids exported key files and adheres strictly to the principle of least privilege required in enterprise release pipelines.

Step-by-Step Solution

1
Analyze security and governance requirements for automated CI/CD pipeline execution.
Identified the requirement to execute deployments under a dedicated identity without creating long-lived service account keys or over-granting administrative roles.
Enterprise compliance requires strict adherence to the principle of least privilege and short-lived credentials.
2
Evaluate Google Cloud IAM mechanisms for service account identity delegation.
Determined that service account impersonation allows one identity (the build runner) to act on behalf of another target identity (the deployment service account).
Impersonation eliminates the need for exported JSON keys and maintains full auditability in Cloud Audit Logs.
3
Identify the minimum required IAM role for service account impersonation.
Selected the Service Account User role (`roles/iam.serviceAccountUser`) scoped specifically to the deployment service account.
This permission permits the runner to attach or impersonate the target identity without conferring administrative privileges over service accounts.

Key Concept

Service Account Impersonation and Least Privilege in CI/CD Pipelines
Estimated Time:2m 0s
Question 450Question

An operations engineering team needs to configure automated incident notifications based on specific error logs emitted by a workload running on Google Cloud. Order the steps required to establish a complete log-based alerting pipeline following Google Cloud observability best practices, starting from raw log evaluation to operational notification.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence is: 1) Construct a precise filter expression in Cloud Logging, 2) Define a custom log-based metric, 3) Configure an alerting policy in Cloud Monitoring using the custom metric, and 4) Attach notification channels to the alerting policy.
To create operational alerts driven by specific log occurrences, you must first define a filter expression in Cloud Logging to pinpoint the error logs. Next, transform those log events into numeric metric data by creating a custom log-based metric. Once the metric is ingested by Cloud Monitoring, construct an alerting policy that evaluates the metric against operational thresholds. Finally, associate notification channels with the alerting policy so that responders receive notifications when an incident is opened.

Step-by-Step Solution

1
Filter target logs in Cloud Logging
Relevant log entries matching the application failure criteria are isolated.
Cloud Logging requires a scope-limiting filter query to extract relevant log events from incoming log streams.
2
Create a log-based metric
Log occurrences are published as a time-series metric stream into Cloud Monitoring.
Cloud Monitoring alerting policies operate on numeric time-series metrics, not directly on text log records.
3
Create an alerting policy in Cloud Monitoring
An operational policy continuously checks the metric rate against defined thresholds.
Alerting policies evaluate conditions over specified time windows to detect incidents.
4
Associate notification channels
Operational alerts are automatically routed to team notification endpoints upon incident trigger.
Notification channels define target destinations (such as Slack, Email, or PagerDuty) for alert delivery.

Key Concept

Configuring Cloud Logging log-based metrics and Cloud Monitoring alerting workflows
Question 451Question

A retail enterprise is standardizing its cloud deployment framework on Google Cloud. The infrastructure architecture requires deploying new GKE clusters alongside Compute Engine Managed Instance Groups (MIGs) via an automated Infrastructure as Code (IaC) CI/CD pipeline. The security and operations policy dictates strict access controls to cluster control planes, least-privilege identity delegation for deployment workers, and prevention of concurrent deployment state corruption across 1515 distinct feature teams. Which THREE configuration standards should the architecture team enforce in their provisioning blueprint? (Select 3 choices)

Select all that apply

Show answer & explanation

Answer: Provision GKE clusters as Private Clusters and configure Control Plane Authorized Networks restricted exclusively to management subnet CIDR ranges.; Grant the deployment pipeline service account the Service Account User role (roles/iam.serviceAccountUser) on the specific compute runtime service accounts.; Store Terraform infrastructure state in a remote Cloud Storage backend configured with Object Versioning and state locking.

Answer

The correct architectural choices are: (1) Provisioning GKE clusters as Private Clusters with Control Plane Authorized Networks configured to restrict access to trusted internal IP ranges, (2) Assigning the Service Account User role to the deployment pipeline service account on runtime identities, and (3) Storing Terraform state in a remote Cloud Storage backend with Object Versioning and state locking enabled.
The solution requires a secure, automated, and maintainable compute provisioning architecture. Private GKE clusters with Control Plane Authorized Networks secure the Kubernetes control plane from unauthorized network access. Assigning `roles/iam.serviceAccountUser` provides the automated pipeline with exact privileges needed to run resources under specified runtime identities without administrative over-privilege. Using a Cloud Storage backend with state locking and Object Versioning ensures safe multi-team IaC collaboration.

Step-by-Step Solution

1
Analyze Kubernetes Engine cluster control plane exposure requirements.
GKE Private Clusters keep worker node IP addresses non-routable over the public internet, and Control Plane Authorized Networks restrict master endpoint communication to specified internal management CIDR ranges.
This satisfies corporate security mandates to prevent untrusted access to Kubernetes API endpoints.
2
Evaluate IAM privilege bounds for automated deployment infrastructure.
Deployment service accounts require permission to bind runtime service accounts to Compute Engine instances or GKE node pools, which is granted via `roles/iam.serviceAccountUser`.
Granting `roles/iam.serviceAccountUser` follows least privilege, whereas granting primitive roles like Editor or Service Account Admin creates severe privilege escalation vectors.
3
Select state management and concurrency controls for multi-team IaC provisioning.
A central Cloud Storage backend with native state locking and versioning prevents concurrent state writes and allows state restoration.
Preventing simultaneous pipeline runs from writing to local unversioned state files eliminates state corruption across 1515 feature teams.

Key Concept

Enterprise provisioning standards for GKE cluster security, IAM service account user delegation, and Terraform remote state lock management.
Question 452Question

In Google Cloud Platform (GCP), IAM permissions are inherited downward through the resource hierarchy structure. How should an architect sequence the GCP resource hierarchy levels in order of policy inheritance, starting from the highest level (broadest policy scope) down to the lowest level (most narrow policy scope)?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of the GCP resource hierarchy from broadest scope to most granular scope is: Organization node, Folder node, Project node, and Individual Resource.
In Google Cloud Platform, IAM policies are inherited transitively from parent to child. The resource hierarchy flows downwards starting from the Organization (root node), through Folders (grouping containers), to Projects (service boundaries), and finally to Individual Resources (leaf elements).

Step-by-Step Solution

1
Identify the root node of the GCP resource hierarchy.
The Organization node is established as position 1.
The Organization node represents the root level, and policies applied here inherit down to all child nodes in the enterprise.
2
Identify the intermediate grouping container node.
The Folder node is established as position 2.
Folders are created directly under the Organization node to group projects and sub-folders for departmental or environment governance.
3
Identify the service and billing boundary container node.
The Project node is established as position 3.
Projects sit inside Folders and act as the core administrative boundary for enabling GCP APIs, services, and billing.
4
Identify the leaf node containing specific GCP service components.
The Individual Resource is established as position 4.
Resources (such as BigQuery datasets or GCS buckets) reside within projects at the lowest level of the resource hierarchy.

Key Concept

GCP IAM Resource Hierarchy Policy Inheritance
Estimated Time:45s
Question 453Question

A cloud operations team needs to deploy a new PostgreSQL database on Google Cloud using Cloud SQL and populate it using a local database dump file. What is the correct sequence of steps to provision the storage staging environment, transfer the dump, and populate the database?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins by creating a Cloud Storage staging bucket, uploading the local database dump file to the bucket, provisioning the Cloud SQL instance, and finally granting IAM permissions to the Cloud SQL service account to execute the import job.
Provisioning database resources on Google Cloud when starting from a local dump requires a staging location. First, a Cloud Storage bucket is created to host the dump file. Second, the dump file is uploaded from the local environment into the bucket. Third, the Cloud SQL database instance is provisioned. Finally, the service account assigned to the Cloud SQL instance is granted permissions on the Cloud Storage bucket so the import operation can execute successfully.

Step-by-Step Solution

1
Create the staging storage bucket
A Cloud Storage bucket is available to receive object uploads.
Cloud SQL import operations require data to be hosted in Cloud Storage.
2
Upload the database dump file to Cloud Storage
The file is stored in Google Cloud and ready for Cloud SQL access.
Local files cannot be imported directly into Cloud SQL without first residing in a staging bucket.
3
Provision the Cloud SQL database instance
The database server is instantiated and running.
Target infrastructure must exist to accept the imported data schema and records.
4
Authorize the service account and run the import job
The database instance is populated with the staging data.
Cloud SQL uses its service account to read from Cloud Storage, requiring explicit IAM access prior to running the import.

Key Concept

Provisioning Cloud SQL and Cloud Storage staging pipelines
Question 454Question

Your organization is establishing standardized Google Cloud Deployment Manager practices for provisioning cloud infrastructure across development environments. You need to create a reusable configuration and safely deploy it. In what order should you execute the steps to construct, validate, preview, and commit the deployment?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts with authoring the Jinja2/Python template and schema file, followed by building the top-level YAML configuration file. Next, execute the deployment creation with the --preview flag to validate proposed changes without provisioning, and finally run the deployment update command to commit and instantiate the infrastructure.
The correct workflow for managing complex Cloud Deployment Manager configurations starts at authoring reusable Jinja2 or Python templates with schemas to validate input properties. Once templates exist, a top-level YAML configuration imports them and sets environment variables. Using the Cloud SDK with the preview flag renders the proposed graph without creating resources, allowing verification. Finally, updating the previewed deployment commits the configuration to provision resources in Google Cloud.

Step-by-Step Solution

1
Define reusable template and schema files.
Establishes parameterized resource logic and strict input validation rules.
Deployment Manager requires underlying template definitions and schema parameters to exist before top-level configurations can reference them.
2
Construct the main YAML configuration file.
Passes specific environment variables into the imported templates.
The YAML configuration acts as the entry point that binds input variables to the schema-validated templates.
3
Run `gcloud deployment-manager deployments create --config <config.yaml> --preview`.
Renders and displays the complete resource manifest in a preview state without making resource allocations.
Previewing ensures architectural correctness and prevents unintended infrastructure changes before provisioning.
4
Run `gcloud deployment-manager deployments update <deployment-name>`.
Provisions and updates the actual Google Cloud infrastructure resources based on the previewed state.
This final command transforms the previewed allocation plan into active infrastructure.

Key Concept

Cloud Deployment Manager Template Lifecycle and Preview Operations
Question 455Question

A global healthcare provider is translating its enterprise conceptual architecture into logical and physical cloud designs on Google Cloud. The architecture requires streaming ingestion of high-frequency IoT patient telemetry data, a globally consistent database supporting multi-region ACID transactions for clinical trial records, private service consumption between isolated line-of-business Virtual Private Clouds (VPCs) without exposing underlying network subnets or relying on transitive routing, and strict controls to prevent authorized internal users from exfiltrating data to external locations. Which physical architecture design correctly satisfies all conceptual and logical requirements while adhering to Google Cloud best practices?

Show answer & explanation

Answer: Deploy Pub/Sub and Cloud Dataflow for streaming ingestion, Cloud Spanner for multi-region transactional data storage, Private Service Connect for cross-VPC service communication, and a VPC Service Controls perimeter encompassing the GCP projects.

Answer

Deploy Pub/Sub and Cloud Dataflow for streaming ingestion, Cloud Spanner for multi-region transactional data storage, Private Service Connect for cross-VPC service communication, and a VPC Service Controls perimeter encompassing the GCP projects.
The architecture combining Pub/Sub, Dataflow, Cloud Spanner, Private Service Connect, and VPC Service Controls correctly maps all conceptual requirements to physical GCP services while enforcing enterprise security boundaries and scalability.

Step-by-Step Solution

1
Analyze the conceptual transactional database requirement for multi-region ACID writes.
Cloud Spanner is identified as the required physical relational storage service, as Cloud SQL does not support multi-region synchronous writes.
Global clinical trial data requires multi-region consistency and strong ACID semantics across regions.
2
Analyze the cross-VPC networking requirement for private service consumption without transitive routing or subnet exposure.
Private Service Connect (PSC) is selected to expose services privately using internal IP endpoints across VPC boundaries.
VPC Network Peering does not support transitive routing and exposes entire subnet spaces, whereas PSC abstracts underlying networks.
3
Analyze the data security and exfiltration prevention requirement.
VPC Service Controls is selected to establish a security perimeter around GCP project resources.
IAM roles alone cannot prevent authenticated users from copying data to non-approved storage locations outside the project perimeter.
4
Map the streaming ingestion logical requirement to managed physical services.
Pub/Sub combined with Cloud Dataflow provides serverless, auto-scaling stream processing.
High-frequency IoT device telemetry requires decoupled message queuing and unified pipeline processing.

Key Concept

Mapping conceptual business and operational requirements to physical GCP architectural components across data, networking, and security tiers.
Estimated Time:3m 0s
Question 456Question

An enterprise architecture team is transitioning a critical Google Cloud infrastructure codebase from local execution to a centralized, collaborative Terraform model. To meet corporate security and operational standards, the team must migrate the local state file to a secure Google Cloud Storage (GCS) remote backend featuring state locking and least-privilege service account impersonation. Sequence the steps required to execute this state backend migration safely and correctly.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence begins with provisioning and securing the target GCS bucket, adding the remote backend definition to the HCL configuration, establishing least-privilege service account impersonation, executing terraform init to migrate the state under state locks, and finally validating state integrity with terraform plan.
Migrating Terraform state safely requires creating the secured GCS storage resource first, configuring HCL backend settings, establishing IAM impersonation credentials, running terraform init to perform state transfer under state locks, and executing terraform plan to confirm operational readiness.

Step-by-Step Solution

1
Provision and secure the Google Cloud Storage bucket
A target GCS bucket exists with Object Versioning and uniform bucket-level access enabled to protect state integrity.
The GCS storage location must exist and be secured prior to pointing Terraform to it.
2
Configure the HCL backend block
The Terraform code declares the gcs backend with the target bucket and prefix.
Terraform needs backend configuration metadata to know where state data should be written.
3
Set up least-privilege Service Account impersonation
Authentication relies on short-lived service account tokens instead of persistent service account key files.
Impersonation must be configured before invoking initialization so state storage operations run under the correct identity.
4
Initialize the backend and migrate state
Terraform acquires a state lock on GCS and transfers the state content from local storage to the bucket.
The terraform init command detects backend changes and performs interactive or automated state migration.
5
Validate remote state operations
Terraform plan acquires the GCS lock, reads state, confirms zero unexpected drift, and releases the lock.
Post-migration verification ensures that remote lock acquisition works as expected and state corruption did not occur.

Key Concept

Remote Terraform State Management with GCS, Object Versioning, State Locking, and Service Account Impersonation
Question 457Question

A global financial analytics firm plans to launch nightly batch processing jobs in Google Cloud to process high-frequency market telemetry data. The batch workload requires automated provisioning of 250 GPU-accelerated Compute Engine instances in a single region (us-central1) using Infrastructure as Code pipelines. During initial test runs, the pipeline execution fails during instance creation due to insufficient GPU resource limits, despite the project having an active billing account with high credit limits. Furthermore, organizational security policy strictly dictates that automated deployment pipelines must adhere to least privilege and cannot hold security administration roles. Which combination of architectural and operational steps should the Cloud Architect execute to resolve the deployment failures while maintaining security compliance?

Show answer & explanation

Answer: Submit a regional GPU quota increase request for us-central1 prior to provisioning, and grant the deployment pipeline service account the Service Account User role (roles/iam.serviceAccountUser) alongside compute provisioning permissions.

Answer

Submit a regional GPU quota increase request for us-central1 prior to provisioning, and grant the deployment pipeline service account the Service Account User role (roles/iam.serviceAccountUser) alongside compute provisioning permissions.
Submitting a regional GPU quota request in us-central1 ahead of deployment ensures GCP allocates sufficient hardware capacity for the workload. In addition, granting the deployment pipeline identity the Service Account User role (roles/iam.serviceAccountUser) allows it to assign runtime service accounts to virtual instances without granting broad administrative security rights, fulfilling least-privilege requirements.

Step-by-Step Solution

1
Diagnose the root cause of compute provisioning failures during pipeline execution
Identify that compute resource instantiation is failing due to regional GPU quota limits, which operate independently of project billing thresholds.
Regional quota caps prevent unexpected resource consumption and require explicit administrative increase requests before scaling up compute capacity.
2
Determine minimal IAM permissions required for automated compute instance creation
Establish that the pipeline identity only needs permission to attach designated runtime service accounts to Compute Engine instances.
Attaching service accounts to virtual machines requires roles/iam.serviceAccountUser, preserving security boundaries without granting administrative control.
3
Align quota management and IAM scoping into the deployment strategy
Pre-request regional quotas in us-central1 and configure the pipeline service account with minimal IAM roles.
This guarantees reliable infrastructure provisioning while strictly enforcing organizational compliance requirements.

Key Concept

Compute Resource Quotas and Least-Privilege IAM Provisioning
Estimated Time:2m 0s
Question 458Question

A software company needs to deploy a stateless HTTP microservice packaged as a container image on Google Cloud. The solution must require zero cluster infrastructure management overhead and automatically scale down to zero instances when no traffic is received. Which TWO options represent the optimal design choices for this requirement?

Select all that apply

Show answer & explanation

Answer: Deploy the containerized service to Cloud Run to achieve automatic scaling to zero without managing underlying cluster infrastructure.; Configure request concurrency settings on Cloud Run so that each instance can process multiple simultaneous HTTP requests.

Answer

Deploying the service to Cloud Run and configuring request concurrency settings on Cloud Run.
Cloud Run is the optimal serverless compute platform for stateless containerized HTTP microservices. It automatically scales down to zero instances when traffic stops and removes all cluster management overhead. Furthermore, configuring concurrency allows each Cloud Run container instance to process multiple HTTP requests simultaneously, optimizing compute efficiency and lowering costs.

Step-by-Step Solution

1
Analyze workload requirements
Stateless HTTP containerized service needing zero cluster management overhead and scaling to zero.
Aligning operational criteria with Google Cloud compute platform features.
2
Evaluate GCP serverless compute options
Cloud Run natively executes custom container images, scales to zero during idle periods, handles multiple concurrent requests per instance, and requires no infrastructure management.
Cloud Run minimizes operational overhead and optimizes resource usage for stateless HTTP microservices.

Key Concept

Cloud Run Platform Selection for Stateless Containerized Workloads
Question 459Question

An organization needs to establish direct, low-latency private IP connectivity between two VPC networks (vpc-a and vpc-b) in Google Cloud without traversing the public internet or deploying hybrid VPN gateways. Which GCP networking configuration should be implemented to enable internal communication between resources in both VPCs?

Show answer & explanation

Answer: Establish a VPC Network Peering connection directly between vpc-a and vpc-b.

Answer

Establish a VPC Network Peering connection directly between vpc-a and vpc-b.
Establishing a direct VPC Network Peering connection enables private RFC 1918 network connectivity between both VPC networks over Google's internal network backbone without public IP routing or VPN infrastructure.

Step-by-Step Solution

1
Identify the primary networking requirement
The requirement calls for direct, private RFC 1918 communication between two Google Cloud VPC networks without public internet routing or VPN overhead.
Google Cloud VPC Network Peering allows private IP address connectivity across distinct VPC networks using Google's internal network infrastructure.
2
Evaluate inter-VPC connectivity features
Direct VPC Network Peering provides full internal IP reachability with low latency and high bandwidth.
Direct VPC Peering is the simplest and most efficient mechanism for linking two separate VPC networks within Google Cloud.

Key Concept

VPC Network Peering capabilities and non-transitive routing behavior
Question 460Question

An enterprise healthcare platform is provisioning a mission-critical Cloud SQL PostgreSQL database instance to store sensitive patient telemetry data. Corporate security policy mandates that data at rest must be encrypted using encryption keys that support automated 90-day key rotation, provide complete centralized key access auditing in Cloud Audit Logs, and require zero raw cryptographic key material handling by the application layer. Which configuration should the cloud architect specify during initial database provisioning to satisfy all requirements?

Show answer & explanation

Answer: Provision the database instance using Customer-Managed Encryption Keys (CMEK) via Cloud KMS, and grant the Cloud SQL service account the CryptoKey Encrypter/Decrypter role on the specified key.

Answer

Provision the database instance using Customer-Managed Encryption Keys (CMEK) via Cloud KMS, and grant the Cloud SQL service account the CryptoKey Encrypter/Decrypter role on the specified key.
Provisioning the database with Customer-Managed Encryption Keys (CMEK) via Cloud KMS allows organization administrators to establish automated 90-day key rotation schedules, track key access in Cloud Audit Logs, and grant permissions via IAM roles without exposing raw key material to the application tier. Granting the Cloud SQL service account the CryptoKey Encrypter/Decrypter role ensures the database engine can encrypt and decrypt data at rest seamlessly.

Step-by-Step Solution

1
Analyze compliance requirements for database encryption
Identify need for automated 90-day rotation, centralized Cloud Audit Log integration, and zero application handling of raw key material.
Choosing the correct GCP encryption model depends on where key management responsibility and key material handling reside.
2
Compare Google Cloud encryption options (Default, CMEK, CSEK)
CMEK allows Cloud KMS key management with automated rotation schedules and IAM-controlled service account access without application key exposure.
CSEK requires application-managed raw keys for every API operation, whereas CMEK delegates cryptographic operations to Cloud KMS.
3
Determine necessary IAM role bindings for database provisioning
Grant the Cloud SQL service account (`[email protected]`) the `roles/cloudkms.cryptoKeyEncrypterDecrypter` role on the KMS key.
Cloud SQL requires explicit service account permissions to wrap and unwrap database encryption keys via Cloud KMS.

Key Concept

Provisioning databases with Customer-Managed Encryption Keys (CMEK) in Google Cloud
PreviousPage 23 / 80Next
All practice questions — Google Cloud Professional Cloud Architect | Examkin