Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. Google
  5. ASSOCIATE-CLOUD-ENGINEER

Google ASSOCIATE-CLOUD-ENGINEER Exam
Associate Cloud Engineer (Page 9 )

Updated On: 25-Jan-2026
Page 9 of 63
PDF with 343 Questions

You created a Kubernetes deployment by running kubectl run nginx image=nginx replicas=1. After a few days, you decided you no longer want this deployment. You identified the pod and deleted it by running kubectl delete pod. You noticed the pod got recreated.
$ kubectl get pods
NAME READY STATUS RESTARTS AGE
nginx-84748895c4-nqqmt 1/1 Running 0 9m41s
$ kubectl delete pod nginx-84748895c4-nqqmt pod nginx-84748895c4-nqqmt deleted
$ kubectl get pods

NAME READY STATUS RESTARTS AGE
nginx-84748895c4-k6bzl 1/1 Running 0 25s
What should you do to delete the deployment and avoid pod getting recreated?

  1. kubectl delete deployment nginx
  2. kubectl delete ­deployment=nginx
  3. kubectl delete pod nginx-84748895c4-k6bzl ­no-restart 2
  4. kubectl delete inginx

Answer(s): A

Explanation:

This command correctly deletes the deployment. Pods are managed by kubernetes workloads (deployments).
When a pod is deleted, the deployment detects the pod is unavailable and brings up another pod to maintain the replica count. The only way to delete the workload is by deleting the deployment itself using the kubectl delete deployment command.
$ kubectl delete deployment nginx deployment.apps nginx deleted
Ref: https://kubernetes.io/docs/reference/kubectl/cheatsheet/#deleting-resources



Your web application has been running successfully on Cloud Run for Anthos. You want to evaluate an updated version of the application with a specific percentage of your production users (canary deployment).
What should you do?

  1. Create a new service with the new version of the application. Split traffic between this version and the version that is currently running.
  2. Create a new revision with the new version of the application. Split traffic between this version and the version that is currently running.
  3. Create a new service with the new version of the application. Add an HTTP Load Balancer in front of both services.
  4. Create a new revision with the new version of the application. Add an HTTP Load Balancer in front of both revisions.

Answer(s): B

Explanation:

https://cloud.google.com/kuberun/docs/rollouts-rollbacks-traffic-migration



You have experimented with Google Cloud using your own credit card and expensed the costs to your company. Your company wants to streamline the billing process and charge the costs of your projects to their monthly invoice.
What should you do?

  1. Grant the financial team the IAM role of Billing Account User on the billing account linked to your credit card.
  2. Set up BigQuery billing export and grant your financial department IAM access to query the data.
  3. Create a ticket with Google Billing Support to ask them to send the invoice to your company.
  4. Change the billing account of your projects to the billing account of your company.

Answer(s): D



Your company has embraced a hybrid cloud strategy where some of the applications are deployed on Google Cloud. A Virtual Private Network (VPN) tunnel connects your Virtual Private Cloud (VPC) in Google Cloud with your company's on-premises network. Multiple applications in Google Cloud need to connect to an on-premises database server, and you want to avoid having to change the IP configuration in all of your applications when the IP of the database changes.
What should you do?

  1. Configure Cloud NAT for all subnets of your VPC to be used when egressing from the VM instances.
  2. Create a private zone on Cloud DNS, and configure the applications with the DNS name.
  3. Configure the IP of the database as custom metadata for each instance, and query the metadata server.
  4. Query the Compute Engine internal DNS from the applications to retrieve the IP of the database.

Answer(s): B

Explanation:

Forwarding zones Cloud DNS forwarding zones let you configure target name servers for specific private zones. Using a forwarding zone is one way to implement outbound DNS forwarding from your VPC network. A Cloud DNS forwarding zone is a special type of Cloud DNS private zone. Instead of creating records within the zone, you specify a set of forwarding targets. Each forwarding target is an IP address of a DNS server, located in your VPC network, or in an on-premises network connected to your VPC network by Cloud VPN or Cloud Interconnect.
https://cloud.google.com/nat/docs/overview

DNS configuration Your on-premises network must have DNS zones and records configured so that Google domain names resolve to the set of IP addresses for either private.googleapis.com or restricted.googleapis.com. You can create Cloud DNS managed private zones and use a Cloud DNS inbound server policy, or you can configure on-premises name servers. For example, you can use BIND or Microsoft Active Directory DNS. https://cloud.google.com/vpc/docs/configure-private- google-access-hybrid#config-domain



Your company has an internal application for managing transactional orders. The application is used exclusively by employees in a single physical location. The application requires strong consistency, fast queries, and ACID guarantees for multi-table transactional updates. The first version of the application is implemented inPostgreSQL, and you want to deploy it to the cloud with minimal code changes.
Which database is most appropriate for this application?

  1. BigQuery
  2. Cloud SQL
  3. Cloud Spanner
  4. Cloud Datastore

Answer(s): B

Explanation:

https://cloud.google.com/sql/docs/postgres



Viewing page 9 of 63
Viewing questions 41 - 45 out of 343 questions



Post your Comments and Discuss Google ASSOCIATE-CLOUD-ENGINEER exam prep with other Community members:

Join the ASSOCIATE-CLOUD-ENGINEER Discussion