Ace Cloud

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?

• Link the acquired company's projects to your company's billing account.

• Configure the acquired company's billing account and your company's billing account to export

  the billing data into the same BigQuery dataset.

• Migrate the acquired company's projects into your company's GCP organization. Link the

  migrated projects to your company's billing account.

• 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.

You built an application on Google Cloud that uses Cloud Spanner. Your support team needs to

monitor the environment but should not have access to table data.

You need a streamlined solution to grant the correct permissi ons to your support team, and you

want to follow Google-recommended practices. What should you do?

• Add the support team group to the roles/monitoring.viewer role

• Add the support team group to the roles/spanner.databaseUser role.

• Add the support team group to the roles/spanner.databaseReader role.

• Add the support team group to the roles/stackdriver.accounts.viewer role.

For analysis purposes, you need to send all the logs from all of your Compute Engine instances to

a BigQuery dataset called platform-logs. You have already installed the Cloud Logging agent on all

the instances. You want to minimize cost. What should you do?

• 1. Give the BigQuery Data Editor role on the platform-logs dataset to the service accounts used

  by your instances. 2. Update your instances' metadata to add the following value: logs-

  destination: bq://platform-logs

• 1. In Cloud Logging, create a logs export with a Cloud Pub/Sub topic called logs as a sink. 2.

  Create a Cloud Function that is triggered by messages in the logs topic. 3. Configure that Cloud

  Function to drop logs that are not from Compute Engine and to insert Compute Engine logs in the

  platform-logs dataset.

• 1. In Cloud Logging, create a filter to view only Compute Engine logs. 2. Click Create Export. 3.

  Choose BigQuery as Sink Service, and the platform-logs dataset as Sink Destination.

• 1. Create a Cloud Function that has the BigQuery User role on the platform-logs dataset. 2.

  Configure this Cloud Function to create a BigQuery Job that executes this query: INSERT INTO

  dataset.platform-logs (timestamp, log) SELECT timestamp, log FROM compute.logs WHERE

  timestamp > DATE_SUB(CURRENT_DATE(), INTERVAL 1 DAY) 3. Use Cloud Scheduler to trigger

  this Cloud Function once a day.

You are using Deployment Manager to create a Google Kubernetes Engine cluster. Using the same

Deployment Manager deployment, you also want to create a

DaemonSet in the kube-system namespace ofthe cluster. You want a solution that uses the fewest

possible services. What should you do?

• Add the cluster's API as a new Type Provider in Deployment Manager, and use the new type to

  create the DaemonSet

• Use the Deployment Manager Runtime Configurator to create a new Config resource that

  contains the DaemonSet definition.

• With Deployment Manager, create a Compute Engine instance with a startup script that uses

  kubectl to create the DaemonSet.

• In the cluster's definition in Deployment Manager, add a metadata that has kube-system as key

  and the DaemonSet manifest as value.

You are building an applicati on that will run in your data center. The application will use Google

Cloud Platform (GCP) services like AutoML. You created a service account that has appropriate

access to AutoML. You need to enable authentication to the APIs from your on-premises

environment. What should you do?

• Use service account credentials in your on-premises application.

• Use gcloud to create a key file for the service account that has appropriate permissions

• Set up direct interconnect between your data center and Google Cloud Platform to enable

  authentication for your on-premises applications.

• Go to the IAM & admin console, grant a user account permissions similar to the service

  account permissions, and use this user account for authentication from your data center.

You are using Container Registry to centrally store your company's container images in a separate

project. In another project, you want to create a Google

Kubernetes Engine (GKE) cluster. You want to ensure that Kubernetes can download images from

Container Registry. What should you do?

• In the project where the images are stored, grant the Storage Object Viewer IAM role to the

  service account used by the Kubernetes nodes.

• When you create the GKE cluster, choose the Allow full access to all Cloud APIs option under

  'Access scopes'.

• Create a service account, and give it access to Cloud Storage. Create a P12 key for this service

  account and use it as an imagePullSecrets in Kubernetes.

• Configure the ACLs on each image in Cloud Storage to give read-only access to the default

  Compute Engine service account .

You deployed a new application inside your Google Kubernetes Engine cluster using the YAML file

specified below.

• Review details of the myapp-service Service object and check for error messages.

• Review details of the myapp-deployment Deployment object and check for error messages

• Review details of myapp-deployment-58ddbbb995-lp86m Pod and check for warning

  messages.

• View logs of the container in myapp-deployment-58ddbbb995-lp86m pod and check for

  warning messages.

You are setting up a Windows VM on Compute Engine and want to make sure you can log in to the

VM via RDP. What should you do?

• After the VM has been created, use your Google Account credentials to log in into the VM.

• After the VM has been created, use gcloud compute reset-windows-password to retrieve the

  login credentials for the VM.

• When creating the VM, add metadata to the instance using 'windows-password' as the key and

  a password as the value

• After the VM has been created, download the JSON private key for the default Compute Engine

  service account. Use the credentials in the JSON file to log in to the VM.