You are performing a semiannual capacity planning exercise for your flagship service. You expect a service user growth rate of 10% month-over-month over the next six months. Your service is fully containerized and runs on Google Cloud Platform (GCP). using a Google Kubernetes Engine (GKE) Standard regional cluster on three zones with cluster autoscaler enabled. You currently consume about 30% of your total deployed CPU capacity, and you require resilience against the failure of a zone. You want to ensure that your users experience minimal negative impact as a result of this growth or as a result of zone failure, while avoiding unnecessary costs. How should you prepare to handle the predicted growth?

Verity the maximum node pool size, enable a horizontal pod autoscaler, and then perform a load test to verity your expected resource needs.

Because you are deployed on GKE and are using a cluster autoscaler. your GKE cluster will scale automatically, regardless of growth rate.

Because you are at only 30% utilization, you have significant headroom and you won't need to add any additional capacity for this rate of growth.

Proactively add 60% more node capacity to account for six months of 10% growth rate, and then perform a load test to make sure you have enough capacity.

You are managing an application that exposes an HTTP endpoint without using a load balancer. The latency of the HTTP responses is important for the user experience. You want to understand what HTTP latencies all of your users are experiencing. You use Stackdriver Monitoring. What should you do?

* In your application, create a metric with a metricKind set to gauge and a valueType set to distribution. * In Stackdriver's Metrics Explorer, use a Heatmap graph to visualize the metric.

* In your application, create a metric with a metricKind set to DELTA and a valueType set to DOUBLE. * In Stackdriver's Metrics Explorer, use a Slacked Bar graph to visualize the metric.

* In your application, create a metric with a metricKind set to CUMULATIVE and a valueType set to DOUBLE. * In Stackdriver's Metrics Explorer, use a Line graph to visualize the metric.

* In your application, create a metric with a metricKind set to gauge and a valueType set to distribution. * In Stackdriver's Metrics Explorer, use a Heatmap graph to visualize the metric.

* In your application, create a metric with a metricKind. set toMETRlc_KIND_UNSPECIFIEDanda valueType set to INT64. * In Stackdriver's Metrics Explorer, use a Stacked Area graph to visualize the metric.

You are responsible for creating and modifying the Terraform templates that define your Infrastructure. Because two new engineers will also be working on the same code, you need to define a process and adopt a tool that will prevent you from overwriting each other's code. You also want to ensure that you capture all updates in the latest version. What should you do?

* Store your code in a Git-based version control system. * Establish a process that includes code reviews by peers and unit testing to ensure integrity and functionality before integration of code. * Establish a process where the fully integrated code in the repository becomes the latest master version.

* Store your code in a Git-based version control system. * Establish a process that allows developers to merge their own changes at the end of each day. * Package and upload code lo a versioned Cloud Storage bucket as the latest master version.

* Store your code in a Git-based version control system. * Establish a process that includes code reviews by peers and unit testing to ensure integrity and functionality before integration of code. * Establish a process where the fully integrated code in the repository becomes the latest master version.

* Store your code as text files in Google Drive in a defined folder structure that organizes the files. * At the end of each day. confirm that all changes have been captured in the files within the folder structure. * Rename the folder structure with a predefined naming convention that increments the version.

* Store your code as text files in Google Drive in a defined folder structure that organizes the files. * At the end of each day, confirm that all changes have been captured in the files within the folder structure and create a new .zip archive with a predefined naming convention. * Upload the .zip archive to a versioned Cloud Storage bucket and accept it as the latest version.

You are running an experiment to see whether your users like a new feature of a web application. Shortly after deploying the feature as a canary release, you receive a spike in the number of 500 errors sent to users, and your monitoring reports show increased latency. You want to quickly minimize the negative impact on users. What should you do first?

Roll back the experimental canary release.

Start monitoring latency, traffic, errors, and saturation.

Record data for the postmortem document of the incident.

Trace the origin of 500 errors and the root cause of increased latency.

You need to run a business-critical workload on a fixed set of Compute Engine instances for several months. The workload is stable with the exact amount of resources allocated to it. You want to lower the costs for this workload without any performance implications. What should you do?

Purchase Committed Use Discounts.

Migrate the instances to a Managed Instance Group.

Convert the instances to preemptible virtual machines.

Create an Unmanaged Instance Group for the instances used to run the workload.

You encountered a major service outage that affected all users of the service for multiple hours. After several hours of incident management, the service returned to normal, and user access was restored. You need to provide an incident summary to relevant stakeholders following the Site Reliability Engineering recommended practices. What should you do first?

Develop a post-mortem to be distributed to stakeholders.

Call individual stakeholders lo explain what happened.

Develop a post-mortem to be distributed to stakeholders.

Send the Incident State Document to all the stakeholders.

Require the engineer responsible to write an apology email to all stakeholders.

Your company follows Site Reliability Engineering practices. You are the person in charge of Communications for a large, ongoing incident affecting your customer-facing applications. There is still no estimated time for a resolution of the outage. You are receiving emails from internal stakeholders who want updates on the outage, as well as emails from customers who want to know what is happening. You want to efficiently provide updates to everyone affected by the outage. What should you do?

Provide periodic updates to all stakeholders in a timely manner. Commit to a 'next update' time in all communications.

Focus on responding to internal stakeholders at least every 30 minutes. Commit to 'next update' times.

Provide periodic updates to all stakeholders in a timely manner. Commit to a 'next update' time in all communications.

Delegate the responding to internal stakeholder emails to another member of the Incident Response Team. Focus on providing responses directly to customers.

Provide all internal stakeholder emails to the Incident Commander, and allow them to manage internal communications. Focus on providing responses directly to customers.

Your team is designing a new application for deployment into Google Kubernetes Engine (GKE). You need to set up monitoring to collect and aggregate various application-level metrics in a centralized location. You want to use Google Cloud Platform services while minimizing the amount of work required to set up monitoring. What should you do?

Publish various metrics from the application directly to the Slackdriver Monitoring API, and then observe these custom metrics in Stackdriver.

Install the Cloud Pub/Sub client libraries, push various metrics from the application to various topics, and then observe the aggregated metrics in Stackdriver.

Install the OpenTelemetry client libraries in the application, configure Stackdriver as the export destination for the metrics, and then observe the application's metrics in Stackdriver.

Emit all metrics in the form of application-specific log messages, pass these messages from the containers to the Stackdriver logging collector, and then observe metrics in Stackdriver.

Your application services run in Google Kubernetes Engine (GKE). You want to make sure that only images from your centrally-managed Google Container Registry (GCR) image registry in the altostrat-images project can be deployed to the cluster while minimizing development time. What should you do?

Use a Binary Authorization policy that includes the whitelist name pattern gcr.io/attostrat-images/.

Create a custom builder for Cloud Build that will only push images to gcr.io/altostrat-images.

Use a Binary Authorization policy that includes the whitelist name pattern gcr.io/attostrat-images/.

Add logic to the deployment pipeline to check that all manifests contain only images from gcr.io/altostrat-images.

Add a tag to each image in gcr.io/altostrat-images and check that this tag is present when the image is deployed.

You are running an application in a virtual machine (VM) using a custom Debian image. The image has the Stackdriver Logging agent installed. The VM has the cloud-platform scope. The application is logging information via syslog. You want to use Stackdriver Logging in the Google Cloud Platform Console to visualize the logs. You notice that syslog is not showing up in the 'All logs' dropdown list of the Logs Viewer. What is the first thing you should do?

SSH to the VM and execute the following commands on your VM: ps ax I grep fluentd

Look for the agent's test log entry in the Logs Viewer.

Install the most recent version of the Stackdriver agent.

Verify the VM service account access scope includes the monitoring.write scope.

SSH to the VM and execute the following commands on your VM: ps ax I grep fluentd

Your organization wants to implement Site Reliability Engineering (SRE) culture and principles. Recently, a service that you support had a limited outage. A manager on another team asks you to provide a formal explanation of what happened so they can action remediations. What should you do?

Develop a postmortem that includes the root causes, resolution, lessons learned, and a prioritized list of action items. Share it on the engineering organization's document portal.

Develop a postmortem that includes the root causes, resolution, lessons learned, and a prioritized list of action items. Share it with the manager only.

Develop a postmortem that includes the root causes, resolution, lessons learned, and a prioritized list of action items. Share it on the engineering organization's document portal.

Develop a postmortem that includes the root causes, resolution, lessons learned, the list of people responsible, and a list of action items for each person. Share it with the manager only.

Develop a postmortem that includes the root causes, resolution, lessons learned, the list of people responsible, and a list of action items for each person. Share it on the engineering organization's document portal.

You have a set of applications running on a Google Kubernetes Engine (GKE) cluster, and you are using Stackdriver Kubernetes Engine Monitoring. You are bringing a new containerized application required by your company into production. This application is written by a third party and cannot be modified or reconfigured. The application writes its log information to /var/log/app_messages.log, and you want to send these log entries to Stackdriver Logging. What should you do?

Deploy a Fluentd daemonset to GKE. Then create a customized input and output configuration to tail the log file in the application's pods and write to Slackdriver Logging.

Use the default Stackdriver Kubernetes Engine Monitoring agent configuration.

Deploy a Fluentd daemonset to GKE. Then create a customized input and output configuration to tail the log file in the application's pods and write to Slackdriver Logging.

Install Kubernetes on Google Compute Engine (GCE> and redeploy your applications. Then customize the built-in Stackdriver Logging configuration to tail the log file in the application's pods and write to Stackdriver Logging.

Write a script to tail the log file within the pod and write entries to standard output. Run the script as a sidecar container with the application's pod. Configure a shared volume between the containers to allow the script to have read access to /var/log in the application container.

You are running a real-time gaming application on Compute Engine that has a production and testing environment. Each environment has their own Virtual Private Cloud (VPC) network. The application frontend and backend servers are located on different subnets in the environment's VPC. You suspect there is a malicious process communicating intermittently in your production frontend servers. You want to ensure that network traffic is captured for analysis. What should you do?

Enable VPC Flow Logs on the testing and production VPC network frontend and backend subnets with a volume scale of 1.0. Apply changes in testing before production.

Enable VPC Flow Logs on the production VPC network frontend and backend subnets only with a sample volume scale of 0.5.

Enable VPC Flow Logs on the production VPC network frontend and backend subnets only with a sample volume scale of 1.0.

Enable VPC Flow Logs on the testing and production VPC network frontend and backend subnets with a volume scale of 0.5. Apply changes in testing before production.

Enable VPC Flow Logs on the testing and production VPC network frontend and backend subnets with a volume scale of 1.0. Apply changes in testing before production.

You support a high-traffic web application and want to ensure that the home page loads in a timely manner. As a first step, you decide to implement a Service Level Indicator (SLI) to represent home page request latency with an acceptable page load time set to 100 ms. What is the Google-recommended way of calculating this SLI?

Count the number of home page requests that load in under 100 ms, and then divide by the total number of home page requests.

Buckelize Ihe request latencies into ranges, and then compute the percentile at 100 ms.

Bucketize the request latencies into ranges, and then compute the median and 90th percentiles.

Count the number of home page requests that load in under 100 ms, and then divide by the total number of home page requests.

Count the number of home page requests that load in under 100 ms. and then divide by the total number of all web application requests.

You use a multiple step Cloud Build pipeline to build and deploy your application to Google Kubernetes Engine (GKE). You want to integrate with a third-party monitoring platform by performing a HTTP POST of the build information to a webhook. You want to minimize the development effort. What should you do?

Create a Cloud Pub/Sub push subscription to the Cloud Build cloud-builds PubSub topic to HTTP POST the build information to a webhook.

Add logic to each Cloud Build step to HTTP POST the build information to a webhook.

Add a new step at the end of the pipeline in Cloud Build to HTTP POST the build information to a webhook.

Use Stackdriver Logging to create a logs-based metric from the Cloud Buitd logs. Create an Alert with a Webhook notification type.

Create a Cloud Pub/Sub push subscription to the Cloud Build cloud-builds PubSub topic to HTTP POST the build information to a webhook.

You created a Stackdriver chart for CPU utilization in a dashboard within your workspace project. You want to share the chart with your Site Reliability Engineering (SRE) team only. You want to ensure you follow the principle of least privilege. What should you do?

Click 'Share chart by URL' and provide the URL to the SRE team. Assign the SRE team the Monitoring Viewer IAM role in the workspace project.

Share the workspace Project ID with the SRE team. Assign the SRE team the Monitoring Viewer IAM role in the workspace project.

Share the workspace Project ID with the SRE team. Assign the SRE team the Dashboard Viewer IAM role in the workspace project.

Click 'Share chart by URL' and provide the URL to the SRE team. Assign the SRE team the Monitoring Viewer IAM role in the workspace project.

Click 'Share chart by URL' and provide the URL to the SRE team. Assign the SRE team the Dashboard Viewer IAM role in the workspace project.

You support a stateless web-based API that is deployed on a single Compute Engine instance in the europe-west2-a zone . The Service Level Indicator (SLI) for service availability is below the specified Service Level Objective (SLO). A postmortem has revealed that requests to the API regularly time out. The time outs are due to the API having a high number of requests and running out memory. You want to improve service availability. What should you do?

Set up additional service instances in other zones and load balance the traffic between all instances.

Change the specified SLO to match the measured SLI.

Move the service to higher-specification compute instances with more memory.

Set up additional service instances in other zones and load balance the traffic between all instances.

Set up additional service instances in other zones and use them as a failover in case the primary instance is unavailable.

You deploy a new release of an internal application during a weekend maintenance window when there is minimal user traffic. After the window ends, you learn that one of the new features isn't working as expected in the production environment. After an extended outage, you roll back the new release and deploy a fix. You want to modify your release process to reduce the mean time to recovery so you can avoid extended outages in the future. What should you do?Choose 2 answers

Adopt the blue/green deployment strategy when releasing new code via a CD server.

Configure a CI server. Add a suite of unit tests to your code and have your CI server run them on commit and verify any changes.

Before merging new code, require 2 different peers to review the code changes.

Adopt the blue/green deployment strategy when releasing new code via a CD server.

Integrate a code linting tool to validate coding standards before any code is accepted into the repository.

Require developers to run automated integration tests on their local development environments before release.

Configure a CI server. Add a suite of unit tests to your code and have your CI server run them on commit and verify any changes.

You have a pool of application servers running on Compute Engine. You need to provide a secure solution that requires the least amount of configuration and allows developers to easily access application logs for troubleshooting. How would you implement the solution on GCP?

* Deploy the Stackdriver logging agent to the application servers. * Give the developers the IAM Logs Viewer role to access Stackdriver and view logs.

* Deploy the Stackdriver logging agent to the application servers. * Give the developers the IAM Logs Private Logs Viewer role to access Stackdriver and view logs.

* Deploy the Stackdriver monitoring agent to the application servers. * Give the developers the IAM Monitoring Viewer role to access Stackdriver and view metrics.

* Install the gsutil command line tool on your application servers. * Write a script using gsutil to upload your application log to a Cloud Storage bucket, and then schedule it to run via cron every 5 minutes. * Give the developers IAM Object Viewer access to view the logs in the specified bucket.

You support a Node.js application running on Google Kubernetes Engine (GKE) in production. The application makes several HTTP requests to dependent applications. You want to anticipate which dependent applications might cause performance issues. What should you do?

Instrument all applications with Stackdriver Trace and review inter-service HTTP requests.

Instrument all applications with Stackdriver Profiler.

Instrument all applications with Stackdriver Trace and review inter-service HTTP requests.

Use Stackdriver Debugger to review the execution of logic within each application to instrument all applications.

Modify the Node.js application to log HTTP request and response times to dependent applications. Use Stackdriver Logging to find dependent applications that are performing poorly.

You use Spinnaker to deploy your application and have created a canary deployment stage in the pipeline. Your application has an in-memory cache that loads objects at start time. You want to automate the comparison of the canary version against the production version. How should you configure the canary analysis?

Compare the canary with a new deployment of the current production version.

Compare the canary with a new deployment of the previous production version.

Compare the canary with the existing deployment of the current production version.

Compare the canary with the average performance of a sliding window of previous production versions.

Your team of Infrastructure DevOps Engineers is growing, and you are starting to use Terraform to manage infrastructure. You need a way to implement code versioning and to share code with other team members. What should you do?

Store the Terraform code in a version-control system. Establish procedures for pushing new versions and merging with the master.

Store the Terraform code in a network shared folder with child folders for each version release. Ensure that everyone works on different files.

Store the Terraform code in a Cloud Storage bucket using object versioning. Give access to the bucket to every team member so they can download the files.

Store the Terraform code in a shared Google Drive folder so it syncs automatically to every team member's computer. Organize files with a naming convention that identifies each new version.

You are using Stackdriver to monitor applications hosted on Google Cloud Platform (GCP). You recently deployed a new application, but its logs are not appearing on the Stackdriver dashboard.You need to troubleshoot the issue. What should you do?

Confirm that the Stackdriver agent has been installed in the hosting virtual machine.

Confirm that your account has the proper permissions to use the Stackdriver dashboard.

Confirm that port 25 has been opened in the firewall to allow messages through to Stackdriver.

Confirm that the application is using the required client library and the service account key has proper permissions.

Your organization recently adopted a container-based workflow for application development. Your team develops numerous applications that are deployed continuously through an automated build pipeline to the production environment. A recent security audit alerted your team that the code pushed to production could contain vulnerabilities and that the existing tooling around virtual machine (VM) vulnerabilities no longer applies to the containerized environment. You need to ensure the security and patch level of all code running through the pipeline. What should you do?

Implement static code analysis tooling against the Docker files used to create the containers.

Set up Container Analysis to scan and report Common Vulnerabilities and Exposures.

Configure the containers in the build pipeline to always update themselves before release.

Reconfigure the existing operating system vulnerability software to exist inside the container.

Implement static code analysis tooling against the Docker files used to create the containers.

You use Cloud Build to build your application. You want to reduce the build time while minimizing cost and development effort. What should you do?

Use multiple smaller build steps to minimize execution time.

Use Cloud Storage to cache intermediate artifacts.

Run multiple Jenkins agents to parallelize the build.

Use multiple smaller build steps to minimize execution time.

Use larger Cloud Build virtual machines (VMs) by using the machine-type option.

You support a web application that is hosted on Compute Engine. The application provides a booking service for thousands of users. Shortly after the release of a new feature, your monitoring dashboard shows that all users are experiencing latency at login. You want to mitigate the impact of the incident on the users of your service. What should you do first?

Upsize the virtual machines running the login services.

Review the Stackdriver monitoring.

Upsize the virtual machines running the login services.

Deploy a new release to see whether it fixes the problem.

You are deploying an application that needs to access sensitive information. You need to ensure that this information is encrypted and the risk of exposure is minimal if a breach occurs. What should you do?

Store the encryption keys in Cloud Key Management Service (KMS) and rotate the keys frequently

Inject the secret at the time of instance creation via an encrypted configuration management system.

Integrate the application with a Single sign-on (SSO) system and do not expose secrets to the application

Leverage a continuous build pipeline that produces multiple versions of the secret for each instance of the application.

You encounter a large number of outages in the production systems you support. You receive alerts for all the outages that wake you up at night. The alerts are due to unhealthy systems that are automatically restarted within a minute. You want to set up a process that would prevent staff burnout while following Site Reliability Engineering practices. What should you do?

Create an incident report for each of the alerts.

Distribute the alerts to engineers in different time zones.

Redefine the related Service Level Objective so that the error budget is not exhausted.

You have migrated an e-commerce application to Google Cloud Platform (GCP). You want to prepare the application for the upcoming busy season. What should you do first to prepare for the busy season?

Load teat the application to profile its performance for scaling.

Enable AutoScaling on the production clusters, in case there is growth.

Pre-provision double the compute power used last season, expecting growth.

Create a runbook on inflating the disaster recovery (DR) environment if there is growth.

You support a web application that runs on App Engine and uses CloudSQL and Cloud Storage for data storage. After a short spike in website traffic, you notice a big increase in latency for all user requests, increase in CPU use, and the number of processes running the application. Initial troubleshooting reveals:After the initial spike in traffic, load levels returned to normal but users still experience high latency.Requests for content from the CloudSQL database and images from Cloud Storage show the same high latency.No changes were made to the website around the time the latency increased.There is no increase in the number of errors to the users.You expect another spike in website traffic in the coming days and want to make sure users don't experience latency. What should you do?

Modify the App Engine configuration to have additional idle instances.

Upgrade the GCS buckets to Multi-Regional.

Enable high availability on the CloudSQL instances.

Move the application from App Engine to Compute Engine.

Modify the App Engine configuration to have additional idle instances.

Your application runs on Google Cloud Platform (GCP). You need to implement Jenkins for deploying application releases to GCP. You want to streamline the release process, lower operational toil, and keep user data secure. What should you do?

Implement Jenkins on Compute Engine virtual machines.

Implement Jenkins on local workstations.

Implement Jenkins on Kubernetes on-premises

Implement Jenkins on Google Cloud Functions.

Implement Jenkins on Compute Engine virtual machines.

You are working with a government agency that requires you to archive application logs for seven years. You need to configure Stackdriver to export and store the logs while minimizing costs of storage. What should you do?

Create a sink in Stackdriver, name it, create a bucket on Cloud Storage for storing archived logs, and then select the bucket as the log export destination.

Create a Cloud Storage bucket and develop your application to send logs directly to the bucket.

Develop an App Engine application that pulls the logs from Stackdriver and saves them in BigQuery.

Create an export in Stackdriver and configure Cloud Pub/Sub to store logs in permanent storage for seven years.

Create a sink in Stackdriver, name it, create a bucket on Cloud Storage for storing archived logs, and then select the bucket as the log export destination.

You support a trading application written in Python and hosted on App Engine flexible environment. You want to customize the error information being sent to Stackdriver Error Reporting. What should you do?

Use the Stackdriver Error Reporting API to write errors from your application to ReportedErrorEvent, and then generate log entries with properly formatted error messages in Stackdriver Logging.

Install the Stackdriver Error Reporting library for Python, and then run your code on a Compute Engine VM.

Install the Stackdriver Error Reporting library for Python, and then run your code on Google Kubernetes Engine.

Install the Stackdriver Error Reporting library for Python, and then run your code on App Engine flexible environment.

Use the Stackdriver Error Reporting API to write errors from your application to ReportedErrorEvent, and then generate log entries with properly formatted error messages in Stackdriver Logging.

You need to define Service Level Objectives (SLOs) for a high-traffic multi-region web application. Customers expect the application to always be available and have fast response times. Customers are currently happy with the application performance and availability. Based on current measurement, you observe that the 90th percentile of latency is 120ms and the 95th percentile of latency is 275ms over a 28-day window. What latency SLO would you recommend to the team to publish?

90th percentile -- 150ms 95th percentile -- 300ms

90th percentile -- 100ms 95th percentile -- 250ms

90th percentile -- 120ms 95th percentile -- 275ms

90th percentile -- 150ms 95th percentile -- 300ms

90th percentile -- 250ms 95th percentile -- 400ms

You support a large service with a well-defined Service Level Objective (SLO). The development team deploys new releases of the service multiple times a week. If a major incident causes the service to miss its SLO, you want the development team to shift its focus from working on features to improving service reliability. What should you do before a major incident occurs?

Develop an appropriate error budget policy in cooperation with all service stakeholders.

Negotiate with the product team to always prioritize service reliability over releasing new features.

Negotiate with the development team to reduce the release frequency to no more than once a week.

Add a plugin to your Jenkins pipeline that prevents new releases whenever your service is out of SLO.

Your company is developing applications that are deployed on Google Kubernetes Engine (GKE). Each team manages a different application. You need to create the development and production environments for each team, while minimizing costs. Different teams should not be able to access other teams' environments. What should you do?

Create a Development and a Production GKE cluster in separate projects. In each cluster, create a Kubernetes namespace per team, and then configure Kubernetes Role-based access control (RBAC) so that each team can only access its own namespace.

Create one GCP Project per team. In each project, create a cluster for Development and one for Production. Grant the teams IAM access to their respective clusters.

Create one GCP Project per team. In each project, create a cluster with a Kubernetes namespace for Development and one for Production. Grant the teams IAM access to their respective clusters.

Create a Development and a Production GKE cluster in separate projects. In each cluster, create a Kubernetes namespace per team, and then configure Identity Aware Proxy so that each team can only access its own namespace.

Create a Development and a Production GKE cluster in separate projects. In each cluster, create a Kubernetes namespace per team, and then configure Kubernetes Role-based access control (RBAC) so that each team can only access its own namespace.

Some of your production services are running in Google Kubernetes Engine (GKE) in the eu-west-1 region. Your build system runs in the us-west-1 region. You want to push the container images from your build system to a scalable registry to maximize the bandwidth for transferring the images to the cluster. What should you do?

Push the images to Google Container Registry (GCR) using the eu.gcr.io hostname.

Push the images to Google Container Registry (GCR) using the gcr.io hostname.

Push the images to Google Container Registry (GCR) using the us.gcr.io hostname.

Push the images to Google Container Registry (GCR) using the eu.gcr.io hostname.

Push the images to a private image registry running on a Compute Engine instance in the eu-west-1 region.

You manage several production systems that run on Compute Engine in the same Google Cloud Platform (GCP) project. Each system has its own set of dedicated Compute Engine instances. You want to know how must it costs to run each of the systems. What should you do?

Assign all instances a label specific to the system they run. Configure BigQuery billing export and query costs per label.

In the Google Cloud Platform Console, use the Cost Breakdown section to visualize the costs per system.

Assign all instances a label specific to the system they run. Configure BigQuery billing export and query costs per label.

Enrich all instances with metadata specific to the system they run. Configure Stackdriver Logging to export to BigQuery, and query costs based on the metadata.

Name each virtual machine (VM) after the system it runs. Set up a usage report export to a Cloud Storage bucket. Configure the bucket as a source in BigQuery to query costs based on VM name.

You use Cloud Build to build and deploy your application. You want to securely incorporate database credentials and other application secrets into the build pipeline. You also want to minimize the development effort. What should you do?

Use Cloud Key Management Service (Cloud KMS) to encrypt the secrets and include them in your Cloud Build deployment configuration. Grant Cloud Build access to the KeyRing.

Create a Cloud Storage bucket and use the built-in encryption at rest. Store the secrets in the bucket and grant Cloud Build access to the bucket.

Encrypt the secrets and store them in the application repository. Store a decryption key in a separate repository and grant Cloud Build access to the repository.

Use client-side encryption to encrypt the secrets and store them in a Cloud Storage bucket. Store a decryption key in the bucket and grant Cloud Build access to the bucket.

Use Cloud Key Management Service (Cloud KMS) to encrypt the secrets and include them in your Cloud Build deployment configuration. Grant Cloud Build access to the KeyRing.

Google Professional Cloud DevOps Engineer Practice Test 2

You currently store the virtual machine (VM) utilization logs in Stackdriver. You need to provide an easy-to-share interactive VM utilization dashboard that is updated in real time and contains information aggregated on a quarterly basis. You want to use Google Cloud Platform solutions. What should you do?

Become a Premium Member for full access

Unlock Premium Member

Google Professional Cloud DevOps Engineer Practice Test 2

Question

Drag and Drop

Hot Area

Google Professional Cloud DevOps Engineer Practice Tests

Practice Tests