ExamGecko
Login
Ask Question

Google Professional Cloud DevOps Engineer Practice Test - Questions Answers, Page 8

List of questions

Question 71

Report
Export
Collapse

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?

Upgrade the GCS buckets to Multi-Regional.
Upgrade the GCS buckets to Multi-Regional.
Enable high availability on the CloudSQL instances.
Enable high availability on the CloudSQL instances.
Move the application from App Engine to Compute Engine.
Move the application from App Engine to Compute Engine.
Modify the App Engine configuration to have additional idle instances.
Modify the App Engine configuration to have additional idle instances.
Suggested answer: D

Explanation:

Scaling App Engine scales the number of instances automatically in response to processing volume. This scaling factors in the automatic_scaling settings that are provided on a per-version basis in the configuration file. A service with basic scaling is configured by setting the maximum number of instances in the max_instances parameter of the basic_scaling setting. The number of live instances scales with the processing volume. You configure the number of instances of each version in that service's configuration file. The number of instances usually corresponds to the size of a dataset being held in memory or the desired throughput for offline work. You can adjust the number of instances of a manually-scaled version very quickly, without stopping instances that are currently running, using the Modules API set_num_instances function. https://cloud.google.com/appengine/docs/standard/python/how-instances-are-managed

https://cloud.google.com/appengine/docs/standard/python/config/appref

max_idle_instances Optional. The maximum number of idle instances that App Engine should maintain for this version. Specify a value from 1 to 1000. If not specified, the default value is automatic, which means App Engine will manage the number of idle instances. Keep the following in mind: A high maximum reduces the number of idle instances more gradually when load levels return to normal after a spike. This helps your application maintain steady performance through fluctuations in request load, but also raises the number of idle instances (and consequent running costs) during such periods of heavy load.

asked 18/09/2024
Andrew Vogel
40 questions

Question 72

Report
Export
Collapse

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 local workstations.
Implement Jenkins on local workstations.
Implement Jenkins on Kubernetes on-premises
Implement Jenkins on Kubernetes on-premises
Implement Jenkins on Google Cloud Functions.
Implement Jenkins on Google Cloud Functions.
Implement Jenkins on Compute Engine virtual machines.
Implement Jenkins on Compute Engine virtual machines.
Suggested answer: D

Explanation:

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?

https://plugins.jenkins.io/google-compute-engine/

asked 18/09/2024
Rajesh Gurav
28 questions

Question 73

Report
Export
Collapse

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 Cloud Storage bucket and develop your application to send logs directly to the bucket.
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.
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 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.
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.
Suggested answer: D

Explanation:

https://cloud.google.com/logging/docs/routing/overview

asked 18/09/2024
tho nguyen
32 questions

Question 74

Report
Export
Collapse

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?

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 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 Google Kubernetes Engine.
Install the Stackdriver Error Reporting library for Python, and then run your code on App Engine flexible environment.
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.
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.
Suggested answer: D

Explanation:

https://cloud.google.com/error-reporting/docs/formatting-error-messages

https://cloud.google.com/error-reporting/docs/reference/libraries#client-libraries-install-python

no need to install error reporting library on App Engine Flex.

asked 18/09/2024
Brandon O'Driscoll
34 questions

Question 75

Report
Export
Collapse

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 -- 100ms 95th percentile -- 250ms
90th percentile -- 100ms 95th percentile -- 250ms
90th percentile -- 120ms 95th percentile -- 275ms
90th percentile -- 120ms 95th percentile -- 275ms
90th percentile -- 150ms 95th percentile -- 300ms
90th percentile -- 150ms 95th percentile -- 300ms
90th percentile -- 250ms 95th percentile -- 400ms
90th percentile -- 250ms 95th percentile -- 400ms
Suggested answer: C

Explanation:

https://sre.google/sre-book/service-level-objectives/

asked 18/09/2024
Nicholas Stoner
41 questions

Question 76

Report
Export
Collapse

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.
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 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.
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.
Add a plugin to your Jenkins pipeline that prevents new releases whenever your service is out of SLO.
Suggested answer: A

Explanation:

Reason : Incident has not occurred yet, even when development team is already pushing new features multiple times a week. The option A says, to define an error budget 'policy', not to define error budget(It is already present). Just simple means to bring in all stakeholders, and decide how to consume the error budget effectively that could bring balance between feature deployment and reliability.

The goals of this policy are to: -- Protect customers from repeated SLO misses -- Provide an incentive to balance reliability with other features https://sre.google/workbook/error-budget-policy/

asked 18/09/2024
Steven Moran
32 questions

Question 77

Report
Export
Collapse

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 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 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 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 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.
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.
Suggested answer: D

Explanation:

https://cloud.google.com/architecture/prep-kubernetes-engine-for-prod#roles_and_groups

asked 18/09/2024
Laura Archilla
36 questions

Question 78

Report
Export
Collapse

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 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 us.gcr.io hostname.
Push the images to Google Container Registry (GCR) using the eu.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.
Push the images to a private image registry running on a Compute Engine instance in the eu-west-1 region.
Suggested answer: C

Explanation:

Hostname Storage location gcr.io Stores images in data centers in the United States asia.gcr.io Stores images in data centers in Asia eu.gcr.io Stores images in data centers within member states of the European Union us.gcr.io Stores images in data centers in the United States

asked 18/09/2024
Carlos Periterra
40 questions

Question 79

Report
Export
Collapse

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?

In the Google Cloud Platform Console, use the Cost Breakdown section to visualize the costs per system.
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.
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.
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.
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.
Suggested answer: B

Explanation:

https://cloud.google.com/billing/docs/how-to/export-data-bigquery

asked 18/09/2024
Brad Jarrett
42 questions

Question 80

Report
Export
Collapse

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?

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.
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.
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 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.
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.
Suggested answer: D

Explanation:

https://cloud.google.com/build/docs/securing-builds/use-encrypted-credentials

asked 18/09/2024
Wojciech Romaldowski
43 questions
Total 166 questions
Go to page: of 17
Search
Open VPLUS File
Convert VPLUS to PDF

Related questions

You are creating a CI/CD pipeline to perform Terraform deployments of Google Cloud resources Your CI/CD tooling is running in Google Kubernetes Engine (GKE) and uses an ephemeral Pod for each pipeline run You must ensure that the pipelines that run in the Pods have the appropriate Identity and Access Management (1AM) permissions to perform the Terraform deployments You want to follow Google-recommended practices for identity management What should you do? Choose 2 answers
The new version of your containerized application has been tested and is ready to be deployed to production on Google Kubernetes Engine (GKE) You could not fully load-test the new version in your pre-production environment and you need to ensure that the application does not have performance problems after deployment Your deployment must be automated What should you do?
You are creating Cloud Logging sinks to export log entries from Cloud Logging to BigQuery for future analysis Your organization has a Google Cloud folder named Dev that contains development projects and a folder named Prod that contains production projects Log entries for development projects must be exported to dev_dataset. and log entries for production projects must be exported to prod_dataset You need to minimize the number of log sinks created and you want to ensure that the log sinks apply to future projects What should you do?
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?
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?
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?
You are managing an application that runs in Compute Engine The application uses a custom HTTP server to expose an API that is accessed by other applications through an internal TCP/UDP load balancer A firewall rule allows access to the API port from 0.0.0-0/0. You need to configure Cloud Logging to log each IP address that accesses the API by using the fewest number of steps What should you do Bret?
Your company runs applications in Google Kubernetes Engine (GKE). Several applications rely on ephemeral volumes. You noticed some applications were unstable due to the DiskPressure node condition on the worker nodes. You need to identify which Pods are causing the issue, but you do not have execute access to workloads and nodes. What should you do?
You need to build a CI/CD pipeline for a containerized application in Google Cloud Your development team uses a central Git repository for trunk-based development You want to run all your tests in the pipeline for any new versions of the application to improve the quality What should you do?
You support an application running on App Engine. The application is used globally and accessed from various device types. You want to know the number of connections. You are using Stackdriver Monitoring for App Engine. What metric should you use?