A.  

Check the app.yaml file for your application and check project settings.

B.  

Check the web-application.xml file for your application and check project settings.

C.  

Go to Deployment Manager and review settings for deployment of applications.

D.  

Go to Cloud Shell and run gcloud config list to review the Google Cloud configuration used for deployment.

A.  

Navigate to Stackdriver Logging and select resource.labels.project_id="*"

B.  

Create a Stackdriver Logging Export with a Sink destination to a BigQuery dataset. Configure the table expiration to 60 days.

C.  

Create a Stackdriver Logging Export with a Sink destination to Cloud Storage. Create a lifecycle rule to delete objects after 60 days.

D.  

Configure a Cloud Scheduler job to read from Stackdriver and store the logs in BigQuery. Configure the table expiration to 60 days.

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.  

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.  

Use a proxy Network Load Balancer for the MIG and an A record in your DNS private zone with the load balancer's IP address.

B.  

Use a proxy Network Load Balancer for the MIG and a CNAME record in your DNS public zone with the load balancer's IP address.

C.  

Use an Application Load Balancer for the MIG and a CNAME record in your DNS private zone with the load balancer's IP address.

D.  

Use an Application Load Balancer for the MIG and an A record in your DNS public zone with the load balancer's IP address.

A.  

Select Google Kubernetes Engine. Use a single-node cluster with a small instance type.

B.  

Select Google Kubernetes Engine. Use a three-node cluster with micro instance types.

C.  

Select Compute Engine. Use preemptible VM instances of the appropriate standard machine type.

D.  

Select Compute Engine. Use VM instance types that support micro bursting.

A.  

BigQuery

B.  

Cloud SQL

C.  

Cloud Spanner

D.  

Cloud Datastore

A.  

Deploy an ingress resource on the GKE cluster to expose the API to the internet. Use Cloud Armor to filter for IP addresses that can connect to the API. On the Cloud Run service, configure the application to fetch its public IP address and update the Cloud Armor policy on startup to allow this IP address to call the API on ports 80 and 443.

B.  

Create an egress firewall rule on the VPC to allow connections to 0.0.0.0/0 on ports 80 and 443.

C.  

Create an ingress firewall rule on the VPC to allow connections from 0.0.0.0/0 on ports 80 and 443.

D.  

Deploy an internal Application Load Balancer to expose the API on GKE to the VPC. Configure Cloud DNS with the IP address of the internal Application Load Balancer. Deploy a Serverless VPC Access connector to allow the Cloud Run service to call the API through the FQDN on Cloud DNS.

A.  

Build the solution by using YAML manifests, and provision the resources.

B.  

Build the solution by using Terraform, and provision the resources.

C.  

Build the solution by using Python and the cloud SDKs from all providers to provision the resources.

D.  

Build the solution by using Config Connector, and provision the resources.

A.  

Create an HTTP load balancer with a backend configuration that references an existing instance group. Set the health check to healthy (HTTP).

B.  

Create an HTTP load balancer with a backend configuration that references an existing instance group. Define a balancing mode and set the maximum RPS to 10.

C.  

Create a managed instance group. Set the Autohealing health check to healthy (HTTP).

D.  

Create a managed instance group. Verify that the autoscaling setting is on.

A.  

Enable the BigQuery API and ensure that the BigQuery User IAM role is selected. Change the BigQuery dataset to select a data location.

B.  

Create a Cloud Billing account. Enable the BigQuery Data Transfer Service API to export pricing data.

C.  

Enable Cloud Billing data export to BigQuery when you create a Cloud Billing account.

D.  

Enable Cloud Billing on the project and link a Cloud Billing account. Then view the billing data table in the BigQuery dataset.

A.  

Use kubect1 to delete the topic resource.

B.  

Use gcloud CLI to delete the topic.

C.  

Use kubect1 to create the label deleted-by-cnrm and to change its value to true for the topic resource.

D.  

Use gcloud CLI to update the topic label managed-by-cnrm to false.

A.  

Use Cloud Storage Object Lifecycle Management using Age conditions with SetStorageClass and Delete actions. Set the SetStorageClass action to 90 days and the Delete action to 275 days (365 – 90)

B.  

Use Cloud Storage Object Lifecycle Management using Age conditions with SetStorageClass and Delete actions. Set the SetStorageClass action to 90 days and the Delete action to 365 days.

C.  

Use gsutil rewrite and set the Delete action to 275 days (365-90).

D.  

Use gsutil rewrite and set the Delete action to 365 days.

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.  

Use the gcloud CLI services enablecloudresourcemanager.googleapis.comcommand to enable all resources.

B.  

Use the gcloud services enablecompute.googleapis.comcommand to enable Compute Engineand thegcloud services enablestorage-api.googleapis.comcommand to enable the Cloud Storage APIs.

C.  

Open the Google Cloud console and enable all Google Cloud APIs from the API dashboard.

D.  

Open the Google Cloud console and run gcloud init --project in a Cloud Shell.

A.  

In the Google Cloud console, visualize the costs related to the projects in the Reports section.

B.  

In the Google Cloud console, visualize the costs related to the projects in the Cost breakdown section.

C.  

In the Google Cloud console, use the export functionality of the Cost table. Create a Looker Studiodashboard on top of the CSV export.

D.  

Configure Cloud Billing data export to BigOuery for the billing account. Create a Looker Studio dashboard on top of the BigQuery export.

A.  

Create a Cloud Storage bucket. Establish an Identity and Access Management (IAM) role with write permissions to the bucket. Use the gsutil tool to directly copy files over the network to Cloud Storage.

B.  

Set up a Cloud Interconnect connection between the on-premises network and Google Cloud. Establish a private endpoint for Filestore access. Transfer the data from the existing Network File System (NFS) to Filestore.

C.  

Use Transfer Appliance to request an appliance. Load the data locally, and ship the appliance back to Google for ingestion into Cloud Storage.

D.  

Use Storage Transfer Service to move the data from the selected on-premises file storage systems to a Cloud Storage bucket.

A.  

Use the gcloud container clusters create command with the options--enable-multi-networking and--enable- autoscaling to create an autoscaling zonal cluster and deploy the application to it.

B.  

Use the gcloud container clusters create-auto command to create an autopilot cluster and deploy the application to it.

C.  

Use the gcloud container clusters update command with the option—region us-centrall to update the cluster and deploy the application to it.

D.  

Use the gcloud container clusters update command with the option—node-locations us-centrall-a,us-centrall-b to update the cluster and deploy the application to the nodes.

A.  

Expose the application by using an internal passthrough Network Load Balancer.

B.  

Expose the application by using an external passthrough Network Load Balancer.

C.  

Expose the application by using a global external proxy Network Load Balancer.

D.  

Expose the application by using a regional external proxy Network Load Balancer.

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.  

Sync Identities with Cloud Directory Sync, and then enable SAML for single sign-on

B.  

Sync Identities in the Google Admin console, and then enable Oauth for single sign-on

C.  

Sync identities with 3rd party LDAP sync, and then copy passwords to allow simplified login with (he same credentials

D.  

Sync identities with Cloud Directory Sync, and then copy passwords to allow simplified login with the same credentials.

A.  

Migrate the users to Active Directory. Connect the Human Resources system to Active Directory. Turn on Google Cloud Directory Sync (GCDS) for Cloud Identity. Turn on Identity Federation from Cloud Identity to Active Directory.

B.  

Organize the users in Cloud Identity into groups. Enforce multi-factor authentication in Cloud Identity.

C.  

Turn on identity federation between Cloud Identity and Google Workspace. Enforce multi-factor authentication for domain wide delegation.

D.  

Use a third-party identity provider service through federation. Synchronize the users from Google Workplace to the third-party provider in real time.

A.  

Search errors in Cloud Audit Logs to analyze the issue.

B.  

Configure Cloud Trace to analyze the issue.

C.  

View errors in Cloud Monitoring to analyze the issue.

D.  

Use the information schema views to analyze the underlying issue.

E.  

Use BigQuery Bl Engine to analyze the issue.

A.  

Create a retention policy on the storage bucket of 30 days, and lock the bucket by using a retention policy lock.

B.  

Enable object versioning on the storage bucket and add lifecycle rules to expire non-current versions after 30 days

C.  

Create an object lifecycle on the storage bucket to change the storage class to Archive Storage for objects with an age over 30 days.

D.  

Create a cron job in Cloud Scheduler to call a Cloud Functions instance every day to delete files older than 30 days.

A.  

Migrate your data to AlloyDB.

B.  

Migrate your data to Spanner.

C.  

Migrate your data to Firebase.

D.  

Migrate your data to Bigtable.

A.  

Create an instance template that contains valid syntax which will be used by the instance group. Delete any persistent disks with the same name as instance names.

B.  

Create an instance template that contains valid syntax that will be used by the instance group. Verify that the instance name and persistent disk name values are not the same in the template.

C.  

Verify that the instance template being used by the instance group contains valid syntax. Delete any persistent disks with the same name as instance names. Set the disks.autoDelete property to true in the instance template.

D.  

Delete the current instance template and replace it with a new instance template. Verify that the instance name and persistent disk name values are not the same in the template. Set the disks.autoDelete property to true in the instance template.

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.  

1. Create an IAM entry for each data scientist's user account.2. Assign the BigQuery jobUser role to the group.

B.  

1. Create an IAM entry for each data scientist's user account.2. Assign the BigQuery dataViewer user role to the group.

C.  

1. Create a dedicated Google group in Cloud Identity.2. Add each data scientist's user account to the group.3. Assign the BigQuery jobUser role to the group.

D.  

1. Create a dedicated Google group in Cloud Identity.2. Add each data scientist's user account to the group.3. Assign the BigQuery dataViewer user role to the group.

A.  

Use Shared VPC to connect all projects, and link Stackdriver to one of the projects.

B.  

For each project, create a Stackdriver account. In each project, create a service account for that project and grant it the role of Stackdriver Account Editor in all other projects.

C.  

Configure a single Stackdriver account, and link all projects to the same account.

D.  

Configure a single Stackdriver account for one of the projects. In Stackdriver, create a Group and add the other project names as criteria for that Group.

A.  

In the Log Viewer, filter the logs on severity 'Error' and the name of the Service Account.

B.  

Create a sink to BigQuery to export all the logs. Create a Data Studio dashboard on the exported logs.

C.  

Create a custom log-based metric for the specific error to be used in an Alerting Policy.

D.  

Grant Project Owner access to the Service Account.

A.  

kubectl delete deployment nginx

B.  

kubectl delete –deployment=nginx

C.  

kubectl delete pod nginx-84748895c4-k6bzl –no-restart 2

D.  

kubectl delete inginx

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.  

Use gcloud container clusters upgrade. Deploy the new services.

B.  

Create a new Node Pool and specify machine type n2–highmem–16. Deploy the new pods.

C.  

Create a new cluster with n2–highmem–16 nodes. Redeploy the pods and delete the old cluster.

D.  

Create a new cluster with both n1–standard–2 and n2–highmem–16 nodes. Redeploy the pods and delete the old cluster.

A.  

Create an export to the sink that saves logs from Cloud Audit to BigQuery.

B.  

Create an export to the sink that saves logs from Cloud Audit to a Coldline Storage bucket.

C.  

Write a custom script that uses logging API to copy the logs from Stackdriver logs to BigQuery.

D.  

Export these logs to Cloud Pub/Sub and write a Cloud Dataflow pipeline to store logs to Cloud SQL.

A.  

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

B.  

Configure the acquired company's billing account and your company's billing account to export the billing data into the same BigQuery dataset.

C.  

Migrate the acquired company’s projects into your company’s GCP organization. Link the migrated 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.

A.  

Use gcloud config configurations describe to review the output.

B.  

Use gcloud config configurations activate and gcloud config list to review the output.

C.  

Use kubectl config get-contexts to review the output.

D.  

Use kubectl config use-context and kubectl config view to review the output.

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.  

Configure the instance to use persistent disk asynchronous replication.

B.  

Configure daily scheduled persistent disk snapshots with a retention period of 7 days.

C.  

Configure Cloud Scheduler to trigger a Cloud Function each day that creates a new machine image and deletes machine images that are older than 7 days.

D.  

Configure a bash script using gsutil to run daily through a cron job. Copy the disk's files to a Cloud Storage bucket with archive storage class and an object lifecycle rule to delete the objects after 7 days.

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.  

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.  

Use gcloud to create the new project, and then deploy your application to the new project.

B.  

Use gcloud to create the new project and to copy the deployed application to the new project.

C.  

Create a Deployment Manager configuration file that copies the current App Engine deployment into a new project.

D.  

Deploy your application again using gcloud and specify the project parameter with the new project name to create the new project.

A.  

Create a health check on port 443 and use that when creating the Managed Instance Group.

B.  

Select Multi-Zone instead of Single-Zone when creating the Managed Instance Group.

C.  

In the Instance Template, add the label ‘health-check’.

D.  

In the Instance Template, add a startup script that sends a heartbeat to the metadata server.

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.  

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

B.  

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

C.  

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

D.  

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

A.  

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

B.  

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

C.  

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

D.  

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

A.  

Create a multi-region Cloud Spanner instance with an optimized schema.

B.  

Create a multi-region Firestore database with aggregation query enabled.

C.  

Create a multi-region Cloud SQL for PostgreSQL database with optimized indexes.

D.  

Create a multi-region BigQuery dataset with optimized tables.

A.  

Use Bigtable.

B.  

Use BigQuery.

C.  

Use Spanner.

D.  

Use Cloud SQL for PostgreSQL.

A.  

Run gcloud configurations list followed by gcloud configurations activate .

B.  

Run gcloud config list followed by gcloud config activate.

C.  

Run gcloud config configurations list followed by gcloud config configurations activate.

D.  

Re-authenticate with the gcloud auth login command and select the correct configurations on login.

A.  

Set up a policy that uses Nearline storage for 30 days and then moves to Archive storage for three years.

B.  

Set up a policy that uses Standard storage for 30 days and then moves to Archive storage for three years.

C.  

Set up a policy that uses Nearline storage for 30 days, then moves the Coldline for one year, and then moves to Archive storage for two years.

D.  

Set up a policy that uses Standard storage for 30 days, then moves to Coldline for one year, and then moves to Archive storage for two years.

A.  

Confirm that network firewall rules are not blocking traffic for User

A.  

B.  

Review recent configuration changes that may have caused unintended modifications to permissions.

C.  

Verify that User A has the Identity and Access Management (IAM) Project Owner role assigned.

D.  

Review the error message that User A received.

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.  

HTTPS Load Balancer

B.  

Network Load Balancer

C.  

SSL Proxy Load Balancer

D.  

Internal TCP/UDP Load Balancer. Add a firewall rule allowing ingress traffic from 0.0.0.0/0 on the target instances.

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.  

Use the command gcloud auth login and point it to the private key

B.  

Use the command gcloud auth activate-service-account and point it to the private key

C.  

Place the private key file in the installation directory of the Cloud SDK and rename it to "credentials ison"

D.  

Place the private key file in your home directory and rename it to ‘’GOOGLE_APPUCATION_CREDENTiALS".

A.  

1. Verify that you are assigned the Project Owners IAM role for this project.2. Locate the project in the GCP console, click Shut down and then enter the project ID.

B.  

1. Verify that you are assigned the Project Owners IAM role for this project.2. Switch to the project in the GCP console, locate the resources and delete them.

C.  

1. Verify that you are assigned the Organizational Administrator IAM role for this project.2. Locate the project in the GCP console, enter the project ID and then click Shut down.

D.  

1. Verify that you are assigned the Organizational Administrators IAM role for this project.2. Switch to the project in the GCP console, locate the resources and delete them.

A.  

Upload the data to BigQuery using the bq command line tool.

B.  

Upload the data to Cloud Storage using the gsutil command line tool.

C.  

Upload the data into Cloud SQL using the import function in the console.

D.  

Upload the data into Cloud Spanner using the import function in the console.

A.  

1. Verify that you ace assigned the Billing Administrator IAM role tor your organization's Google Cloud Project for the Marketing department2. Link the new project to a Marketing Billing Account

B.  

1. Verify that you are assigned the Billing Administrator IAM role for your organization's Google Cloud account2. Create a new Google Cloud Project for the Marketing department3. Set the default key-value project labels to department marketing for all services in this project

C.  

1. Verify that you are assigned the Organization Administrator IAM role for your organization's Google Cloud account2. Create a new Google Cloud Project for the Marketing department 3. Link the new project to a Marketing Billing Account.

D.  

1. Verity that you are assigned the Organization Administrator IAM role for your organization's Google Cloud account2. Create a new Google Cloud Project for the Marketing department3. Set the default key value project labels to department marketing for all services in this protect

A.  

1. Create a consumer Gmail account.2.Write a script that monitors the CPU usage.3.When the CPU usage exceeds the threshold, have that script send an email using the Gmail account and smtp.gmail.com on port 25 as SMTP server.

B.  

1. Create a Stackdriver Workspace, and associate your Google Cloud Platform (GCP) project with it.2.Create an Alerting Policy in Stackdriver that uses the threshold as a trigger condition.3.Configure your email address in the notification channel.

C.  

1. Create a Stackdriver Workspace, and associate your GCP project with it.2.Write a script that monitors the CPU usage and sends it as a custom metric to Stackdriver.3.Create an uptime check for the instance in Stackdriver.

D.  

1. In Stackdriver Logging, create a logs-based metric to extract the CPU usage by using this regular expression: CPU Usage: ([0-9] {1,3}) %2.In Stackdriver Monitoring, create an Alerting Policy based on this metric.3.Configure your email address in the notification channel.

A.  

Create a cluster with a single node-pool by using standard VMs. Label the fault-tolerant Deployments as spot-true.

B.  

Create a cluster with a single node-pool by using Spot VMs. Label the critical Deployments as spot-false.

C.  

Create a cluster with both a Spot W node pool and a rode pool by using standard VMs Deploy the critical.deployments on the Spot VM node pool and the fault; tolerant deployments on the node pool by using standard VMs.

D.  

Create a cluster with both a Spot VM node pool and by using standard VMs. Deploy the critical deployments on the mode pool by using standard VMs and the fault-tolerant deployments on the Spot VM node pool.

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.  

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 gcloud iam roles copy and specify the production project as the destination project.

B.  

Use gcloud iam roles copy and specify your organization as the destination organization.

C.  

In the Google Cloud Platform Console, use the ‘create role from role’ functionality.

D.  

In the Google Cloud Platform Console, use the ‘create role’ functionality and select all applicable permissions.

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.  

An internal HTTP(S) load balancer together with Identity-Aware Proxy to allow only HTTPS traffic.

B.  

An external HTTP(S) load balancer to distribute the load and a URL map to target the requests for the static content to the Cloud Storage backend. Install the HTTPS certificates on the instance.

C.  

An external HTTP(S) load balancer with a managed SSL certificate to distribute the load and a URL map to target the requests for the static content to the Cloud Storage backend.

D.  

An external network load balancer pointing to the backend instances to distribute the load evenly. The web servers will forward the request to the Cloud Storage as needed.

A.  

Create a Cloud Scheduler task to regularly scan your projects and delete mismatched users.

B.  

Create a Cloud Scheduler task to regularly scan your resources and delete mismatched users.

C.  

Set an organizational policy constraint to limit identities by domain to automatically remove mismatched users.

D.  

Set an organizational policy constraint to limit identities by domain, and then retroactively remove the existing mismatched users.

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

A.  

Use a Shielded VM.

B.  

Use a Preemptible VM.

C.  

Use a sole-tenant node.

D.  

Enable deletion protection on the instance.

A.  

Enable retention policies on the bucket, and use Cloud Scheduler to invoke a Cloud Function to move or delete your documents based on their metadata.

B.  

Enable retention policies on the bucket, use lifecycle rules to change the storage classes of the objects, set the number of versions, and delete old files.

C.  

Enable object versioning on the bucket, and use Cloud Scheduler to invoke a Cloud Functions instance to move or delete your documents based on their metadata.

D.  

Enable object versioning on the bucket, use lifecycle conditions to change the storage class of the objects, set the number of versions, and delete old files.

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.  

Configure the gcloud CLI with Application Default Credentials using your user account. Issue a relevant BigGuery request through the gcloud CLI to test the access.

B.  

Grant the service account the BlgQuery Administrator 1AM role to ensure the service account has all required access.

C.  

Generate a service account key, and configure the gcloud CLI to use this key. Issue a relevant BlgQuery request through the gcloud CLI to test the access.

D.  

Configure the gcloud CLI to use service account impersonation. Issue a relevant BigQuery request through the gcloud CLI to test the access.

A.  

Configure username and password by using gcloud configure set proxy/username and gcloud configure set proxy/ proxy/password commands.

B.  

Encode username and password in sha256 encoding, and save it to a text file. Use filename as a value in the gcloud configure set core/custom_ca_certs_file command.

C.  

Provide values for CLOUDSDK_USERNAME and CLOUDSDK_PASSWORD in the gcloud CLI tool configure file.

D.  

Set the CLOUDSDK_PROXY_USERNAME and CLOUDSDK_PROXY PASSWORD properties by using environment variables in your command line tool.

A.  

Use Cloud Logging filters to create log-based metrics for firewall and instance actions. Monitor the changes and set up reasonable alerts.

B.  

Install Kibana on a compute Instance. Create a log sink to forward Cloud Audit Logs filtered for firewalls andcompute instances to Pub/Sub. Target the Pub/Sub topic to push messages to the Kibana instance. Analyze the logs on Kibana in real time.

C.  

Turn on Google Cloud firewall rules logging, and set up alerts for any insert, update, or delete events.

D.  

Create a log sink to forward Cloud Audit Logs filtered for firewalls and compute instances to Cloud Storage.Use BigQuery to periodically analyze log events in the storage bucket.

A.  

Configure an HTTP(S) load balancer.

B.  

Configure an internal TCP load balancer.

C.  

Configure an external SSL proxy load balancer.

D.  

Configure an external TCP proxy load balancer.

A.  

Grant "project owner" for web-applications appropriate roles to crm-databases.

B.  

Grant "project owner" role to crm-databases and the web-applications project.

C.  

Grant "project owner" role to crm-databases and roles/bigquery.dataViewer role to web-applications.

D.  

Grant roles/bigquery.dataViewer role to crm-databases and appropriate roles to web-applications.

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.  

Cloud SQL

B.  

Cloud Spanner

C.  

Cloud Firestore

D.  

Cloud Datastore

A.  

Option A

B.  

Option B

C.  

Option C

D.  

Option D

A.  

Enable Cloud IAP for the Compute Engine instances, and add the operations partner as a Cloud IAP Tunnel User.

B.  

Tag all the instances with the same network tag. Create a firewall rule in the VPC to grant TCP access on port 22 for traffic from the operations partner to instances with the network tag.

C.  

Set up Cloud VPN between your Google Cloud VPC and the internal network of the operations partner.

D.  

Ask the operations partner to generate SSH key pairs, and add the public keys to the VM instances.

A.  

Ask the other team to grant your default App Engine Service account the role of BigQuery Job User.

B.  

Ask the other team to grant your default App Engine Service account the role of BigQuery Data Viewer.

C.  

In Cloud IAM of your project, ensure that the default App Engine service account has the role of BigQuery Data Viewer.

D.  

In Cloud IAM of your project, grant a newly created service account from the other team the role of BigQuery Job User in your project.

A.  

Grant each individual external consultant the role of BigQuery Editor

B.  

Grant each individual external consultant the role of BigQuery Viewer

C.  

Create a Google Group that contains the consultants and grant the group the role of BigQuery Editor

D.  

Create a Google Group that contains the consultants, and grant the group the role of BigQuery Viewer

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.  

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.  

• Navigate to Cloud Mentioning in the Google Cloud console, and create a custom monitoring job for theBigtable instance to track all changes.• Create an alert by using webhook endpoints. with the SIEM endpoint as a receiver

B.  

• Navigate to the Audit Logs page in the Google Cloud console, and enable Data Read. Data Write and Admin Read logs for the Bigtable instance• Create a Pub/Sub topic as a Cloud Logging sink destination, and add your SIEM as a subscriber to the topic.

C.  

• Install the Ops Agent on the Bigtable instance during configuration. K• Create a service account with read permissions for the Bigtable instance.• Create a custom Dataflow job with this service account to export logs to the company's SIEM system.

D.  

• Navigate to the Audit Logs page in the Google Cloud console, and enable Admin Write logs for theBiglable instance.• Create a Cloud Functions instance to export logs from Cloud Logging to your SIEM.

A.  

In the console, validate which SSH keys have been stored as project-wide keys.

B.  

Navigate to Identity-Aware Proxy and check the permissions for these resources.

C.  

Enable Audit Logs on the IAM & admin page for all resources, and validate the results.

D.  

Use the command gcloud projects get–iam–policy to view the current role assignments.

A.  

Update your web application to use the protocol HTTP/2 instead of HTTP/1.1

B.  

Set the concurrency number to 1 for your Cloud Run service.

C.  

Set the maximum number of instances for your Cloud Run service to 100.

D.  

Set the minimum number of instances for your Cloud Run service to 3.

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.  

Arrange to switch to Flat-Rate pricing for this query, then move back to on-demand.

B.  

Use the command line to run a dry run query to estimate the number of bytes read. Then convert that bytes estimate to dollars using the Pricing Calculator.

C.  

Use the command line to run a dry run query to estimate the number of bytes returned. Then convert that bytes estimate to dollars using the Pricing Calculator.

D.  

Run a select count (*) to get an idea of how many records your query will look through. Then convert that number of rows to dollars using the Pricing Calculator.

A.  

Use a custom script to push your application logs to Cloud SQL for exploration.

B.  

Ingest your application logs to Cloud Logging by using Ops Agent, and explore your logs in Logs Explorer.

C.  

Ingest your application logs to Cloud Logging by using Ops Agent, and explore your logs with Log Analytics.

D.  

Use a custom script to push your application logs to BigQuery for exploration.

A.  

Create a file in Cloud Storage per device and append new data to that file.

B.  

Create a file in Cloud Filestore per device and append new data to that file.

C.  

Ingest the data into Datastore. Store data in an entity group based on the device.

D.  

Ingest the data into Cloud Bigtable. Create a row key based on the event timestamp.

A.  

Create and deploy a Custom Resource Definition per microservice.

B.  

Create and deploy a Docker Compose File.

C.  

Create and deploy a Job per microservice.

D.  

Create and deploy a Deployment per microservice.

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.  

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.  

Add the auditors group to the ‘logging.viewer’ and ‘bigQuery.dataViewer’ predefined IAM roles.

B.  

Add the auditors group to two new custom IAM roles.

C.  

Add the auditor user accounts to the ‘logging.viewer’ and ‘bigQuery.dataViewer’ predefined IAM roles.

D.  

Add the auditor user accounts to two new custom IAM roles.

A.  

Enable node auto-provisioning on the GKE cluster.

B.  

Create a VerticalPodAutscaler for those workloads.

C.  

Create a node pool with preemptible VMs and GPUs attached to those VMs.

D.  

Create a node pool of instances with GPUs, and enable autoscaling on this node pool with a minimum size of 1.

A.  

Create a VPC with non-overlapping CIDR ranges compared to your on-premises network. When migrating individual workloads, assign each workload a new static internal IP address.

B.  

Migrate your DNS server first. Configure Cloud DNS with a forwarding zone to your migrated DNS server. Then migrate all other workloads with ephemeral internal IP addresses.

C.  

Migrate all workloads to a single VPC subnet. Configure Cloud NAT for the subnet and manually assign a static IP address to the Cloud NAT gateway.

D.  

Create a VPC with the same CIDR ranges as your on-premises network. When migrating individual workloads, assign each workload the same static internal IP address.

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.  

Deploy a Cloud SQL database with the SSL mode set to encrypted only, configure SSL/TLS client certificates, and configure a database user and password.

B.  

Deploy a Cloud SOL database and configure IAM database authentication. Access the database through the Cloud SQL Auth Proxy.

C.  

Deploy a Cloud SQL database with the SSL mode set to encrypted only, configure SSL/TLS client certificates, and configure IAM database authentication.

D.  

Deploy a Cloud SQL database and configure a database user and password. Access the database through the Cloud SQL Auth Proxy.

A.  

Use the BigQuery interface to review the nightly Job and look for any errors

B.  

Review the Error Reporting page in the Cloud Console to find any errors.

C.  

In Cloud Logging create a filter for your Data Studio report

D.  

Use the open source CLI tool. Snapshot Debugger, to find out why the data was not refreshed correctly.

A.  

Create the GKE cluster and deploy the application. Request a security exception to create a Google service account key. Set the constraints/iam.serviceAccountKeyExpiryHours organization policy to 8 hours.

B.  

Create the GKE cluster and deploy the application. Request a security exception to create a Google service account key. Set the constraints/iam.serviceAccountKeyExpiryHours organization policy to 24 hours.

C.  

Create the GKE cluster with Workload Identity Federation. Configure the default node service account to access the bucket. Deploy the application into the cluster so the application can use the node service account permissions. Use Identity and Access Management (IAM) to grant the service account access to the bucket.

D.  

Create the GKE cluster with Workload Identity Federation. Create a Google service account and a Kubernetes ServiceAccount, and configure both service accounts to use Workload Identity Federation. Attach the Kubernetes ServiceAccount to the application Pods and configure the Google service account to access the bucket with Identity and Access Management (IAM).