A.  

B.  

C.  

D.  

A.  

Grant the financial team the IAM role of ג€Billing Account Userג€ on the billing account linked to your credit card.

B.  

Set up BigQuery billing export and grant your financial department IAM access to query the data.

C.  

Create a ticket with Google Billing Support to ask them to send the invoice to your company.

D.  

Change the billing account of your projects to the billing account of your company.

A.  

1. Create a subnetwork in the same VPC, in europe-west1.2. Create the new instance in the new subnetwork and use the first instance's private address as the endpoint.

B.  

1. Create a VPC and a subnetwork in europe-west1.2. Expose the application with an internal load balancer.3. Create the new instance in the new subnetwork and use the load balancer's address as the endpoint.

C.  

1. Create a subnetwork in the same VPC, in europe-west1.2. Use Cloud VPN to connect the two subnetworks.3. Create the new instance in the new subnetwork and use the first instance's private address as the endpoint.

D.  

1. Create a VPC and a subnetwork in europe-west1.2. Peer the 2 VPCs.3. Create the new instance in the new subnetwork and use the first instance's private address as the endpoint.

A.  

gcloud deployment-manager deployments create my-gcp-ace-cluster --config cluster.yaml

B.  

gcloud deployment-manager deployments create my-gcp-ace-cluster --type container.v1.cluster --config cluster.yaml

C.  

gcloud deployment-manager deployments apply my-gcp-ace-cluster --type container.v1.cluster --config cluster.yaml

D.  

gcloud deployment-manager deployments apply my-gcp-ace-cluster --config cluster.yaml

A.  

Save file automatic first-of-the- month backup for three years Store the backup file in an Archive class Cloud Storage bucket

B.  

Convert the automatic first-of-the-month backup to an export file Write the export file to a Coldline class Cloud Storage bucket

C.  

Set up an export job for the first of the month Write the export file to an Archive class Cloud Storage bucket

D.  

Set up an on-demand backup tor the first of the month Write the backup to an Archive class Cloud Storage bucket

A.  

Run gcloud compute instances list to get the IP address of the instance, then use the ssh command.

B.  

Use the gcloud compute ssh command.

C.  

Create a key with the ssh-keygen command. Then use the gcloud compute ssh command.

D.  

Create a key with the ssh-keygen command. Upload the key to the instance. Run gcloud compute instances list to get the IP address of the instance, then use the ssh command.

A.  

Deploy the container on Cloud Run for Anthos, and set the minimum number of instances to zero

B.  

Deploy the container on Cloud Run (fully managed), and set the minimum number of instances to zero.

C.  

Deploy the container on App Engine flexible environment with autoscaling. and set the value min_instances to zero in the app yaml

D.  

Deploy the container on App Engine flexible environment with manual scaling, and set the value instances to zero in the app yaml

A.  

Create a bash script that contains all requirement steps as gcloud commands

B.  

Develop templates for the environment using Cloud Deployment Manager

C.  

Use curl in a terminal to send a REST request to the relevant Google API for each individual resource.

D.  

Use the Cloud Console interface to provision and manage all related resources

A.  

Migrate from MySQL to Cloud SQL, from Kafka to Memorystore, and from Cloud SQL for PostgreSQL to Cloud SQL

B.  

Migrate from MySQL to Cloud Spanner, from Kafka to Memorystore, and from Cloud SOL for PostgreSQL to Cloud SQL

C.  

Migrate from MySQL to Cloud SOL, from Kafka to Pub/Sub, and from Cloud SOL for PostgreSQL to BigQuery.

D.  

Migrate from MySQL to Cloud Spanner, from Kafka to Pub/Sub. and from Cloud SQL for PostgreSQL to BigQuery

A.  

Use Cloud Bigtable for data storage.

B.  

Use Cloud SQL for data storage.

C.  

Use Cloud Spanner for data storage.

D.  

Use Firestore for data storage.

A.  

When creating the VM via the web console, specify the service account under the ‘Identity and API Access’ section.

B.  

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.

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.

A.  

Use Binary Authorization and whitelist only the container images used by your customers’ Pods.

B.  

Use the Container Analysis API to detect vulnerabilities in the containers used by your customers’ Pods.

C.  

Create a GKE node pool with a sandbox type configured to gvisor. Add the parameter runtimeClassName: gvisor to the specification of your customers’ Pods.

D.  

Use the cos_containerd image for your GKE nodes. Add a nodeSelector with the value cloud.google.com/gke-os-distribution: cos_containerd to the specification of your customers’ Pods.

A.  

Add the cluster’s API as a new Type Provider in Deployment Manager, and use the new type to create the DaemonSet.

B.  

Use the Deployment Manager Runtime Configurator to create a new Config resource that contains the DaemonSet definition.

C.  

With Deployment Manager, create a Compute Engine instance with a startup script that uses kubectl to create the DaemonSet.

D.  

In the cluster’s definition in Deployment Manager, add a metadata that has kube-system as key and the DaemonSet manifest as value.

A.  

1. Build an instruction guide to install Cassandra on GCP.

2. Make the instruction guide accessible to your developers.

B.  

1. Advise your developers to go to Cloud Marketplace.

2. Ask the developers to launch a Cassandra image for their development work.

C.  

1. Build a Cassandra Compute Engine instance and take a snapshot of it.

2. Use the snapshot to create instances for your developers.

D.  

1. Build a Cassandra Compute Engine instance and take a snapshot of it.

2.Upload the snapshot to Cloud Storage and make it accessible to your developers.

3.Build instructions to create a Compute Engine instance from the snapshot so that developers can do it themselves.

A.  

Write a script that runs gsutil Is -| – gs://myapp-gcp-ace-logs/** to find and remove items older than 90 days. Schedule the script with cron.

B.  

Write a lifecycle management rule in JSON and push it to the bucket with gsutil lifecycle set config-json-file.

C.  

Write a lifecycle management rule in XML and push it to the bucket with gsutil lifecycle set config-xml-file.

D.  

Write a script that runs gsutil Is -Ir gs://myapp-gcp-ace-logs/** to find and remove items older than 90 days. Repeat this process every morning.

A.  

Add the users to roles/browser role.

B.  

Add the users to roles/iam.roleViewer role.

C.  

Add the users to a group, and add this group to roles/browser role.

D.  

Add the users to a group, and add this group to roles/iam.roleViewer role.

A.  

BigQuery

B.  

Cloud SQL

C.  

Cloud Spanner

D.  

Cloud Datastore

A.  

• Add a step for human approval to the CI/CD pipeline before the execution of the infrastructure

provisioning.

• Use the human approvals IAM account for the provisioning.

B.  

• Attach a single service account to the compute instances.

• Add minimal rights to the service account.

• Allow the service account to impersonate a Cloud Identity user with elevated permissions to create, update, or delete resources.

C.  

• Attach a single service account to the compute instances.

• Add all required Identity and Access Management (IAM) permissions to this service account to create, update, or delete resources

D.  

• Create multiple service accounts, one for each pipeline with the appropriate minimal Identity and

Access Management (IAM) permissions.

• Use a secret manager service to store the key files of the service accounts.

• Allow the CI/CD pipeline to request the appropriate secrets during the execution of the pipeline.

A.  

Create a GKE Autopilot cluster. Enroll the cluster in the rapid release channel.

B.  

Create a GKE Autopilot cluster. Enroll the cluster in the stable release channel.

C.  

Create a zonal GKE standard cluster. Enroll the cluster in the stable release channel.

D.  

Create a regional GKE standard cluster. Enroll the cluster in the rapid release channel.

A.  

Open the Cloud Spanner console to review configurations.

B.  

Open the IAM & admin console to review IAM policies for Cloud Spanner roles.

C.  

Go to the Stackdriver Monitoring console and review information for Cloud Spanner.

D.  

Go to the Stackdriver Logging console, review admin activity logs, and filter them for Cloud Spanner IAM roles.

A.  

Run gcloud app restore.

B.  

On the App Engine page of the GCP Console, select the application that needs to be reverted and click Revert.

C.  

On the App Engine Versions page of the GCP Console, route 100% of the traffic to the previous version.

D.  

Deploy the original version as a separate application. Then go to App Engine settings and split traffic between applications so that the original version serves 100% of the requests.

A.  

Select the MIG from the Compute Engine console and, in the menu, select Replace VMs.

B.  

Use the gcloud compute instance-groups managed recreate-instances command to recreate theVM.

C.  

Use the gcloud compute instances update command with a REFRESH action for the VM.

D.  

Update and apply the instance template of the MIG.

A.  

Load data in Cloud Datastore and run a SQL query against it.

B.  

Create a BigQuery table and load data in BigQuery. Run a SQL query on this table and drop this table after you complete your request.

C.  

Create external tables in BigQuery that point to Cloud Storage buckets and run a SQL query on these external tables to complete your request.

D.  

Create a Hadoop cluster and copy the AVRO file to NDFS by compressing it. Load the file in a hive table and provide access to your analysts so that they can run SQL queries.

A.  

Use kubectl app deploy .

B.  

Use gcloud app deploy .

C.  

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.

D.  

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.

A.  

Cloud Run for Anthos

B.  

Cloud Run

C.  

App Engine Standard

D.  

Cloud Functions.

A.  

Create a Google Kubernetes Engine cluster, and use horizontal pod autoscaling to scale the application.

B.  

Create an instance template, and use the template in a managed instance group with autoscaling configured.

C.  

Create an instance template, and use the template in a managed instance group that scales up and down based on the time of day.

D.  

Use a set of third-party tools to build automation around scaling the application up and down, based on Stackdriver CPU usage monitoring.

A.  

Reserve a new static external IP address and assign the new IP address to the VM.

B.  

Promote the existing IP address of the VM to become a static external IP address.

C.  

Reserve a new static external IPv6 address and assign the new IP address to the VM.

D.  

Promote the existing IP address of the VM to become a static internal IP address.

A.  

Use your existing CI/CD pipeline Use the generated Docker images and deploy them to Cloud Run. Update the configurations and the required endpoints.

B.  

Use your existing continuous integration and delivery (CI/CD) pipeline. Use the generated Docker images and deploy them to Cloud Function. Use the same configuration as on-premises.

C.  

Use the existing codebase and deploy each service as a separate Cloud Function Update the configurations and the required endpoints.

D.  

Use your existing codebase and deploy each service as a separate Cloud Run Use the same configurations as on-premises.

A.  

Create a service account with an access scope. Use the access scope ‘https://www.googleapis.com/auth/devstorage.write_only’.

B.  

Create a service account with an access scope. Use the access scope ‘https://www.googleapis.com/auth/cloud-platform’.

C.  

Create a service account and add it to the IAM role ‘storage.objectCreator’ for that bucket.

D.  

Create a service account and add it to the IAM role ‘storage.objectAdmin’ for that bucket.

A.  

Deploy me application on App Engine For each update, create a new version of the same service Configure traffic splitting to send a small percentage of traffic to the new version

B.  

Deploy the application on App Engine For each update, create a new service Configure traffic splitting to send a small percentage of traffic to the new service.

C.  

Deploy the application on Kubernetes Engine For a new release, update the deployment to use the new version

D.  

Deploy the application on Kubernetes Engine For a now release, create a new deployment for the new version Update the service e to use the now deployment.

A.  

Verify that you are the project billing administrator. Select the associated billing account and create a budget and alert for the appropriate project.

B.  

Verify that you are the project billing administrator. Select the associated billing account and create a budget and a custom alert.

C.  

Verify that you are the project administrator. Select the associated billing account and create a budget for the appropriate project.

D.  

Verify that you are project administrator. Select the associated billing account and create a budget and a custom alert.

A.  

Use the GCP Console to transfer the file instead of gsutil.

B.  

Enable parallel composite uploads using gsutil on the file transfer.

C.  

Decrease the TCP window size on the machine initiating the transfer.

D.  

Change the storage class of the bucket from Nearline to Multi-Regional.

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.

A.  

Use gcloud to expand the IP range of the current subnet.

B.  

Delete the subnet, and recreate it using a wider range of IP addresses.

C.  

Create a new project. Use Shared VPC to share the current network with the new project.

D.  

Create a new subnet with the same starting IP but a wider range to overwrite the current subnet.

A.  

Open the Google Cloud console, and run a query to determine which resources this service account can access.

B.  

Open the Google Cloud console, and run a query of the audit logs to find permission denied errors for this service account.

C.  

Open the Google Cloud console, and check the organization policies.

D.  

Open the Google Cloud console, and check the Identity and Access Management (IAM) roles assigned to the service account at the project or inherited from the folder or organization levels.

A.  

Upload the code to Cloud Functions. Use Cloud Scheduler to start the application.

B.  

Create a container for the set of binaries. Use Cloud Scheduler to start a Cloud Run job for the container.

C.  

Create a container for the set of binaries Deploy the container to Google Kubernetes Engine (GKE) and use the Kubernetes scheduler to start the application.

D.  

Lift and shift to a VM on Compute Engine. Use an instance schedule to start and stop the instance.

A.  

gcloud deployment-manager deployments create --config

B.  

gcloud deployment-manager deployments update --config

C.  

gcloud deployment-manager resources create --config

D.  

gcloud deployment-manager resources update --config

A.  

Enable the Node Auto-Repair feature for your GKE cluster.

B.  

Enable the Node Auto-Upgrades feature for your GKE cluster.

C.  

Select the latest available cluster version for your GKE cluster.

D.  

Select “Container-Optimized OS (cos)” as a node image for your GKE cluster.

A.  

Create a Service Account in your own project, and grant this Service Account access to BigGuery in your project

B.  

Create a Service Account in your own project, and ask the partner to grant this Service Account access to BigQuery in their project

C.  

Ask the partner to create a Service Account in their project, and have them give the Service Account access to BigQuery in their project

D.  

Ask the partner to create a Service Account in their project, and grant their Service Account access to the BigQuery dataset in your project

A.  

Give “project owner” for web-applications appropriate roles to crm-databases- proj

B.  

Give “project owner” role to crm-databases-proj and the web-applications project.

C.  

Give “project owner” role to crm-databases-proj and bigquery.dataViewer role to web-applications.

D.  

Give bigquery.dataViewer role to crm-databases-proj and appropriate roles to web-applications.

A.  

Create the instance with the default Compute Engine service account Grant the service account permissions on Cloud Storage.

B.  

Create the instance with the default Compute Engine service account Add metadata to the objects on Cloud Storage that matches the metadata on the new instance.

C.  

Create a new service account and assig n this service account to the new instance Grant the service account permissions on Cloud Storage.

D.  

Create a new service account and assign this service account to the new instance Add metadata to the objects on Cloud Storage that matches the metadata on the new instance.

A.  

• Ensure that the Ops Agent Is Installed on the Compute Engine instance.

• Create a custom metric in the Cloud Monitoring dashboard.

• Provide the security team member with access to this dashboard.

B.  

• Ensure that the Ops Agent is installed on tie Compute Engine instance.

• Provide the security team member roles/configure.inventoryViewer permission.

C.  

• Ensure that the OS Config agent Is Installed on the Compute Engine instance.

• Provide the security team member roles/configure.vulnerabilityViewer permission.

D.  

• Ensure that the OS Config agent is installed on the Compute Engine instance

• Create a log sink Co a BigQuery dataset.

• Provide the security team member with access to this dataset.

A.  

Create a new project and create an App Engine instance in europe-west3

B.  

Use the gcloud app region set command and supply the name of the new region.

C.  

From the console, under the App Engine page, click edit, and change the region drop-down.

D.  

Contact Google Cloud Support and request the change.

A.  

Deploy a new version of your application in Google Kubernetes Engine instead of App Engine and then use GCP Console to split traffic.

B.  

Deploy a new version of your application in a Compute Engine instance instead of App Engine and then use GCP Console to split traffic.

C.  

Deploy a new version as a separate app in App Engine. Then configure App Engine using GCP Console to split traffic between the two apps.

D.  

Deploy a new version of your application in App Engine. Then go to App Engine settings in GCP Console and split traffic between the current version and newly deployed versions accordingly.

A.  

Fill in local SSD. Fill in persistent disk storage and snapshot storage.

B.  

Fill in local SSD. Add estimated cost for cluster management.

C.  

Select Add GPUs. Fill in persistent disk storage and snapshot storage.

D.  

Select Add GPUs. Add estimated cost for cluster management.

A.  

Store the application data on a zonal persistent disk. Create a snapshot schedule for the disk. If an outage occurs, create a new disk from the most recent snapshot and attach it to a new VM in another zone.

B.  

Store the application data on a zonal persistent disk. If an outage occurs, create an instance in another zone with this disk attached.

C.  

Store the application data on a regional persistent disk. Create a snapshot schedule for the disk. If an outage occurs, create a new disk from the most recent snapshot and attach it to a new VM in another zone.

D.  

Store the application data on a regional persistent disk If an outage occurs, create an instance in another zone with this disk attached.

A.  

Meet with the cloud enablement team to discuss load balancer options.

B.  

Redesign the application to use a distributed user session service that does not rely on WebSockets and HTTP sessions.

C.  

Review the encryption requirements for WebSocket connections with the security team.

D.  

Convert the WebSocket code to use HTTP streaming.

A.  

Use Deployment Manager templates to describe the proposed changes and store them in a Cloud Storage bucket.

B.  

Use Deployment Manager templates to describe the proposed changes and store them in Cloud Source Repositories.

C.  

Apply the change in a development environment, run gcloud compute instances list, and then save the output in a shared Storage bucket.

D.  

Apply the change in a development environment, run gcloud compute instances list, and then save the output in Cloud Source Repositories.

A.  

• Create a custom role with Compute Engine, Cloud Functions, and Cloud SQL permissions in one project within the Google Cloud organization.

• Copy the role across all projects created within the organization with the gcloud iam roles copy command.

• Assign the role to developers in those projects.

B.  

• Add all developers to a Google group in Google Groups for Workspace.

• Assign the predefined role of Compute Admin to the Google group at the Google Cloud organization level.

C.  

• Add all developers to a Google group in Cloud Identity.

• Assign predefined roles for Compute Engine, Cloud Functions, and Cloud SQL permissions to the Google group for each project in the Google Cloud organization.

D.  

• Add all developers to a Google group in Cloud Identity.

• Create a custom role with Compute Engine, Cloud Functions, and Cloud SQL permissions at the Google Cloud organization level.

• Assign the custom role to the Google group.

A.  

Set the europe-west1-d zone as the default zone using the gcloud config subcommand.

B.  

In the Settings page for Compute Engine under Default location, set the zone to europe–west1-d.

C.  

In the CLI installation directory, create a file called default.conf containing zone=europe–west1–d.

D.  

Create a Metadata entry on the Compute Engine page with key compute/zone and value europe–west1–d.

A.  

Use App Engine and configure Cloud Scheduler to trigger the application using Pub/Sub.

B.  

Use Cloud Functions and configure the bucket as a trigger resource.

C.  

Use Google Kubernetes Engine and configure a CronJob to trigger the application using Pub/Sub.

D.  

Use Dataflow as a batch job, and configure the bucket as a data source.

A.  

Use a Deployment Manager script to automate creating storage buckets in an appropriate region

B.  

Use a local SSD to improve performance of the VM for the targeted workload

C.  

Use the gsutii command to create a storage bucket in the same region as the VM

D.  

Use a Persistent Disk SSD in the same zone as the VM to improve performance of the VM

A.  

Grant all members of the DevOps team the role of Project Editor on the organization level.

B.  

Grant all members of the DevOps team the role of Project Editor on the production project.

C.  

Create a custom role that combines the required permissions. Grant the DevOps team the custom role on the production project.

D.  

Create a custom role that combines the required permissions. Grant the DevOps team the custom role on the organization level.

A.  

Create a new subnet in the same region as the subnet being used.

B.  

Add an alias IP range to the subnet used by the GKE clusters.

C.  

Create a new VPC, and set up VPC peering with the existing VP

C.  

D.  

Expand the CIDR range of the relevant subnet for the cluster.

A.  

Create a single budget for all projects and configure budget alerts on this budget.

B.  

Create a separate billing account per sandbox project and enable BigQuery billing exports. Create a Data Studio dashboard to plot the spending per billing account.

C.  

Create a budget per project and configure budget alerts on all of these budgets.

D.  

Create a single billing account for all sandbox projects and enable BigQuery billing exports. Create a Data Studio dashboard to plot the spending per project.

A.  

Assign the auditor the IAM role roles/logging.privateLogViewer. Perform the export of logs to Cloud Storage.

B.  

Assign the auditor the IAM role roles/logging.privateLogViewer. Direct the auditor to also review the logs for changes to Cloud IAM policy.

C.  

Assign the auditor’s IAM user to a custom role that has logging.privateLogEntries.list

permission. Perform the export of logs to Cloud Storage.

D.  

Assign the auditor’s IAM user to a custom role that has logging.privateLogEntries.list

permission. Direct the auditor to also review the logs for changes to Cloud IAM policy.

A.  

Deploy the application lo Cloud. Run. Use gradual rollouts for traffic spelling.

B.  

Deploy the application lo Google Kubemetes Engine. Use Anthos Service Mesh for traffic splitting.

C.  

Deploy the application to Cloud functions. Saucily the version number in the functions name.

D.  

Deploy the application to App Engine. For each new version, create a new service.

A.  

Contact cloud-billing@google.com with your bank account details and request a corporate billing account for your company.

B.  

Create a ticket with Google Support and wait for their call to share your credit card details over the phone.

C.  

In the Google Platform Console, go to the Resource Manage and move all projects to the root Organization.

D.  

In the Google Cloud Platform Console, create a new billing account and set up a payment method.

A.  

Deployment Manager

B.  

Cloud Composer

C.  

Managed Instance Group

D.  

Unmanaged Instance Group

A.  

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 instance group.

B.  

Create an instance template for the instances. Set ‘Automatic Restart’ to off. Set ‘On-host maintenance’ to Terminate VM instances. Add the instance template to an instance group.

C.  

Create an instance group for the instances. Set the ‘Autohealing’ health check to healthy (HTTP).

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.

A.  

Create Java packages that utilize the Google Cloud Client Libraries for Java to configure Google Cloud products. Store and share the packages in a source code repository.

B.  

Create bash scripts that utilize the Google Cloud CLI to configure Google Cloud products. Store and share the bash scripts in a source code repository.

C.  

Create Terraform modules that utilize the Google Cloud Terraform Provider to configure Google Cloud products. Store and share the modules in a source code repository.

D.  

Use the Google Cloud APIs by using curl to configure Google Cloud products. Store and share the curl commands in a source code repository.

A.  

Export Cloud Datastore data using gcloud datastore export.

B.  

Create a Cloud Datastore index using gcloud datastore indexes create.

C.  

Install the google-cloud-sdk-datastore-emulator component using the apt get install command.

D.  

Install the cloud-datastore-emulator component using the gcloud components install command.

A.  

When creating the instances, specify a Service Account for each instance

B.  

When creating the instances, assign the name of each Service Account as instance metadata

C.  

After starting the instances, use gcloud compute instances update to specify a Service Account for each instance

D.  

After starting the instances, use gcloud compute instances update to assign the name of the relevant Service Account as instance metadata

A.  

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

B.  

After the VM has been created, use gcloud compute reset-windows-password to retrieve the login credentials for the VM.

C.  

When creating the VM, add metadata to the instance using ‘windows-password’ as the key and a password as the value.

D.  

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.

A.  

Assign the finance team only the Billing Account User role on the billing account.

B.  

Assign the engineering team only the Billing Account User role on the billing account.

C.  

Assign the finance team the Billing Account User role on the billing account and the Project Billing Manager role on the organization.

D.  

Assign the engineering team the Billing Account User role on the billing account and the Project Billing Manager role on the organization.

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.

A.  

Use the command gcloud config set container/cluster dev.

B.  

Use the command gcloud container clusters update dev.

C.  

Create a file called gke.default in the ~/.gcloud folder that contains the cluster name.

D.  

Create a file called defaults.json in the ~/.gcloud folder that contains the cluster name.

A.  

1. Create a single VPC with a subnet for the DMZ and a subnet for the LAN. 2. Set up firewall rules to open up relevant traffic between the DMZ and the LAN subnets, and another firewall rule to allow public ingress traffic for the DMZ.

B.  

1. Create a single VPC with a subnet for the DMZ and a subnet for the LAN. 2. Set up firewall rules to open up relevant traffic between the DMZ and the LAN subnets, and another firewall rule to allow public egress traffic for the DMZ.

C.  

1. Create a VPC with a subnet for the DMZ and another VPC with a subnet for the LAN. 2. Set up firewall rules to open up relevant traffic between the DMZ and the LAN subnets, and another firewall rule to allow public ingress traffic for the DMZ.

D.  

1. Create a VPC with a subnet for the DMZ and another VPC with a subnet for the LAN. 2. Set up firewall rules to open up relevant traffic between the DMZ and the LAN subnets, and another firewall rule to allow public egress traffic for the DMZ.

A.  

Perform a rolling-action start-update with maxSurge set to 0 and maxUnavailable set to 1.

B.  

Perform a rolling-action start-update with maxSurge set to 1 and maxUnavailable set to 0.

C.  

Create a new managed instance group with an updated instance template. Add the group to the backend service for the load balancer. When all instances in the new managed instance group are healthy, delete the old managed instance group.

D.  

Create a new instance template with the new application version. Update the existing managed instance group with the new instance template. Delete the instances in the managed instance group to allow the managed instance group to recreate the instance using the new instance template.

A.  

Create the instance without a public IP address.

B.  

Create the instance with Private Google Access enabled.

C.  

Create a deny-all egress firewall rule on the VPC network.

D.  

Create a route on the VPC to route all traffic to the instance over the VPN tunnel.

A.  

Your zonal capacity is limited, causing all preemptible VM's to be shutdown torecover capacity. Try deploying your group to another zone.

B.  

You have hit your instance quota for the region.

C.  

Your managed instance group's VM's are toggled to only last 1 minute inpreemptible settings.

D.  

Your managed instance group's health check is repeatedly failing, either to amisconfigured health check or misconfigured firewall rules not allowing the healthcheck to access the instance

A.  

Configure the Horizontal Pod Autoscaler for availability, and configure the cluster autoscaler for suggestions.

B.  

Configure the Horizontal Pod Autoscaler for availability, and configure the Vertical Pod Autoscaler recommendations for suggestions.

C.  

Configure the Vertical Pod Autoscaler recommendations for availability, and configure the Cluster autoscaler for suggestions.

D.  

Configure the Vertical Pod Autoscaler recommendations for availability, and configure the Horizontal Pod Autoscaler for suggestions.

A.  

The pending Pod's resource requests are too large to fit on a single node of the cluster.

B.  

Too many Pods are already running in the cluster, and there are not enough resources left to schedule the pending Pod.

C.  

The node pool is configured with a service account that does not have permission to pull the container image used by the pending Pod.

D.  

The pending Pod was originally scheduled on a node that has been preempted between the creation of the Deployment and your verification of the Pods’ status. It is currently being rescheduled on a new node.

A.  

Create a single custom VPC with 2 subnets. Create each subnet in a different region and with a different CIDR range.

B.  

Create a single custom VPC with 2 subnets. Create each subnet in the same region and with the same CIDR range.

C.  

Create 2 custom VPCs, each with a single subnet. Create each subnet is a different region and with a different CIDR range.

D.  

Create 2 custom VPCs, each with a single subnet. Create each subnet in the same region and with the same CIDR range.

A.  

Use service account credentials in your on-premises application.

B.  

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

C.  

Set up direct interconnect between your data center and Google Cloud Platform to enable authentication for your on-premises applications.

D.  

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.

A.  

Set autoscaling to On, set the minimum number of instances to 1, and then set the maximum number of instances to 1.

B.  

Set autoscaling to Off, set the minimum number of instances to 1, and then set the maximum number of instances to 1.

C.  

Set autoscaling to On, set the minimum number of instances to 1, and then set the maximum number of instances to 2.

D.  

Set autoscaling to Off, set the minimum number of instances to 1, and then set the maximum number of instances to 2.

A.  

Modify the minimum number of Cloud Run instances.

B.  

Set a minimum concurrent requests environment variable for the application.

C.  

Modify the maximum number of Cloud Run instances.

D.  

Use traffic splitting.

A.  

Create a Cloud Bigtable cluster and use the HBase API

B.  

Deploy MongoDB Alias from the Google Cloud Marketplace

C.  

Download a MongoDB installation package and run it on Compute Engine instances

D.  

Download a MongoDB installation package, and run it on a Managed Instance Group

A.  

Create a service account with just the permissions to access files in the bucket. Create a JSON key for the service account. Execute the command gsutil signurl -m 1h gs:///*.

B.  

Create a service account with just the permissions to access files in the bucket. Create a JSON key for the service account. Execute the command gsutil signurl -d 1h gs:///**.

C.  

Create a service account with just the permissions to access files in the bucket. Create a JSON key for the service account. Execute the command gsutil signurl -p 60m gs:///.

D.  

Create a JSON key for the Default Compute Engine Service Account. Execute the command gsutil signurl -t 60m gs:///***

A.  

Upload the image to Cloud Storage and create a Kubernetes Service referencing the image.

B.  

Upload the image to Cloud Storage and create a Kubernetes Deployment referencing the image.

C.  

Upload the image to Container Registry and create a Kubernetes Service referencing the image.

D.  

Upload the image to Container Registry and create a Kubernetes Deployment referencing the image.

A.  

Enable the Identity Aware Proxy API on the project.

B.  

Scan the bucker using the Data Loss Prevention API.

C.  

Allow only a single Service Account access to read the data.

D.  

Enable Data Access audit logs for the Cloud Storage API.

A.  

Increase the size of the disk to 1 TB.

B.  

Increase the allocated CPU to the instance.

C.  

Migrate to use a Local SSD on the instance.

D.  

Migrate to use a Regional SSD on the instance.

A.  

Run gcloud iam roles list. Review the output section.

B.  

Run gcloud iam service-accounts list. Review the output section.

C.  

Navigate to the project and then to the IAM section in the GCP Console. Review the members and roles.

D.  

Navigate to the project and then to the Roles section in the GCP Console. Review the roles and status.

A.  

In the project where the images are stored, grant the Storage Object Viewer IAM role to the service account used by the Kubernetes nodes.

B.  

When you create the GKE cluster, choose the Allow full access to all Cloud APIs option under ‘Access scopes’.

C.  

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.

D.  

Configure the ACLs on each image in Cloud Storage to give read-only access to the default Compute Engine service account.

A.  

For each GCP product in the solution, review the pricing details on the products pricing page. Use the pricing calculator to total the monthly costs for each GCP product.

B.  

For each GCP product in the solution, review the pricing details on the products pricing page. Create a Google Sheet that summarizes the expected monthly costs for each product.

C.  

Provision the solution on GCP. Leave the solution provisioned for 1 week. Navigate to the Billing Report page in the Google Cloud Platform Console. Multiply the 1 week cost to determine the monthly costs.

D.  

Provision the solution on GCP. Leave the solution provisioned for 1 week. Use Stackdriver to determine the provisioned and used resource amounts. Multiply the 1 week cost to determine the monthly costs.