mcAfee Secure Website
23

Google Associate Cloud Engineer Bundle

Exam Code: Associate Cloud Engineer

Exam Name Associate Cloud Engineer

Certification Provider: Google

Corresponding Certification: Associate Cloud Engineer

Associate Cloud Engineer Training Materials $44.99

Reliable & Actual Study Materials for Associate Cloud Engineer Exam Success

The Latest Associate Cloud Engineer Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    Associate Cloud Engineer Questions & Answers

    391 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • 25
    Associate Cloud Engineer Video Course

    Associate Cloud Engineer Training Course

    234 Video Lectures

    Based on Real Life Scenarios which you will encounter in exam and learn by working with real equipment.

  • exam =30
    Study Guide

    Associate Cloud Engineer Study Guide

    849 PDF Pages

    Study Guide developed by industry experts who have written exams in the past. They are technology-specific IT certification researchers with at least a decade of experience at Fortune 500 companies.

exam =32

Associate Cloud Engineer Practice Tests

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Google Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    391 Questions

    $124.99
    exam =35
  • exam =37
    Associate Cloud Engineer Video Course

    Training Course

    234 Video Lectures

    $39.99
  • exam =36
    Study Guide

    Study Guide

    849 PDF Pages

    $29.99

Google Associate Cloud Engineer Practice Test 22

Question 210

A global HTTPS application faces abusive requests targeting specific paths and needs rate limiting and Layer 7 web-application protection at supported load-balancer edges. Which service should be attached to the eligible backend?

  1. VPC Network Peering to every client.
  2. Cloud Armor security policies with appropriate WAF or rate-limiting rules.
  3. Configure VPC firewall rules to match HTTP URL paths and request rate thresholds.
  4. Cloud DNS response policy only.

Explanation

Correct Answer

B:

Cloud Armor evaluates HTTP(S) traffic at supported load balancers, providing application-layer filtering beyond VPC packet firewall rules.

Incorrect Answers

A:

Peering is not an internet WAF and does not filter request paths.

C:

VPC firewall rules match network-level attributes, not application-layer HTTP path signatures and WAF/rate-limiting policies.

D:

DNS response controls do not inspect or rate-limit HTTPS requests at the load balancer.

Question 211

A VM sends an outbound HTTPS request through an allowed egress flow. No explicit ingress rule permits the response packet, but the established connection succeeds. Which VPC firewall characteristic explains the return traffic?

  1. Google Cloud VPC firewall evaluation is stateful for allowed connections, permitting corresponding response traffic.
  2. All Google Cloud VPCs implicitly allow arbitrary new inbound TCP connections.
  3. Cloud DNS automatically creates a temporary firewall rule for every hostname.
  4. Create explicit reverse-direction ingress allow rules for all ephemeral response ports.

Explanation

Correct Answer

A:

Stateful connection tracking allows reply packets associated with an established permitted flow without a separate ingress allow for each response.

Incorrect Answers

B:

Implied ingress deny still blocks unsolicited inbound flows; the observed return is part of an established outbound connection.

C:

DNS queries and caching are separate from connection tracking in the VPC firewall.

D:

Stateful firewall tracking permits related return traffic for an allowed connection; blanket port rules unnecessarily expand exposure.

Question 212

A team cloned a Terraform repository containing the Google Cloud provider configuration. Running terraform plan reports the working directory has not been initialized. What command prepares provider plugins and backend configuration?

  1. Run terraform destroy immediately.
  2. Change the Google Cloud project display name.
  3. Run kubectl logs against the repo.
  4. Run terraform init in the configuration directory.

Explanation

Correct Answer

D:

Initialization installs required provider dependencies and prepares the selected backend before later planning or applying resource changes.

Incorrect Answers

A:

Destroy attempts to remove managed resources and does not prepare the uninitialized workspace.

B:

Resource metadata has no effect on local Terraform provider installation.

C:

Kubernetes log retrieval cannot initialize Terraform modules or provider plugins.

Question 213

A change review approved an exact Terraform plan file after checking proposed infrastructure modifications. The deployment pipeline must execute that reviewed set rather than silently recompute a possibly different plan. Which operation meets the requirement?

  1. Run terraform plan again and automatically approve any new changes.
  2. Delete the remote state and start over.
  3. Apply the saved binary plan with terraform apply <planfile> after confirming the expected context.
  4. Run terraform plan again and assume the saved approved binary plan is automatically applied.

Explanation

Correct Answer

C:

Applying a saved plan uses the approved set of actions captured at plan time, subject to compatible state and environment.

Incorrect Answers

A:

Replanning can produce a different action set from the reviewed artifact.

B:

Removing state destroys authoritative tracking and invalidates the reviewed plan.

D:

Planning reports proposed changes but does not execute the reviewed saved plan file; `terraform apply <planfile>` makes the approved change.

Question 214

A production Cloud Storage bucket already exists, and engineers want Terraform to manage it without recreating or deleting its objects. What state-onboarding action should they use after defining appropriate configuration?

  1. Run terraform destroy on the whole project.
  2. Import the existing bucket into the matching Terraform resource address and reconcile its configuration.
  3. Change the bucket's DNS name only.
  4. Add the existing bucket's name to the Terraform state file by editing JSON manually.

Explanation

Correct Answer

B:

Terraform import associates a real existing resource with state so declarative management can continue without initial creation.

Incorrect Answers

A:

Destruction would remove managed resources and violates non-disruption requirements.

C:

Naming does not bind an existing resource to Terraform state.

D:

Direct manual state editing risks incorrect resource attributes and serial information; a managed import associates the real bucket with its resource address.

Question 215

A Terraform module refactor changes the address of a managed resource, but the remote Google Cloud object should remain untouched and retain its identity. Which state operation can update the tracked address?

  1. Use terraform state mv for the old and new resource addresses, with an appropriate reviewed configuration change.
  2. Delete the old resource before running plan.
  3. Rename the Google Cloud project ID to match the module.
  4. Delete the existing Terraform state and let a fresh apply reconstruct the renamed resource.

Explanation

Correct Answer

A:

Moving the state address preserves the underlying resource association while code is reorganized.

Incorrect Answers

B:

Deletion would destroy the real resource rather than simply changing its IaC address.

C:

Project IDs are immutable and irrelevant to the state address mapping.

D:

Removing state can make Terraform treat an existing resource as new and risks unintended replacement instead of a controlled address move.

Question 216

An operator suspects a console hotfix changed cloud resource attributes outside Terraform. Before deciding whether to overwrite or adopt the change, they want a state-only proposal based on current remote objects. Which Terraform mode should they inspect?

  1. Run terraform destroy to reset drift.
  2. Add more IAM project viewers.
  3. Create a Kubernetes Ingress resource.
  4. Use terraform plan -refresh-only to review changes needed in recorded state without proposing configuration-driven infrastructure updates.

Explanation

Correct Answer

D:

Refresh-only planning compares prior state with remote objects and proposes updating Terraform's state view rather than applying resource configuration changes.

Incorrect Answers

A:

Destroy is destructive and inappropriate for a non-mutating inspection.

B:

Viewer grants do not reconcile Terraform state drift.

C:

Ingress is an application routing object, not a state synchronization inspection.

Question 217

Several teams need a standardized VPC pattern with identical security controls but different IP ranges and project IDs. Which Terraform construct promotes maintained reuse without copying code into dozens of repositories?

  1. Put each team's CIDR in the same public DNS TXT record.
  2. Manually duplicate the root configuration into every repository and never version it.
  3. Package the VPC configuration as a versioned module with input variables and outputs.
  4. Grant every team Organization Administrator.

Explanation

Correct Answer

C:

Terraform modules encapsulate repeatable resource patterns while parameters allow project-specific values without duplicating implementation code.

Incorrect Answers

A:

DNS records do not instantiate or version IaC resource definitions.

B:

Code copying creates drift and weakens central maintenance.

D:

Broad IAM grants do not supply reusable infrastructure definitions.

Question 218

Two CI runners produce different Terraform plans because they independently resolve different provider versions. What repository artifact helps keep provider selections reproducible?

  1. Pin the provider version only in a developer's local Terraform CLI configuration.
  2. Commit and maintain the Terraform dependency lock file with the approved provider selections.
  3. Configure Cloud NAT for both runners only.
  4. Rename the production VPC network.

Explanation

Correct Answer

B:

The lock file records provider versions and checksums, helping compatible runs use consistent provider dependencies.

Incorrect Answers

A:

Local settings are not a shared dependency lock; CI runners need a committed lock file to select the same provider release.

C:

Network access may be necessary to download providers, but does not pin their versions.

D:

Resource names do not define provider dependency versions.

Question 219

Before connecting a Terraform PR to cloud credentials, a reviewer wants to check whether the configuration is internally valid without planning changes against current remote state. Which command is intended for this validation?

  1. Run terraform validate after initializing dependencies where needed.
  2. Run terraform apply -auto-approve in production.
  3. Run gcloud compute instances delete to test permissions.
  4. Create a Cloud DNS private zone for the module.

Explanation

Correct Answer

A:

Terraform validate checks configuration syntax and internal consistency without executing a state-based infrastructure change plan.

Incorrect Answers

B:

Auto-applying can mutate production and is not a static validation step.

C:

Deletion is destructive and does not validate Terraform HCL configuration.

D:

DNS records neither parse Terraform HCL nor run configuration syntax validation; use the Terraform CLI's validation command after initialization.

Question 220

A Terraform plan creates managed credentials. The team marks outputs sensitive and concludes its remote state may be made public because the CLI hides those output values. What security control is still required?

  1. Make the state object publicly readable to simplify debugging.
  2. Store the state in a public Cloud DNS record.
  3. Disable all CI audit logs so nobody can see state activity.
  4. Protect Terraform state storage and access because sensitive values can still appear in the state data.

Explanation

Correct Answer

D:

The sensitive output flag masks displays but does not universally remove secret values from persisted state; backend permissions remain essential.

Incorrect Answers

A:

Public state access can leak credentials or internal infrastructure details.

B:

DNS is neither confidential nor a suitable state backend.

C:

Removing logs does not protect stored state and reduces accountability.