Question 1

You want to set up a Google Kubernetes Engine cluster Verifiable node identity and integrity are required for the cluster, and nodes cannot be accessed from the internet. You want to reduce the operational cost of managing your cluster, and you want to follow Google-recommended practices. What should you do?

ADeploy a private autopilot cluster

BDeploy a public autopilot cluster.

CDeploy a standard public cluster and enable shielded nodes.

DDeploy a standard private cluster and enable shielded nodes.

Answer : D

Question 2

An external member of your team needs list access to compute images and disks in one of your projects. You want to follow Google-recommended practices when you grant the required permissions to this user. What should you do?

ACreate a custom role, and add all the required compute.disks.list and compute, images.list permissions as includedPermissions. Grant the custom role to the user at the project level.

BCreate a custom role based on the Compute Image User role Add the compute.disks, list to the
includedPermissions field Grant the custom role to the user at the project level

CGrant the Compute Storage Admin role at the project level.

DCreate a custom role based on the Compute Storage Admin role. Exclude unnecessary permissions from the custom role. Grant the custom role to the user at the project level.

Answer : B

Question 3

Your company wants to migrate their on-premises workloads to Google Cloud. The current on-premises workloads consist of:

* A Flask web application

* AbackendAPI

* A scheduled long-running background job for ETL and reporting.

You need to keep operational costs low You want to follow Google-recommended practices to migrate these workloads to serverless solutions on Google Cloud. What should you do?

AMigrate the web application to App Engine and the backend API to Cloud Run Use Cloud Tasks to run your background job on Compute Engine

BMigrate the web application to App Engine and the backend API to Cloud Run. Use Cloud Tasks to run your background job on Cloud Run.

CRun the web application on a Cloud Storage bucket and the backend API on Cloud Run Use Cloud Tasks to run your background job on Cloud Run.

DRun the web application on a Cloud Storage bucket and the backend API on Cloud Run. Use Cloud Tasks to run your background job on Compute Engine

Answer : B

Question 4

You are building a data lake on Google Cloud for your Internet of Things (loT) application. The loT application has millions of sensors that are constantly streaming structured and unstructured data to your backend in the cloud. You want to build a highly available and resilient architecture based on Google-recommended practices. What should you do?

AStream data to Pub/Sub, and use Dataflow to send data to Cloud Storage

BStream data to Pub/Sub. and use Storage Transfer Service to send data to BigQuery.

CStream data to Dataflow, and use Storage Transfer Service to send data to BigQuery.

DStream data to Dataflow, and use Dataprep by Trifacta to send data to Bigtable.

Answer : B

Question 5

You are deploying a web application using Compute Engine. You created a managed instance group (MIG) to host the application. You want to follow Google-recommended practices to implement a secure and highly available solution. What should you do?

AUse SSL proxy load balancing for the MIG and an A record in your DNS private zone with the load balancer's IP address.

BUse SSL proxy load balancing for the MIG and a CNAME record in your DNS public zone with the load balancer's IP address.

CUse HTTP(S) load balancing for the MIG and a CNAME record in your DNS private zone with the load balancer's IP address.

DUse HTTP(S) load balancing for the MIG and an A record in your DNS public zone with the load balancer's IP address.

Answer : D

HTTP(S) load balancing is a Google-recommended practice for distributing web traffic across multiple regions and zones, and providing high availability, scalability, and security for web applications. It supports both IPv4 and IPv6 addresses, and can handle SSL/TLS termination and encryption. It also integrates with Cloud CDN, Cloud Armor, and Cloud Identity-Aware Proxy for enhanced performance and protection. A MIG can be used as a backend service for HTTP(S) load balancing, and can automatically scale and heal the VM instances that host the web application.

To configure DNS for HTTP(S) load balancing, you need to create an A record in your DNS public zone with the load balancer's IP address. This will map your domain name to the load balancer's IP address, and allow users to access your web application using the domain name. A CNAME record is not recommended, as it can cause latency and DNS resolution issues. A private zone is not suitable, as it is only visible within your VPC network, and not to the public internet.

HTTP(S) Load Balancing documentation

Setting up DNS records for HTTP(S) load balancing

Choosing a load balancer

Free Google Associate Cloud Engineer Questions for Google Associate Cloud Engineer Exam as PDF & Practice Test Software

Question 1

Question 2

Question 3

Question 4

Question 5