Associate-Cloud-Engineer Practice Questions

A.  

Create an instance template that contains valid syntax which will be used by the instance group. Delete any persistent disks with the same name as instance names.

B.  

Create an instance template that contains valid syntax that will be used by the instance group. Verify that the instance name and persistent disk name values are not the same in the template.

C.  

Verify that the instance template being used by the instance group contains valid syntax. Delete any persistent disks with the same name as instance names. Set the disks.autoDelete property to true in the instance template.

D.  

Delete the current instance template and replace it with a new instance template. Verify that the instance name and persistent disk name values are not the same in the template. Set the disks.autoDelete property to true in the instance template.

A.  

Use Dataflow as a platform to run the fine-tuning jobs.

B.  

Use a Compute Engine managed instance group as a platform to deploy Jupyter Notebooks and run fine-tuning jobs.

C.  

Use Google Kubernetes Engine (GKE) and hardware accelerators as a platform to run the fine-tuning jobs.

D.  

Use Cloud Run and GPU as a platform to run the fine-tuning jobs.

A.  

Modify the cluster ' s node pool machine type and choose a machine type with more memory and CPU.

B.  

Configure a Horizontal Pod Autoscaler for each microservice.

C.  

Configure GKE cluster autoscaling.

D.  

Configure a Vertical Pod Autoscaler for each microservice.

A.  

Create an HTTP load balancer with a backend configuration that references an existing instance group. Set the health check to healthy (HTTP).

B.  

Create an HTTP load balancer with a backend configuration that references an existing instance group. Define a balancing mode and set the maximum RPS to 10.

C.  

Create a managed instance group. Set the Autohealing health check to healthy (HTTP).

D.  

Create a managed instance group. Verify that the autoscaling setting is on.

A.  

Enable the BigQuery API and ensure that the BigQuery User IAM role is selected. Change the BigQuery dataset to select a data location.

B.  

Create a Cloud Billing account. Enable the BigQuery Data Transfer Service API to export pricing data.

C.  

Enable Cloud Billing data export to BigQuery when you create a Cloud Billing account.

D.  

Enable Cloud Billing on the project and link a Cloud Billing account. Then view the billing data table in the BigQuery dataset.

A.  

Use the command gcloud auth login and point it to the private key

B.  

Use the command gcloud auth activate-service-account and point it to the private key

C.  

Place the private key file in the installation directory of the Cloud SDK and rename it to " credentials ison "

D.  

Place the private key file in your home directory and rename it to ‘’GOOGLE_APPUCATION_CREDENTiALS " .

A.  

Migrate the users to Active Directory. Connect the Human Resources system to Active Directory. Turn on Google Cloud Directory Sync (GCDS) for Cloud Identity. Turn on Identity Federation from Cloud Identity to Active Directory.

B.  

Organize the users in Cloud Identity into groups. Enforce multi-factor authentication in Cloud Identity.

C.  

Turn on identity federation between Cloud Identity and Google Workspace. Enforce multi-factor authentication for domain wide delegation.

D.  

Use a third-party identity provider service through federation. Synchronize the users from Google Workplace to the third-party provider in real time.

A.  

Run gcloud auth login, enter your login credentials in the dialog window, and paste the received login token to gcloud CLI.

B.  

Create a Google Cloud service account, and download the service account key. Place the key file in a folder on your machine where gcloud CLI can find it.

C.  

Download your Cloud Identity user account key. Place the key file in a folder on your machine where gcloud CLI can find it.

D.  

Run gcloud config set compute/zone $my_zone to set the default zone for gcloud CLI.

E.  

Run gcloud config set project $my_project to set the default project for gcloud CLI.

A.  

Grant yourself the IAM role of Cloud Spanner Admin

B.  

Create a new VPC network with subnetworks in all desired regions

C.  

Configure your Cloud Spanner instance to be multi-regional

D.  

Enable the Cloud Spanner API

A.  

Rely on live migration to move the workload to a machine with more memory.

B.  

Use gcloud to add metadata to the VM. Set the key to required-memory-size and the value to 8 G

B.  

C.  

Stop the VM, change the machine type to n1-standard-8, and start the VM.

D.  

Stop the VM, increase the memory to 8 GB, and start the VM.