All practice questions

1591 questions

Question 421Question

An organization is setting up detailed cost analytics and needs to export daily Cloud Billing data to a BigQuery dataset located in a central management project. A cloud engineer has already been granted the BigQuery Data Editor role on the destination project and dataset, but receives a permission denied error when attempting to configure the BigQuery export sink in the Google Cloud Console. Which Identity and Access Management (IAM) role must be assigned to the engineer on the Cloud Billing account to successfully complete this export setup?

Show answer & explanation

Answer: Billing Account Costs Manager

Answer

The Billing Account Costs Manager role must be assigned on the Cloud Billing account.
Setting up BigQuery billing exports requires permissions across two separate resource levels. The user needs BigQuery dataset write access (such as BigQuery Data Editor) on the destination project AND billing administrative access (specifically Billing Account Administrator or Billing Account Costs Manager) on the Cloud Billing account.

Step-by-Step Solution

1
Analyze the resource boundaries involved in exporting billing data to BigQuery.
BigQuery billing exports span two distinct GCP resource levels: the Cloud Billing account (where data originates) and the GCP Project/BigQuery Dataset (where data is written).
Permissions on the target project alone (such as BigQuery Data Editor) do not grant authorization to modify billing account export settings.
2
Determine the required role on the Cloud Billing account.
The user must possess either the Billing Account Administrator or Billing Account Costs Manager role directly on the Cloud Billing account.
These predefined roles contain the necessary permissions (billing.accounts.update) to select and link a BigQuery dataset for export.

Key Concept

Configuring Cloud Billing BigQuery export requires administrative or cost management roles on the Cloud Billing account resource in addition to dataset permissions on the target BigQuery project.
Question 422Question

A centralized accounting department manages a primary Google Cloud Billing Account for your company. To support decentralized resource deployment, project managers require the ability to associate their newly created Google Cloud projects with this central billing account. However, organizational security policies mandate that project managers must not be allowed to view invoice payment histories, change billing account settings, or manage billing permissions. Which IAM role should be assigned to the project managers on the billing account to satisfy these requirements while adhering to the principle of least privilege?

Show answer & explanation

Answer: Billing Account User (roles/billing.user)

Answer

Billing Account User (roles/billing.user)
The Billing Account User (roles/billing.user) role provides users with the precise permission needed to link projects to a billing account (resourcemanager.projects.createBillingAssignment) without exposing billing transaction history, credit card details, or administrative settings.

Step-by-Step Solution

1
Identify the operation being performed
The operation is associating (linking) a newly created Google Cloud project to an existing Billing Account.
Linking a project requires permission on both the project (Project Creator/Owner) and the target Billing Account.
2
Analyze permission boundaries on the Billing Account
The requirement mandates granting only the ability to link projects without allowing access to view financial invoices or modify billing management settings.
Least privilege dictates selecting a predefined role tailored specifically to project-to-billing association.
3
Select the appropriate IAM role on the Billing Account resource
Billing Account User (roles/billing.user) provides the exact permission (resourcemanager.projects.createBillingAssignment) needed to link projects without extra privileges.
Billing Account Viewer lacks assignment rights, Billing Account Administrator is overly permissive, and project-level roles do not grant permissions on the Billing Account resource.

Key Concept

Least Privilege Billing Account IAM Role Assignment
Question 423Question

A cloud engineer is configuring command-line administration and compute resources for a stateless, fault-tolerant batch data processing pipeline on Google Kubernetes Engine (GKE). The target cluster `analytics-batch-cluster` is deployed in region `us-central1`. Which TWO configuration steps must the engineer perform?

Select all that apply

Show answer & explanation

Answer: Execute `gcloud container clusters get-credentials analytics-batch-cluster --region us-central1` to populate local kubeconfig authentication context.; Provision a dedicated node pool utilizing Spot VMs for batch workloads and ensure pod specifications contain tolerations for node preemption taints.

Answer

The correct configuration steps are to execute `gcloud container clusters get-credentials analytics-batch-cluster --region us-central1` to set up kubeconfig credentials, and to provision a Spot VM node pool with pod preemption tolerations for fault-tolerant batch processing.
To establish control plane access, `gcloud container clusters get-credentials` must be executed to populate local `kubeconfig` entries. For cost-effective batch computing, Spot VM node pools paired with pod preemption tolerations provide the recommended Google Cloud pattern for fault-tolerant workloads.

Step-by-Step Solution

1
Authenticate local CLI tools to the regional GKE cluster
Local kubeconfig context is populated with API server endpoint and credentials
Running `gcloud container clusters get-credentials` is required to enable `kubectl` to communicate with the GKE control plane.
2
Configure node pool architecture for stateless batch workloads
Spot VM node pool is provisioned with preemption taints
Spot VMs significantly reduce compute costs for fault-tolerant workloads when pods tolerate preemption taints.

Key Concept

GKE Cluster Credential Retrieval and Node Pool Workload Optimization
Question 424Question

A cloud engineer manages a stateless application deployed as a Kubernetes Deployment on a Google Kubernetes Engine (GKE) cluster. During peak business hours, CPU usage increases significantly. The engineer needs to automatically scale the number of running application Pods up or down based on CPU utilization metrics. Which Kubernetes resource should the engineer configure?

Show answer & explanation

Answer: HorizontalPodAutoscaler

Answer

The HorizontalPodAutoscaler (HPA) resource should be configured to scale the number of Pod replicas based on CPU utilization.
The HorizontalPodAutoscaler (HPA) automatically adjusts the number of Pod replicas in a Deployment based on targeted metrics such as CPU utilization.

Step-by-Step Solution

1
Identify the requirement
The requirement is to automatically scale the number of application Pods (workload replicas) in response to CPU utilization metrics.
Scaling Pod count requires a workload-level autoscaler rather than node-level infrastructure management.
2
Evaluate Kubernetes scaling mechanisms
HorizontalPodAutoscaler monitors Pod metrics (like target CPU utilization percentage) and adjusts the Deployment's replica count accordingly.
HPA is specifically designed for scaling container workloads horizontally.

Key Concept

Horizontal Pod Autoscaler vs. Cluster Autoscaler in GKE
Question 425Question

A logistics enterprise is designing a Google Kubernetes Engine (GKE) cluster architecture to host a real-time tracking system containing two workloads:
1. A stateless API service that ingests location updates continuously.
2. A batch analytics engine that processes bulk telemetry data, can easily recover from unexpected instance terminations, and requires specialized Linux kernel parameters (`sysctl` network tuning) configured at the node OS level.

Which cluster configuration strategy satisfies all technical and operational requirements while optimizing node management and compute costs?

Show answer & explanation

Answer: Deploy a single GKE Standard cluster with a standard node pool of regular Compute Engine instances for the stateless API service, and a separate node pool using Spot VMs with custom node configuration scripts to apply the required sysctl parameters for the batch analytics engine.

Answer

Deploy a single GKE Standard cluster with a standard node pool of regular Compute Engine instances for the stateless API service, and a separate node pool using Spot VMs with custom node configuration scripts to apply the required sysctl parameters for the batch analytics engine.
GKE Standard is required when workloads demand low-level node OS customizations, such as custom sysctl parameters. Creating separate node pools within a single GKE Standard cluster allows the stateless API service to run reliably on regular instances while leveraging Spot VMs for the fault-tolerant batch analytics workload to optimize costs.

Step-by-Step Solution

1
Evaluate operational boundaries between GKE Autopilot and GKE Standard
GKE Autopilot locks down node OS level access and prevents custom sysctl kernel parameter modifications. Therefore, GKE Standard must be selected.
The batch analytics engine requires custom Linux kernel sysctl parameters applied at the node level.
2
Determine node pool strategies for compute cost vs. availability
Use regular instances for the API ingestion service and Spot VMs for the fault-tolerant batch workload.
Spot VMs provide significant cost savings for workloads that tolerate unexpected node preemptions, whereas the stateless API ingestion service requires stable, non-preemptible nodes.
3
Verify cluster node pool compatibility in GKE
A single GKE Standard cluster supports multiple heterogenous node pools (standard VM node pool + Spot VM node pool with custom configurations).
Combining node pool types within one Standard cluster avoids multi-cluster management overhead while supporting distinct node requirements.

Key Concept

Selecting between GKE Standard and Autopilot based on node OS modification constraints and leveraging specialized node pools for cost optimization
Question 426Question

An enterprise is planning a high-availability multi-region network architecture on Google Cloud. The workload requirements specify:
1. Global HTTPS web traffic must support edge caching for static assets and path-based routing to Compute Engine managed instance groups deployed in both `us-central1` and `europe-west3`.
2. Internal microservice RPC traffic running a non-HTTP raw TCP protocol on port 8443 within `us-central1` must be load-balanced with minimal latency across private Compute Engine instances without exposing public IP addresses.

Which TWO load balancing and network service configurations should you select to fulfill these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploy a Global External Application Load Balancer with Cloud CDN enabled on the backend services for the web application.; Deploy an Internal Passthrough Network Load Balancer in us-central1 for the internal raw TCP microservice backends.

Answer

To satisfy the architectural requirements, deploy a Global External Application Load Balancer with Cloud CDN for global HTTPS traffic and static edge caching, and deploy an Internal Passthrough Network Load Balancer for private, low-latency Layer 4 TCP microservice traffic.
The solution requires two distinct load balancing tiers based on protocol and network scope. For public HTTPS traffic spanning multiple regions with edge caching requirements, a Global External Application Load Balancer integrated with Cloud CDN is mandatory. For private, high-performance microservices using a raw TCP protocol, an Internal Passthrough Network Load Balancer provides regional Layer 4 traffic distribution without exposing external IP endpoints.

Step-by-Step Solution

1
Analyze public web application requirements.
Requirements call for global HTTPS routing, multi-region backends, and edge caching.
Global External Application Load Balancer is the only Google Cloud load balancer that supports multi-region HTTP(S) backends with Cloud CDN edge caching.
2
Analyze internal microservices traffic requirements.
Requirements demand private IP load balancing for non-HTTP raw TCP traffic on port 8443 in us-central1.
Internal Passthrough Network Load Balancers provide high-performance Layer 4 load balancing using internal VPC IP addresses for non-HTTP protocols.

Key Concept

GCP Load Balancer Protocol and Scope Selection (L7 Global HTTP(S) vs L4 Internal Passthrough TCP)
Question 427Question

A network engineering lead at a financial institution is designing a multi-tier enterprise architecture in Google Cloud. The infrastructure requires dedicated Virtual Private Cloud (VPC) subnets across multiple regions for database clusters, web microservices, and internal administrative services. To enforce strict administrative segregation and prevent cross-team network provisioning errors, the security governance team dictates that IP address allocations must be explicitly controlled per subnet without automatic default subnet creation across all GCP regions. Furthermore, the architecture must support future IP space expansion without downtime, while maintaining isolation from legacy on-premises RFC 1918 addresses. Which VPC network design approach best satisfies these requirements?

Show answer & explanation

Answer: Create a custom-mode VPC network, explicitly defining subnets with tailored primary CIDR blocks in required regions, and leave auto-create subnets disabled.

Answer

Create a custom-mode VPC network with explicitly defined regional subnets and customized primary CIDR ranges.
Custom-mode VPC networks give full control over subnet creation. No subnets are created automatically, preventing unexpected IP range collisions with existing on-premises networks and enabling strict regional governance and precise IP planning.

Step-by-Step Solution

1
Analyze enterprise requirements
Identified requirements for explicit IP address management, regional subnet control, prevention of automatic region-wide subnet creation, and non-overlapping IP space with on-premises networks.
Enterprise hybrid environments require custom CIDR range selection to avoid overlapping with existing corporate IP space.
2
Evaluate GCP VPC network creation modes
Auto-mode automatically populates a predefined /20 subnet in every GCP region, whereas custom-mode creates zero subnets initially, giving complete control over subnet creation, regional placement, and CIDR sizing.
Custom-mode VPCs ensure compliance with strict organizational IP governance and facilitate seamless subnet expansion.
3
Select optimal architecture
Provisioning a custom-mode VPC network fulfills all administrative isolation, zero default subnet, and IP planning constraints.
Custom mode is the recommended best practice for enterprise production workloads.

Key Concept

VPC Network Modes and Subnet IP Planning
Estimated Time:2m 0s
Question 428Question

A cloud engineer needs to apply an automated lifecycle configuration policy file named `lifecycle.json` to an existing Google Cloud Storage bucket named `analytics-raw-data-prod`. According to Google Cloud CLI standards, which command should be executed to apply this lifecycle policy to the bucket?

Show answer & explanation

Answer: gcloud storage buckets update gs://analytics-raw-data-prod --lifecycle-file=lifecycle.json

Answer

Execute 'gcloud storage buckets update gs://analytics-raw-data-prod --lifecycle-file=lifecycle.json' to apply the lifecycle configuration file to the bucket.
The command 'gcloud storage buckets update gs://analytics-raw-data-prod --lifecycle-file=lifecycle.json' correctly uses the modern gcloud storage CLI interface to update bucket settings with a local JSON lifecycle specification file.

Step-by-Step Solution

1
Identify the resource scope for object lifecycle management
Object lifecycle management rules are defined at the bucket level and apply across objects stored in that bucket.
Lifecycle configuration settings cannot be applied directly to individual objects using object commands.
2
Select the correct gcloud CLI command group
Use the 'gcloud storage buckets update' command group.
Cloud Storage bucket modifications are executed under the 'gcloud storage buckets' sub-command space.
3
Specify the lifecycle configuration parameter
Pass '--lifecycle-file=lifecycle.json' along with the target bucket URI 'gs://analytics-raw-data-prod'.
The '--lifecycle-file' flag is the standard gcloud CLI flag for loading bucket lifecycle rules from a JSON or YAML file.

Key Concept

Configuring Cloud Storage Bucket Lifecycle Rules via gcloud CLI
Question 429Question

An online gaming company is planning a Google Kubernetes Engine (GKE) cluster architecture to host two distinct workloads:

1. A stateless, fault-tolerant match history analytics engine that processes asynchronous batch jobs with high sensitivity to compute costs.
2. A specialized security monitoring agent deployed as a DaemonSet that requires low-level custom Linux kernel sysctl parameter modifications on host nodes.

The cloud team wants to minimize cluster management overhead as much as possible while satisfying all technical requirements. Which TWO architectural decisions should the team implement? (Select 2 choices.)

Select all that apply

Show answer & explanation

Answer: Deploy a GKE Standard cluster to accommodate the host node operating system kernel modification requirements.; Create a dedicated GKE Standard node pool utilizing Spot VMs for the stateless match history analytics workload.

Answer

The team should deploy a GKE Standard cluster to allow host kernel sysctl tuning and configure a GKE Standard node pool using Spot VMs for the stateless batch analytics workload.
Choosing a GKE Standard cluster fulfills the requirement for custom sysctl kernel parameter tuning on host nodes, as GKE Autopilot restricts host-level OS changes. Additionally, creating a GKE Standard node pool with Spot VMs delivers maximum cost efficiency for the stateless, fault-tolerant match history analytics batch jobs.

Step-by-Step Solution

1
Evaluate the operational boundary between GKE Autopilot and GKE Standard.
GKE Autopilot locks down the underlying node operating system to guarantee managed security, preventing custom sysctl Linux kernel modifications. GKE Standard is mandatory when node-level kernel tuning is required.
Choosing Autopilot would violate the technical prerequisite of custom sysctl configuration.
2
Evaluate compute types for the stateless batch analytics engine.
The analytics engine is stateless, fault-tolerant, and cost-sensitive. Provisioning a dedicated node pool with Spot VMs significantly reduces compute expenses while allowing batch jobs to resume upon preemption.
Spot VMs are optimized for fault-tolerant workloads needing steep cost optimization.
3
Evaluate compute types for core infrastructure and security agents.
Critical system agents requiring reliable node coverage should run on standard compute instances rather than Spot VMs to prevent widespread daemon downtime during node reclamations.
Spot VMs are volatile and unsuitable for baseline security monitoring daemons.

Key Concept

GKE Cluster Mode Selection (Autopilot vs. Standard) and Spot VM Suitability
Question 430Question

A security auditing team requires access to run SQL queries and analyze table data within a specific BigQuery dataset in the project `finance-analytics-prod`. The team must be able to execute jobs in the project, but company security policy mandates strict adherence to the principle of least privilege, prohibiting the use of primitive roles or broad administrative privileges. Which TWO actions should you perform to grant the minimum required access? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Grant the BigQuery Job User (roles/bigquery.jobUser) role to the auditing team at the project level.; Grant the BigQuery Data Viewer (roles/bigquery.dataViewer) role to the auditing team at the dataset level.

Answer

Grant the BigQuery Job User role to the team at the project level, and grant the BigQuery Data Viewer role to the team at the specific dataset level.
To execute BigQuery queries and read table data securely under the principle of least privilege, two separate predefined roles are required: the BigQuery Job User role assigned at the project level to allow job running, and the BigQuery Data Viewer role assigned specifically on the target dataset to permit data reading.

Step-by-Step Solution

1
Identify the minimum permission required to create and execute BigQuery query jobs in the project.
Determine that `roles/bigquery.jobUser` assigned at the project level enables job execution without granting data access.
Running a query in BigQuery requires project-level compute job creation privileges.
2
Identify the minimum permission required to read table data within the target dataset.
Determine that `roles/bigquery.dataViewer` assigned at the dataset level grants data access scoped strictly to that dataset.
Scoping data access roles to specific datasets prevents unauthorized read access across other datasets in the project.

Key Concept

Combining resource-level and project-level predefined IAM roles to enforce the principle of least privilege in Google Cloud.
Estimated Time:2m 0s
Question 431Question

A lead cloud engineer at a renewable energy analytics firm needs to authorize a junior site reliability engineer (SRE) to link a newly created project, grid-telemetry-prod, to the company's central Cloud Billing account. Following the Google Cloud principle of least privilege, which combination of IAM roles must be granted to the SRE?

Show answer & explanation

Answer: Billing Account User (roles/billing.user) on the Cloud Billing account and Project Billing Manager (roles/resourcemanager.projectBillingManager) on the grid-telemetry-prod project

Answer

The correct answer specifies granting Billing Account User (roles/billing.user) on the Cloud Billing account and Project Billing Manager (roles/resourcemanager.projectBillingManager) on the target project.
Linking a Google Cloud project to a Cloud Billing account requires permissions on both resource levels: billing.resourceAssociations.create on the billing account (granted by roles/billing.user) and resourcemanager.projects.createBillingAssignment on the target project (granted by roles/resourcemanager.projectBillingManager). Using these two specific predefined roles strictly satisfies least privilege.

Step-by-Step Solution

1
Identify the required billing account permission
The identity needs billing.resourceAssociations.create on the billing account, provided by the predefined role Billing Account User (roles/billing.user).
Linking requires authorization to attach projects to the specified billing account.
2
Identify the required project permission
The identity needs resourcemanager.projects.createBillingAssignment on the project, provided by the predefined role Project Billing Manager (roles/resourcemanager.projectBillingManager).
Linking requires authorization to modify the billing configuration of the target project.
3
Apply the principle of least privilege
Combine roles/billing.user on the billing account and roles/resourcemanager.projectBillingManager on the project.
This grants exact necessary rights without using overly broad primitive roles like Owner or Editor.

Key Concept

Two-sided IAM permission requirement for linking GCP projects to Cloud Billing accounts under least privilege
Question 432Question

A satellite remote-sensing analytics organization ingests radar dataset files into a Google Cloud Storage bucket. The operations team outlines the following access pattern and compliance lifecycle for the data:

• For the first 1414 days after ingestion, dataset files undergo intense processing and are accessed multiple times per day by automated analytical workloads.
• Between day 1515 and day 9090, dataset files are queried sporadically (approximately once every 3030 days) for custom customer reporting.
• After 9090 days, the datasets are accessed less than once per year but must be retained for 77 years to meet regulatory compliance requirements.

Which Cloud Storage bucket lifecycle strategy minimizes the total cost of ownership (TCO) while adhering to storage class minimum duration rules and retrieval cost considerations?

Show answer & explanation

Answer: Set the default bucket class to Standard. Add Object Lifecycle Management rules to transition objects to Nearline storage after 1414 days, and transition objects to Archive storage after 9090 days.

Answer

Configure a bucket with the Standard storage class, transitioning objects to Nearline storage after 14 days and to Archive storage after 90 days using Object Lifecycle Management.
The correct strategy starts with the Standard storage class for active processing during the first 14 days to prevent retrieval charges. Moving data to Nearline after 14 days aligns with the monthly access pattern and respects Nearline's 30-day minimum storage requirement. Finally, transitioning data to Archive after 90 days minimizes long-term retention cost for 7 years while satisfying Archive's 365-day minimum storage commitment.

Step-by-Step Solution

1
Analyze initial ingestion access requirements (Days 0-14).
Identified high-frequency daily read access pattern.
Standard storage class has no retrieval fees per GB or retrieval operation charges, making it optimal for active processing.
2
Evaluate intermediate storage requirements (Days 15-90).
Selected Nearline storage class at Day 14 transition.
Nearline is intended for data accessed less than once a month with a 30-day minimum storage duration requirement. Staying in Nearline from day 14 to day 90 (76 days) satisfies the 30-day minimum duration requirement without incurring early deletion penalties.
3
Evaluate long-term compliance archiving requirements (Day 91+ to 7 years).
Selected Archive storage class at Day 90 transition.
Archive storage class offers the lowest per-gigabyte storage pricing for data accessed less than once per year, and retaining objects for 7 years easily fulfills Archive's 365-day minimum storage duration threshold.

Key Concept

Cloud Storage Class Selection & Lifecycle Transition Rules
Question 433Question

An enterprise application team is preparing to deploy a fault-tolerant, stateless data processing microservice to an existing Google Kubernetes Engine (GKE) Standard cluster. To optimize compute expenses, the cluster administrator has provisioned a secondary node pool using Spot VMs. Which configuration must be included in the application's Deployment manifest to ensure its pods are scheduled only on the Spot VM node pool?

Show answer & explanation

Answer: Specify a nodeSelector matching the cloud.google.com/gke-spot: "true" label within the Pod template specification.

Answer

Specify a nodeSelector matching the cloud.google.com/gke-spot: "true" label within the Pod template specification.
GKE automatically attaches the label cloud.google.com/gke-spot: "true" to nodes provisioned within a Spot node pool. Including a matching nodeSelector in the deployment template ensures the Kubernetes scheduler assigns pods only to nodes possessing that label.

Step-by-Step Solution

1
Identify the node labeling mechanism used by GKE for Spot VM node pools.
GKE automatically assigns the node label cloud.google.com/gke-spot="true" to nodes provisioned in Spot node pools.
Kubernetes uses labels on nodes to allow workloads to target specific hardware or pricing configurations.
2
Configure the Kubernetes Deployment spec to target this node label.
Adding nodeSelector: cloud.google.com/gke-spot: "true" inside the template spec directs the Kubernetes scheduler to place pods only on matching Spot nodes.
nodeSelector is the standard way to constrain pod scheduling to nodes with specific key-value labels.

Key Concept

Scheduling workloads on GKE Spot VM node pools using nodeSelector labels
Estimated Time:1m 30s
Question 434Question

A cloud network architect is planning a Virtual Private Cloud (VPC) network in Google Cloud to support a hybrid enterprise environment connected to an on-premises data center via Cloud VPN. The on-premises network uses the 10.128.0.0/910.128.0.0/9 CIDR range for internal services. The planned GCP footprint requires a primary subnet in region `us-central1` starting at 10.200.8.0/2410.200.8.0/24 and another primary subnet in region `us-east1` allocated at 10.200.16.0/2410.200.16.0/24.

Which TWO subnet planning and design requirements must be applied to ensure seamless hybrid connectivity and prevent IP address collisions? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Provision the VPC network in custom mode because auto-mode VPC networks automatically allocate subnets within the 10.128.0.0/910.128.0.0/9 range, which creates an IP address space collision with the on-premises network.; Ensure that any future expansion of the 10.200.8.0/2410.200.8.0/24 primary subnet CIDR block retains the same start IP address or aligns with contiguous CIDR boundaries while avoiding overlap with 10.200.16.0/2410.200.16.0/24 or on-premises networks.

Answer

The network architect must provision the VPC network in custom mode to prevent auto-mode's default 10.128.0.0/910.128.0.0/9 subnets from colliding with the on-premises range, and ensure any future subnet expansions follow contiguous CIDR boundary rules without overlapping existing regional subnets or hybrid network ranges.
Provisioning the VPC in custom mode is essential because auto-mode automatically creates subnets in the 10.128.0.0/910.128.0.0/9 range, which directly collides with the on-premises network range over Cloud VPN. Additionally, expanding a primary subnet's IP range requires adhering to contiguous CIDR boundary rules while ensuring the expanded block does not overlap with existing subnets such as the one in 10.200.16.0/2410.200.16.0/24 or on-premises spaces.

Step-by-Step Solution

1
Analyze the on-premises IP allocation versus GCP VPC creation modes.
Auto-mode VPCs create subnets in 10.128.0.0/910.128.0.0/9 in every GCP region by default. Since on-premises uses 10.128.0.0/910.128.0.0/9, auto-mode causes immediate CIDR overlap. Custom-mode VPC is mandatory.
Custom-mode VPC networks give architects complete control over subnet IP range selection, avoiding collisions across hybrid VPN tunnels.
2
Evaluate subnet expansion constraints in Google Cloud VPCs.
Subnet primary CIDRs can only be expanded (netmask length decreased), never shrunk. The new expanded block must be contiguous and must not overlap with any other subnet in the VPC or connected routes.
Expanding 10.200.8.0/2410.200.8.0/24 to a contiguous boundary like 10.200.8.0/2310.200.8.0/23 (10.200.8.010.200.8.0 - 10.200.9.25510.200.9.255) is valid and avoids 10.200.16.0/2410.200.16.0/24.
3
Verify distractor invalidity.
Auto-mode cannot be reconfigured to solve overlapping default IP spaces cleanly, and GCP VPCs do not support automatic merging of overlapping subnets.
Any CIDR overlap proposal triggers an API failure during subnet modification.

Key Concept

VPC Network Modes and Subnet Expansion Rules in GCP
Question 435Question

A cloud engineering team is expanding a compute-intensive microservices application in project `ecommerce-inventory-prod`. During rollout, the team discovers that deploying additional virtual machine instances in the `us-central1` region will exceed the project's regional Compute Engine `CPUS` resource quota. Which TWO valid strategies can the team use to resolve this regional quota constraint? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Submit a formal quota increase request for regional Compute Engine CPUS in us-central1 via the Google Cloud Console Quotas page.; Deploy the additional microservice virtual machine instances into an alternate region such as us-east1 where regional quota is available.

Answer

The correct strategies are submitting a quota increase request for regional Compute Engine CPUs in us-central1 via the Cloud Console, and deploying additional virtual machine instances into an alternate region with available quota.
The correct choices recognize that Compute Engine CPU limits are enforced per project per region. Submitting a quota request via the Cloud Console Quotas interface is the standard procedure to officially raise a regional CPU limit. Alternatively, distributing workloads across another region utilizes that region's separate quota pool.

Step-by-Step Solution

1
Identify the boundary and scope of the quota restriction.
Recognize that Compute Engine CPU quota is enforced per project per region.
Understanding quota scope determines whether regional reallocation or administrative request is appropriate.
2
Evaluate administrative quota adjustment options.
Submitting a quota increase request via the Cloud Console Quotas interface requests an increase to the project's regional CPU ceiling.
Quota increases must follow official GCP request workflows.
3
Evaluate architectural workload redistribution options.
Provisioning instances in a secondary region (such as us-east1) leverages unused quota specific to that region.
Regional quotas operate independently across different GCP regions.

Key Concept

GCP Resource Quotas are project- and region-specific boundaries that prevent resource exhaustion. They must be managed via formal quota requests or multi-region resource distribution.
Question 436Question

A solutions architect is planning a multi-region network layout for an enterprise application across two custom-mode Virtual Private Cloud (VPC) networks named `vpc-analytics` and `vpc-services`. The organization plans to establish VPC Network Peering between `vpc-analytics` and `vpc-services` so instances in both networks can communicate using internal IP addresses. Which network planning requirement must be met before creating the VPC Network Peering connection?

Show answer & explanation

Answer: The primary and secondary IP ranges of subnets in both VPC networks must not overlap.

Answer

The primary and secondary IP ranges of subnets in both VPC networks must not overlap.
VPC Network Peering enables private RFC 1918 connectivity between two VPC networks. A fundamental constraint of GCP VPC Network Peering is that no subnets (including primary and secondary IP ranges) can overlap between the peered networks.

Step-by-Step Solution

1
Analyze VPC Network Peering requirements
Identify that VPC Peering connects two VPC networks using internal IP routing.
Internal IP routing between peered networks requires unique IP ranges so packets can be routed unambiguously without IP conflicts.
2
Evaluate subnet range constraints for peered VPCs
Confirm that neither primary CIDR blocks nor secondary CIDR blocks (used for GKE or alias IPs) can overlap across the peered networks.
If any primary or secondary IP ranges overlap between the two VPCs, GCP prevents the creation or establishment of the peering connection.

Key Concept

VPC Network Peering IP Non-Overlap Requirement
Estimated Time:1m 30s
Question 437Question

A Lead Systems Engineer is configuring a new administrative workstation to manage deployments on an existing Google Kubernetes Engine (GKE) Standard cluster named `analytics-prod-cluster` in region `us-central1`. The engineer has completed authentication via `gcloud auth login` and installed `kubectl`. However, executing `kubectl get pods` results in an error indicating connection attempts to `localhost:8080`. Simultaneously, the team needs to create a new node pool dedicated to processing fault-tolerant, asynchronous batch calculations while keeping compute costs to a minimum. Which pair of actions correctly resolves the command-line authentication issue and fulfills the workload requirement?

Show answer & explanation

Answer: Execute `gcloud container clusters get-credentials analytics-prod-cluster --region us-central1` to populate the local kubeconfig, and provision a node pool configured with `--spot` instances.

Answer

Execute `gcloud container clusters get-credentials analytics-prod-cluster --region us-central1` to populate the local kubeconfig, and provision a node pool configured with `--spot` instances.
The correct response addresses both operational requirements: running `gcloud container clusters get-credentials` updates the local kubeconfig file with API server access credentials, resolving the `localhost:8080` connection error. Additionally, configuring a GKE node pool using `--spot` instances delivers significant cost reduction for stateless, fault-tolerant batch processing workloads.

Step-by-Step Solution

1
Diagnose the local `kubectl` error.
The connection error to `localhost:8080` indicates that `kubectl` lacks valid cluster endpoint credentials in the local `~/.kube/config` file.
When `kubectl` is invoked without a configured context, it defaults to attempting a local server connection at `localhost:8080`.
2
Update kubeconfig credentials using the gcloud CLI.
Running `gcloud container clusters get-credentials analytics-prod-cluster --region us-central1` fetches cluster metadata and endpoint information, writing valid credentials to kubeconfig.
This command generates the necessary authentication token and context for `kubectl` to communicate with the GKE control plane.
3
Select the appropriate GKE compute configuration for fault-tolerant batch processing.
Provisioning a dedicated GKE node pool with Spot VMs (`--spot`) provides discounted compute capacity suitable for batch workloads that tolerate preemption.
Spot VMs offer substantial cost savings compared to standard compute instances for workloads that are stateless and fault-tolerant.

Key Concept

GKE Cluster Credential Fetching & Spot Node Pool Provisioning
Estimated Time:2m 0s
Question 438Question

A cloud administrator needs to establish command-line management from a local workstation to a newly created Google Kubernetes Engine (GKE) cluster and deploy an application. Which two actions must the administrator perform to authenticate kubectl and deploy the Kubernetes workload? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Run `gcloud container clusters get-credentials` specifying the cluster name and location to update the local kubeconfig context.; Execute `kubectl apply -f` referencing the application deployment manifest files.

Answer

The administrator must update local kubeconfig credentials using `gcloud container clusters get-credentials` and deploy the application resources using `kubectl apply -f`.
To administer a GKE cluster via `kubectl`, an administrator must first fetch the cluster credentials using `gcloud container clusters get-credentials`, which updates the local `kubeconfig` context. Once authentication is established, executing `kubectl apply -f` deploys the defined Kubernetes manifests to the cluster.

Step-by-Step Solution

1
Authenticate kubectl to the GKE cluster
Local kubeconfig file is updated with cluster API server endpoints and access credentials.
kubectl requires context information from kubeconfig to communicate with the GKE control plane.
2
Apply the workload configuration manifests
Kubernetes Deployment and related resources are created in the cluster.
kubectl apply reads the declarative YAML manifests and submits them to the GKE API server for deployment.

Key Concept

Authenticating to GKE clusters with gcloud get-credentials and managing workloads with kubectl
Question 439Question

A cloud engineer needs to set up a new Google Cloud Storage bucket for an analytics project, grant read permissions to a designated service account, and upload an initial data file. In what sequence should the engineer execute these operational steps?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence is: first create the Cloud Storage bucket, next grant the IAM role to the service account, and finally upload the dataset file to the bucket.
Infrastructure provisioning follows a strict order of dependencies: create the bucket container first, configure access governance by applying IAM policy bindings second, and copy objects into the secured bucket last.

Step-by-Step Solution

1
Provision the destination bucket resource.
The Cloud Storage bucket gs://analytics-data-2026 is created in region us-central1.
A storage bucket must exist before any IAM policies can be attached to it or objects stored within it.
2
Attach the IAM policy binding to the bucket.
The service account is assigned the roles/storage.objectViewer role on the bucket.
Configuring access controls prior to populating objects ensures that authorized applications can read data immediately upon upload.
3
Copy the data file to the bucket.
The object sales_report.csv is uploaded into gs://analytics-data-2026/.
Object ingestion is executed once the destination container and permissions are fully established.

Key Concept

Deployment lifecycle sequence for provisioning Cloud Storage buckets, securing them with IAM roles, and uploading objects.
Estimated Time:1m 0s
Question 440Question

An enterprise cloud engineer is tasked with configuring financial management controls for a Google Cloud organization. The requirements specify that historical cost metrics must be saved daily to BigQuery for SQL-based cost analysis, and an event-driven mechanism must be established to broadcast real-time messages when monthly project expenditure hits 80% of a defined financial limit. Which TWO configuration steps are required to fulfill these requirements?

Select all that apply

Show answer & explanation

Answer: Create a target dataset within BigQuery and enable Cloud Billing export to BigQuery from the Cloud Billing console.; Configure a Cloud Billing budget with threshold rules set at 80% and attach a designated Cloud Pub/Sub topic under programmatic notifications.

Answer

The correct steps are creating a BigQuery dataset and enabling billing export in the Cloud Billing console, alongside configuring a Cloud Billing budget threshold linked to a Cloud Pub/Sub topic for programmatic notification.
Exporting daily Cloud Billing data requires creating a BigQuery dataset in a destination project and configuring standard/detailed export in the Cloud Billing console. For event-driven programmatic alerts, Cloud Billing budgets must be connected to a Cloud Pub/Sub topic under programmatic notification settings.

Step-by-Step Solution

1
Identify BigQuery export requirements
Creating a BigQuery dataset in the management project and linking it via Cloud Billing export enables automatic daily transfer of raw billing logs.
Cloud Billing export relies on standard BigQuery dataset destinations for raw and detailed usage data streaming.
2
Identify event-driven budget notification requirements
Setting an 80% threshold budget linked to a Cloud Pub/Sub topic publishes JSON alert payloads whenever the threshold is breached.
Native GCP billing budget alerts are passive notifications unless integrated with Cloud Pub/Sub for automated programmatic processing.
3
Evaluate distractor misconceptions
Eliminate choices suggesting native budget resource capping or organization-level API enablement.
GCP budgets never stop resources automatically, and APIs cannot be enabled directly on organization nodes.

Key Concept

Configuring Cloud Billing BigQuery export and programmatic Pub/Sub budget notifications
Estimated Time:2m 30s
PreviousPage 22 / 80Next
All practice questions — Google Cloud Associate Cloud Engineer | Examkin