support@Free-Braindumps.com
Register Login
Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
CrowdStrike
Anthropic
All Vendors
  1. Home
  2. Exams
  3. Google
  4. Associate Cloud Engineer

Free Associate Cloud Engineer Exam Braindumps
Associate Cloud Engineer Questions 61–65 (page: 14)

Updated On: 10-Feb-2026
Page 14 of 69
PDF with 391 Questions

Your organization is a financial company that needs to store audit log files for 3 years. Your organization has hundreds of Google Cloud projects. You need to implement a cost-effective approach for log file retention.
What should you do?

  1. Create an export to the sink that saves logs from Cloud Audit to BigQuery.
  2. Create an export to the sink that saves logs from Cloud Audit to a Coldline Storage bucket.
  3. Write a custom script that uses logging API to copy the logs from Stackdriver logs to BigQuery.
  4. Export these logs to Cloud Pub/Sub and write a Cloud Dataflow pipeline to store logs to Cloud SQL.

Answer(s): B


Reference:

https://cloud.google.com/blog/products/devops-sre/cloud-logging-cost-management-best-practices



You want to run a single caching HTTP reverse proxy on GCP for a latency-sensitive website. This specific reverse proxy consumes almost no CPU. You want to have a 30-GB in-memory cache, and need an additional 2 GB of memory for the rest of the processes. You want to minimize cost. How should you run this reverse proxy?

  1. Create a Cloud Memorystore for Redis instance with 32-GB capacity.
  2. Run it on Compute Engine, and choose a custom instance type with 6 vCPUs and 32 GB of memory.
  3. Package it in a container image, and run it on Kubernetes Engine, using n1-standard-32 instances as nodes.
  4. Run it on Compute Engine, choose the instance type n1-standard-1, and add an SSD persistent disk of 32 GB.

Answer(s): A


Reference:

https://cloud.google.com/memorystore/docs/redis/redis-overview#what_its_good_for



You are hosting an application on bare-metal servers in your own data center. The application needs access to Cloud Storage. However, security policies prevent the servers hosting the application from having public IP addresses or access to the internet. You want to follow Google-recommended practices to provide the application with access to Cloud Storage.
What should you do?

  1. 1. Use nslookup to get the IP address for storage.googleapis.com.
    2. Negotiate with the security team to be able to give a public IP address to the servers.
    3. Only allow egress traffic from those servers to the IP addresses for storage.googleapis.com.
  2. 1. Using Cloud VPN, create a VPN tunnel to a Virtual Private Cloud (VPC) in Google Cloud.
    2. In this VPC, create a Compute Engine instance and install the Squid proxy server on this instance.
    3. Configure your servers to use that instance as a proxy to access Cloud Storage.
  3. 1. Use Migrate for Compute Engine (formerly known as Velostrata) to migrate those servers to Compute Engine.
    2. Create an internal load balancer (ILB) that uses storage.googleapis.com as backend.
    3. Configure your new instances to use this ILB as proxy.
  4. 1. Using Cloud VPN or Interconnect, create a tunnel to a VPC in Google Cloud.
    2. Use Cloud Router to create a custom route advertisement for 199.36.153.4/30. Announce that network to your on-premises network through the VPN tunnel.
    3. In your on-premises network, configure your DNS server to resolve *.googleapis.com as a CNAME to restricted.googleapis.com.

Answer(s): D


Reference:

https://cloud.google.com/vpc/docs/configure-private-google-access-hybrid



You want to deploy an application on Cloud Run that processes messages from a Cloud Pub/Sub topic. You want to follow Google-recommended practices.
What should you do?

  1. 1. Create a Cloud Function that uses a Cloud Pub/Sub trigger on that topic.
    2. Call your application on Cloud Run from the Cloud Function for every message.
  2. 1. Grant the Pub/Sub Subscriber role to the service account used by Cloud Run.
    2. Create a Cloud Pub/Sub subscription for that topic.
    3. Make your application pull messages from that subscription.
  3. 1. Create a service account.
    2. Give the Cloud Run Invoker role to that service account for your Cloud Run application.
    3. Create a Cloud Pub/Sub subscription that uses that service account and uses your Cloud Run application as the push endpoint.
  4. 1. Deploy your application on Cloud Run on GKE with the connectivity set to Internal.
    2. Create a Cloud Pub/Sub subscription for that topic.
    3. In the same Google Kubernetes Engine cluster as your application, deploy a container that takes the messages and sends them to your application.

Answer(s): C


Reference:

https://cloud.google.com/run/docs/tutorials/pubsub#integrating-pubsub



You need to deploy an application, which is packaged in a container image, in a new project. The application exposes an HTTP endpoint and receives very few requests per day. You want to minimize costs.
What should you do?

  1. Deploy the container on Cloud Run.
  2. Deploy the container on Cloud Run on GKE.
  3. Deploy the container on App Engine Flexible.
  4. Deploy the container on GKE with cluster autoscaling and horizontal pod autoscaling enabled.

Answer(s): A


Reference:

https://cloud.google.com/kubernetes-engine/docs/tutorials/hello-app



  PDF
Viewing page 14 of 69
Viewing questions 66 - 70 out of 391 questions


Post your Comments and Discuss Google Associate Cloud Engineer exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!