You are planning to migrate a database and a backend application to a Standard Google Kubernetes Engine (GKE) cluster. You need to prevent data loss and make sure there are enough nodes available for your backend application based on the demands of your workloads. You want to follow Google-recommended practices and minimize the amount of manual work required. What should you do?

• A.Run your database as a Deployment. Configure cluster autoscaling to handle changes in the demands of your workloads.
• B.Run your database as a single Pod. Run the resize command when you notice changes in the demands of your workloads.
• C.Run your database as a StatefulSet. Configure cluster autoscaling to handle changes in the demands of your workloads.
• D.Run your database as a DaemonSet. Run the resize command when you notice changes in the demands of your workloads.

Comment: *

Name: *

Email: *

Verification: *

Every employee of your company has a Google account. Your operational team needs to manage a large number of instances on Compute Engine. Each member of this team needs only administrative access to the servers. Your security team wants to ensure that the deployment of credentials is operationally efficient and must be able to determine who accessed a given instance. What should you do?

• A.Generate a new SSH key pair. Give the private key to each member of your team.
  Configure the public key in the metadata of each instance.
• B.Ask each member of the team to generate a new SSH key pair and to send you their public key.
  Use a configuration management tool to deploy those keys on each instance.
• C.Ask each member of the team to generate a new SSH key pair and to add the public key to their Google account.
  Grant the "compute.osAdminLogin" role to the Google group corresponding to this team.
• D.Generate a new SSH key pair. Give the private key to each member of your team.
  Configure the public key as a project-wide public SSH key in your Cloud Platform project and allow project-wide public SSH keys on each instance.

Comment: *

Name: *

Email: *

Verification: *

You're about to deploy your team's App Engine application. They're using the Go runtime with a Standard Environment. Which command should you use to deploy the application?

• A.gcloud app-engine deploy app.yaml
• B.gcloud app-engine apply app.yaml
• C.gcloud app apply app.yaml
• D.gcloud app deploy app.yaml

Comment: *

Name: *

Email: *

Verification: *

You have a Linux VM that must connect to Cloud SQL. You created a service account with the appropriate access rights. You want to make sure that the VM uses this service account instead of the default Compute Engine service account. What should you do?

• A.Download a JSON Private Key for the service account. On the Project Metadata, add that JSON as the value for the key compute-engine-service-account.
• B.When creating the VM via the web console, specify the service account under the 'Identity and API Access' section.
• C.Download a JSON Private Key for the service account. On the Custom Metadata of the VM, add that JSON as the value for the key compute-engine-service-account.
• D.Download a JSON Private Key for the service account. After creating the VM, ssh into the VM and save the JSON under ~/.gcloud/compute-engine-service-account.json.

Comment: *

Name: *

Email: *

Verification: *

Your company has a 3-tier solution running on Compute Engine. The configuration of the current infrastructure is shown below.

Each tier has a service account that is associated with all instances within it. You need to enable communication on TCP port 8080 between tiers as follows:
* Instances in tier #1 must communicate with tier #2.
* Instances in tier #2 must communicate with tier #3.
What should you do?

• A.1. Create an ingress firewall rule with the following settings:* Targets: all instances* Source filter: IP ranges (with the range set to 10.0.2.0/24)* Protocols: allow all2. Create an ingress firewall rule with the following settings:* Targets: all instances* Source filter: IP ranges (with the range set to 10.0.1.0/24)* Protocols: allow all
• B.1. Create an ingress firewall rule with the following settings:* Targets: all instances with tier #2 service account* Source filter: all instances with tier #1 service account* Protocols: allow TCP:80802. Create an ingress firewall rule with the following settings:* Targets: all instances with tier #3 service account* Source filter: all instances with tier #2 service account* Protocols: allow TCP: 8080
• C.1. Create an ingress firewall rule with the following settings:* Targets: all instances with tier #2 service account* Source filter: all instances with tier #1 service account* Protocols: allow all2. Create an ingress firewall rule with the following settings:* Targets: all instances with tier #3 service account* Source filter: all instances with tier #2 service account* Protocols: allow all
• D.1. Create an egress firewall rule with the following settings:* Targets: all instances* Source filter: IP ranges (with the range set to 10.0.2.0/24)* Protocols: allow TCP: 80802. Create an egress firewall rule with the following settings:* Targets: all instances* Source filter: IP ranges (with the range set to
  10.0.1.0/24)* Protocols: allow TCP: 8080

Comment: *

Name: *

Email: *

Verification: *