Google Associate Cloud Engineer Google Associate Cloud Engineer Exam Questions in PDF

Free Google Google Associate Cloud Engineer Dumps Questions (page: 2)

Your company uses Cloud Storage to store application backup files for disaster recovery purposes. You want to follow Google's recommended practices.
Which storage option should you use?

  1. Multi-Regional Storage
  2. Regional Storage
  3. Nearline Storage
  4. Coldline Storage

Answer(s): D


Reference:

https://cloud.google.com/storage/docs/storage-classes#nearline https://cloud.google.com/blog/products/gcp/introducing-coldline-and-a-unified-platform-for-data- storage

Cloud Storage Coldline: a low-latency storage class for long-term archiving Coldline is a new Cloud Storage class designed for long-term archival and disaster recovery. Coldline is perfect for the archival needs of big data or multimedia content, allowing businesses to archive years of data. Coldline provides fast and instant (millisecond) access to data and changes the way that companies think about storing and accessing their cold data.



Several employees at your company have been creating projects with Cloud Platform and paying for it with their personal credit cards, which the company reimburses. The company wants to centralize all these projects under a single, new billing account.
What should you do?

  1. Contact cloud-billing@google.com with your bank account details and request a corporate billing account for your company.
  2. Create a ticket with Google Support and wait for their call to share your credit card details over the phone.
  3. In the Google Platform Console, go to the Resource Manage and move all projects to the root Organization.
  4. In the Google Cloud Platform Console, create a new billing account and set up a payment method.

Answer(s): D

Explanation:

(https://cloud.google.com/resource-manager/docs/project-migration#change_billing_account)

https://cloud.google.com/billing/docs/concepts https://cloud.google.com/resource-manager/docs/project-migration



You have an application that looks for its licensing server on the IP 10.0.3.21. You need to deploy the licensing server on Compute Engine. You do not want to change the configuration of the application and want the application to be able to reach the licensing server.
What should you do?

  1. Reserve the IP 10.0.3.21 as a static internal IP address using gcloud and assign it to the licensing server.
  2. Reserve the IP 10.0.3.21 as a static public IP address using gcloud and assign it to the licensing server.
  3. Use the IP 10.0.3.21 as a custom ephemeral IP address and assign it to the licensing server.
  4. Start the licensing server with an automatic ephemeral IP address, and then promote it to a static internal IP address.

Answer(s): A

Explanation:

IP 10.0.3.21 is internal by default, and to ensure that it will be static non-changing it should be selected as static internal ip address.



You are deploying an application to App Engine. You want the number of instances to scale based on request rate. You need at least 3 unoccupied instances at all times.
Which scaling type should you use?

  1. Manual Scaling with 3 instances.
  2. Basic Scaling with min_instances set to 3.
  3. Basic Scaling with max_instances set to 3.
  4. Automatic Scaling with min_idle_instances set to 3.

Answer(s): D


Reference:

https://cloud.google.com/appengine/docs/standard/python/how-instances-are-managed https://cloud.google.com/appengine/docs/standard/go/config/appref

"App Engine calculates the number of instances necessary to serve your current application traffic based on scaling settings such as target_cpu_utilization and target_throughput_utilization. Setting min_idle_instances specifies the number of instances to run in addition to this calculated number. For example, if App Engine calculates that 5 instances are necessary to serve traffic, and min_idle_instances is set to 2, App Engine will run 7 instances (5, calculated based on traffic, plus 2 additional per min_idle_instances)."

Automatic scaling creates dynamic instances based on request rate, response latencies, and other application metrics. However, if you specify the number of minimum idle instances, that specified number of instances run as resident instances while any additional instances are dynamic. Ref: https://cloud.google.com/appengine/docs/standard/python/how-instances-are-managed



You have a development project with appropriate IAM roles defined. You are creating a production project and want to have the same IAM roles on the new project, using the fewest possible steps.
What should you do?

  1. Use gcloud iam roles copy and specify the production project as the destination project.
  2. Use gcloud iam roles copy and specify your organization as the destination organization.
  3. In the Google Cloud Platform Console, use the `create role from role' functionality.
  4. In the Google Cloud Platform Console, use the `create role' functionality and select all applicable permissions.

Answer(s): A


Reference:

https://cloud.google.com/sdk/gcloud/reference/iam/roles/copy

To create a copy of an existing role spanner.databaseAdmin into a project with PROJECT_ID, run:
gcloud iam roles copy --source="roles/spanner.databaseAdmin" -- destination=CustomSpannerDbAdmin --dest-project=PROJECT_ID



Share your comments for Google Google Associate Cloud Engineer exam with other users:

A
Anonymous User
4/13/2026 6:29:58 PM

Question 1:

  • Correct answer: C

  • Why this is best:
- Uses OS Login with IAM, so SSH access is granted via Google accounts rather than distributing per-user SSH keys. - Granting the compute.osAdminLogin role to a Google group gives admin access to all team members in a centralized, auditable way. - Access is auditable: Cloud Audit Logs show who accessed which VM, satisfying the security requirement to determine who accessed a given instance.
  • How it works:
- Enable OS Login on the project/instances (enable-oslogin metadata). - Add the team’s

AI Tutor 👋 I’m here to help!