You have a Dockerfile that you need to deploy on Kubernetes Engine. What should you do?

• A.Use kubectl app deploy <dockerfilename>.
• B.Create a docker image from the Dockerfile and upload it to Container Registry.
  Create a Deployment YAML file to point to that image.
  Use kubectl to create the deployment with that file.
• C.Create a docker image from the Dockerfile and upload it to Cloud Storage.
  Create a Deployment YAML file to point to that image.
  Use kubectl to create the deployment with that file.
• D.Use gcloud app deploy <dockerfilename>.

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

Comment: *

Name: *

Email: *

Verification: *

Your company has an existing GCP organization with hundreds of projects and a billing account. Your company recently acquired another company that also has hundreds of projects and its own billing account.
You would like to consolidate all GCP costs of both GCP organizations onto a single invoice. You would like to consolidate all costs as of tomorrow. What should you do?

• A.Configure the acquired company's billing account and your company's billing account to export the billing data into the same BigQuery dataset.
• B.Migrate the acquired company's projects into your company's GCP organization. Link the migrated projects to your company's billing account.
• C.Link the acquired company's projects to your company's billing account.
• D.Create a new GCP organization and a new billing account. Migrate the acquired company's projects and your company's projects into the new GCP organization and link the projects to the new billing account.

Comment: *

Name: *

Email: *

Verification: *

You need to set a budget alert for use of Compute Engineer services on one of the three Google Cloud Platform projects that you manage. All three projects are linked to a single billing account. What should you do?

• A.Verify that you are project administrator. Select the associated billing account and create a budget and a custom alert.
• B.Verify that you are the project administrator. Select the associated billing account and create a budget for the appropriate project.
• C.Verify that you are the project billing administrator. Select the associated billing account and create a budget and a custom alert.
• D.Verify that you are the project billing administrator. Select the associated billing account and create a budget and alert for the appropriate project.

Comment: *

Name: *

Email: *

Verification: *

Your organization uses Active Directory (AD) to manage user identities. Each user uses this identity for federated access to various on-premises systems. Your security team has adopted a policy that requires users to log into Google Cloud with their AD identity instead of their own login.
You want to follow the Google-recommended practices to implement this policy.
What should you do?

• A.Sync Identities with Cloud Directory Sync, and then enable SAML for single sign-on
• B.Sync identities with 3rd party LDAP sync, and then copy passwords to allow simplified login with (he same credentials
• C.Sync identities with Cloud Directory Sync, and then copy passwords to allow simplified login with the same credentials.
• D.Sync Identities in the Google Admin console, and then enable Oauth for single sign-on

Comment: *

Name: *

Email: *

Verification: *