You want to configure 10 Compute Engine instances for availability when maintenance occurs.
Your requirements state that these instances should attempt to automatically restart if they crash.
Also, the instances should be highly available including during system maintenance. What should you do?

• A.Create an instance group for the instances.
  Set the `Autohealing' health check to healthy (HTTP).
• B.Create an instance template for the instances.
  `Automatic Restart' to off. Set `On-host maintenance' to Terminate VM instances.
  Add the instance template to an instance group.
• C.Create an instance template for the instances.
  Set the `Automatic Restart' to on. Set the `On-host maintenance' to Migrate VM instance.
  Add the instance template to an intsance group.
• D.Create an instance group for the instance.
  Verify that the `Advanced creation options' setting for `do not retry machine creation' is set to off.

Comment: *

Name: *

Email: *

Verification: *

You've deployed a microservice called myapp1 to a Google Kubernetes Engine cluster using the YAML file specified below:

You need to refactor this configuration so that the database password is not stored in plain text. You want to follow Google-recommended practices. What should you do?

• A.Store the database password inside the Docker image of the container, not in the YAML file.
• B.Store the database password inside a Secret object. Modify the YAML file to populate the DB_PASSWORD environment variable from the Secret.
• C.Store the database password inside a ConfigMap object. Modify the YAML file to populate the DB_PASSWORD environment variable from the ConfigMap.
• D.Store the database password in a file inside a Kubernetes persistent volume, and use a persistent volume claim to mount the volume to the container.

Comment: *

Name: *

Email: *

Verification: *

You have a website hosted on App Engine standard environment. You want 1% of your users to see a new test version of the website. You want to minimize complexity. What should you do?

• A.Deploy the new version in the same application and use the --migrate option.
• B.Create a new App Engine application in the same project. Deploy the new version in that application.
  Configure your network load balancer to send 1% of the traffic to that new application.
• C.Deploy the new version in the same application and use the --splits option to give a weight of 99 to the current version and a weight of 1 to the new version.
• D.Create a new App Engine application in the same project. Deploy the new version in that application.
  Use the App Engine library to proxy 1% of the requests to the new version.

Comment: *

Name: *

Email: *

Verification: *

You recently received a new Google Cloud project with an attached billing account where you will work. You need to create instances, set firewalls, and store data in Cloud Storage. You want to follow Google-recommended practices. What should you do?

• A.Open the Google Cloud console and run gcloud init --project in a Cloud Shell.
• B.Open the Google Cloud console and enable all Google Cloud APIs from the API dashboard.
• C.Use the gcloud services enable compute.googleapis.com command to enable Compute Engine and the gcloud services enable storage-api.googleapis.com command to enable the Cloud Storage APIs.
• D.Use the gcloud CLI services enable cloudresourcemanager.googleapis.com command to enable all resources.

Comment: *

Name: *

Email: *

Verification: *