Google Associate Cloud Engineer Practice Test 34

Question 330

Two application subnets are being planned in the same VPC and their primary CIDRs overlap. Which solution should be used?

  1. Use a subnet located in the VM's region
  2. Create separate custom VPC networks for the teams
  3. Use separate VPC networks and add peering only if later explicitly needed
  4. Choose an eligible regional load balancer and verify backend-region requirements
  5. Choose distinct nonoverlapping subnet address ranges

Explanation

Correct Answer

E:

Conflicting primary ranges cannot coexist in one VPC. Planning ranges early avoids disruptive later renumbering.

Incorrect Answers

A:

This mechanism is intended to match VM placement to subnet region. It does not implement the required action to create valid private subnet plans, even though both are relevant to the same general service.

B:

The result of this choice would be to isolate team networking into separate VPCs. The requested outcome, to create valid private subnet plans, is handled at a different layer or through another operation.

C:

While this can keep networks isolated until connectivity is approved, the present task requires an action to create valid private subnet plans. This operation does not supply the behavior described in the requirements.

D:

Administrators use it to align frontend and backend regional scope, rather than to create valid private subnet plans. Applying it would change the wrong component of this deployment.

Question 331

An operator wants two isolated application networks without automatically granting them private connectivity. How should the team proceed?

  1. Use a subnet located in the VM's region
  2. Configure a load balancer backend service with the appropriate health check
  3. Use separate VPC networks and add peering only if later explicitly needed
  4. Choose an eligible regional load balancer and verify backend-region requirements
  5. Choose distinct nonoverlapping subnet address ranges

Explanation

Correct Answer

C:

VPC isolation is a separate control from connecting VPCs. Resources in different networks do not receive automatic direct VPC routing just because projects share a billing account.

Incorrect Answers

A:

Select this when the goal is to match VM placement to subnet region. Here the decisive requirement is to avoid implicit cross-VPC access, and that outcome is not achieved by this action.

B:

The technical effect is to health-check load balancing backends, not to avoid implicit cross-VPC access; That distinction matters here because the first operation serves stop sending traffic to unhealthy VMs, rather than the scenario's required result.

D:

It can align frontend and backend regional scope; however, it does not provide the specific operation to avoid implicit cross-VPC access. The two controls serve different purposes.

E:

This choice is useful to avoid overlapping CIDR allocation. The stated task is to avoid implicit cross-VPC access, which requires a different mechanism or permission scope.

Question 332

A design depends on the load balancer's backend locations and expects a single regional frontend. What is the most direct solution?

  1. Configure VPC Network Peering where route exchange and limitations fit
  2. Choose distinct nonoverlapping subnet address ranges
  3. Choose an eligible regional load balancer and verify backend-region requirements
  4. Use separate VPC networks and add peering only if later explicitly needed
  5. Use a subnet located in the VM's region

Explanation

Correct Answer

C:

Regional load balancer types have region-specific backend and frontend constraints. A global design assumption could cause an invalid regional backend selection.

Incorrect Answers

A:

Choosing this would connect independent VPC networks privately, an appropriate action for vpc topology choices operations; It cannot take the place of the separate step needed to plan regional load balancing placement in this specific situation.

B:

Its purpose is to avoid overlapping CIDR allocation. That distinction matters: the scenario calls for an action to plan regional load balancing placement, not this separate configuration task.

D:

This setting would keep networks isolated until connectivity is approved. That behavior does not establish the requested ability to plan regional load balancing placement; it addresses an adjacent concern instead.

E:

This approach can match VM placement to subnet region. The requirement is to plan regional load balancing placement, so it controls a different part of the workflow and leaves that result unaddressed.

Question 333

An infrastructure team wants declarative cloud resources managed with a plan and state file. What should be configured?

  1. Use Terraform with an appropriate Google provider and remote state strategy
  2. Use an appropriate Fabric FAST or validated cloud foundation toolkit approach
  3. Use Helm charts and releases
  4. Use Config Connector where supported

Explanation

Correct Answer

A:

Terraform maintains desired infrastructure declarations and tracks resource state. Plans make proposed changes reviewable before apply.

Incorrect Answers

B:

This mechanism is intended to bootstrap standardized cloud foundations. It does not implement the required action to manage declarative infrastructure changes, even though both are relevant to the same general service.

C:

The tool can template and release Kubernetes applications, but it cannot be substituted for the capability needed to manage declarative infrastructure changes. Its operational effect is not equivalent.

D:

Select this when the goal is to manage Google Cloud resources through Kubernetes resources. Here the decisive requirement is to manage declarative infrastructure changes, and that outcome is not achieved by this action.

Question 334

A Kubernetes platform team wants Google Cloud resource definitions represented by Kubernetes custom resources. Which action is most appropriate?

  1. Use Terraform with an appropriate Google provider and remote state strategy
  2. Run terraform plan against the selected configuration and state
  3. Use an appropriate Fabric FAST or validated cloud foundation toolkit approach
  4. Use Config Connector where supported
  5. Use Helm charts and releases

Explanation

Correct Answer

D:

Config Connector exposes Google Cloud resources through Kubernetes-style declarative configurations. It requires appropriate cluster and controller setup.

Incorrect Answers

A:

This approach can provision Google Cloud resources through Terraform state. The requirement is to reconcile cloud infrastructure from KRM manifests, so it controls a different part of the workflow and leaves that result unaddressed.

B:

The technical effect is to preview declarative infrastructure changes, not to reconcile cloud infrastructure from KRM manifests; That distinction matters here because the first operation serves review an infrastructure change set, rather than the scenario's required result.

C:

This setting would bootstrap standardized cloud foundations. That behavior does not establish the requested ability to reconcile cloud infrastructure from KRM manifests; it addresses an adjacent concern instead.

E:

Using this action would template and release Kubernetes applications, not reconcile cloud infrastructure from KRM manifests. Its function is different from the specific change described in the scenario.

Question 335

A service deployment uses parameterized Kubernetes manifests and must be installed repeatedly into clusters. Which solution should be used?

  1. Use an appropriate Fabric FAST or validated cloud foundation toolkit approach
  2. Use Helm charts and releases
  3. Use Terraform with an appropriate Google provider and remote state strategy
  4. Configure a supported remote state backend such as a secured Cloud Storage bucket
  5. Use Config Connector where supported

Explanation

Correct Answer

B:

Helm packages Kubernetes resource manifests into configurable charts. It does not replace Terraform state for unrelated cloud infrastructure.

Incorrect Answers

A:

Administrators use it to bootstrap standardized cloud foundations, rather than to manage Kubernetes manifest packages. Applying it would change the wrong component of this deployment.

C:

This mechanism is intended to provision Google Cloud resources through Terraform state. It does not implement the required action to manage Kubernetes manifest packages, even though both are relevant to the same general service.

D:

Choosing this would share and protect Terraform state, an appropriate action for terraform workflow and state operations; It cannot take the place of the separate step needed to manage Kubernetes manifest packages in this specific situation.

E:

The result of this choice would be to manage Google Cloud resources through Kubernetes resources. The requested outcome, to manage Kubernetes manifest packages, is handled at a different layer or through another operation.

Question 336

A large organization needs a maintained foundation of Terraform components for core cloud architecture. How should the team proceed?

  1. Use Config Connector where supported
  2. Deploy a Helm release with reviewed values
  3. Use Helm charts and releases
  4. Use Terraform with an appropriate Google provider and remote state strategy
  5. Use an appropriate Fabric FAST or validated cloud foundation toolkit approach

Explanation

Correct Answer

E:

Fabric FAST and foundation approaches provide reusable infrastructure patterns. Teams still review permissions, state ownership, and organization-specific inputs.

Incorrect Answers

A:

The tool can manage Google Cloud resources through Kubernetes resources, but it cannot be substituted for the capability needed to reuse platform infrastructure building blocks. Its operational effect is not equivalent.

B:

This proposal can install repeatable chart releases, but the failure or goal described here calls for a way to reuse platform infrastructure building blocks; It changes the wrong control or scope for the requested outcome.

C:

Using this action would template and release Kubernetes applications, not reuse platform infrastructure building blocks. Its function is different from the specific change described in the scenario.

D:

This choice is useful to provision Google Cloud resources through Terraform state. The stated task is to reuse platform infrastructure building blocks, which requires a different mechanism or permission scope.

Question 337

Two engineers maintain a Terraform-managed Google Cloud environment and want repeatable, reviewable changes without overwriting each other's state. Which TWO practices should be adopted? (Choose TWO.)

  1. Delete the shared state after each apply so each developer independently guesses the infrastructure inventory
  2. Use a secured, shared Terraform backend with appropriate state protection and concurrency controls
  3. Require review of a Terraform execution plan before applying proposed infrastructure changes
  4. Commit decrypted provider credentials and service-account private keys next to Terraform files

Explanation

Correct Answers

B:

Remote state centralizes the tracked infrastructure state for collaboration. Backend permissions and locking or conflict protections help avoid parallel changes overwriting one another.

C:

A reviewed plan shows the intended resource changes based on configuration and current state. This reduces surprise modifications before committing them to Google Cloud.

Incorrect Answers

A:

Terraform state records resource associations needed for reliable updates. Discarding it on every run makes reconciliation and team operation error-prone rather than safe.

D:

Putting long-lived private credentials in source control exposes sensitive access. Prefer short-lived or federated authentication and secure secret handling.

Question 338

A deployment must persist Terraform state for collaborative team access with access control. What should be configured?

  1. Refresh and review Terraform plan results before reconciling
  2. Run terraform plan against the selected configuration and state
  3. Configure a supported remote state backend such as a secured Cloud Storage bucket
  4. Run terraform apply with the reviewed configuration or plan

Explanation

Correct Answer

C:

Remote state allows controlled shared access to Terraform's resource mapping. State can contain sensitive material and needs restricted access and appropriate concurrency handling.

Incorrect Answers

A:

This mechanism is intended to detect declarative resource drift. It does not implement the required action to enable collaborative IaC resource tracking, even though both are relevant to the same general service.

B:

It can preview declarative infrastructure changes; however, it does not provide the specific operation to enable collaborative IaC resource tracking. The two controls serve different purposes.

D:

Select this when the goal is to enact Terraform configuration changes. Here the decisive requirement is to enable collaborative IaC resource tracking, and that outcome is not achieved by this action.

Question 339

A platform engineer has approved a plan and needs Terraform to enact it. Which action is most appropriate?

  1. Use Terraform with an appropriate Google provider and remote state strategy
  2. Run terraform apply with the reviewed configuration or plan
  3. Run terraform plan against the selected configuration and state
  4. Configure a supported remote state backend such as a secured Cloud Storage bucket
  5. Refresh and review Terraform plan results before reconciling

Explanation

Correct Answer

B:

Terraform apply performs the requested resource creates, updates, or destroys. Its effects depend on provider permissions and current state.

Incorrect Answers

A:

While this can provision Google Cloud resources through Terraform state, the present task requires an action to apply a reviewed infrastructure deployment. This operation does not supply the behavior described in the requirements.

C:

Its purpose is to preview declarative infrastructure changes. That distinction matters: the scenario calls for an action to apply a reviewed infrastructure deployment, not this separate configuration task.

D:

This setting would share and protect Terraform state. That behavior does not establish the requested ability to apply a reviewed infrastructure deployment; it addresses an adjacent concern instead.

E:

Using this action would detect declarative resource drift, not apply a reviewed infrastructure deployment. Its function is different from the specific change described in the scenario.

Question 340

A resource was changed manually and the team wants to compare reality to its declarative configuration. Which solution should be used?

  1. Use Gemini Cloud Assist and verify the generated guidance
  2. Run terraform plan against the selected configuration and state
  3. Run terraform apply with the reviewed configuration or plan
  4. Configure a supported remote state backend such as a secured Cloud Storage bucket
  5. Refresh and review Terraform plan results before reconciling

Explanation

Correct Answer

E:

Infrastructure drift appears when observed cloud resources differ from desired configuration or tracked state. Reconciliation should be reviewed rather than blindly overwriting the manual change.

Incorrect Answers

A:

An operator would use this action to generate contextual cloud configuration assistance, chiefly when trying to investigate a deployment configuration with AI help; The current requirement is to compare manual changes with IaC definitions, which remains unresolved by that operation.

B:

This mechanism is intended to preview declarative infrastructure changes. It does not implement the required action to compare manual changes with IaC definitions, even though both are relevant to the same general service.

C:

Select this when the goal is to enact Terraform configuration changes. Here the decisive requirement is to compare manual changes with IaC definitions, and that outcome is not achieved by this action.

D:

The result of this choice would be to share and protect Terraform state. The requested outcome, to compare manual changes with IaC definitions, is handled at a different layer or through another operation.

Associate Cloud Engineer Practice Tests