Pass the Google Cloud DevOps Engineer Professional-Cloud-DevOps-Engineer Questions and answers with CertsForce

Viewing page 4 out of 6 pages
Viewing questions 31-40 out of questions
Questions # 31:

As a Site Reliability Engineer, you support an application written in GO that runs on Google Kubernetes Engine (GKE) in production. After releasing a new version Of the application, you notice the applicationruns for about 15 minutes and then restarts. You decide to add Cloud Profiler to your application and now notice that the heap usage grows constantly until the application restarts. What should you do?

Options:

A.

Add high memory compute nodes to the cluster.


B.

Increase the memory limit in the application deployment.


C.

Add Cloud Trace to the application, and redeploy.


D.

Increase the CPU limit in the application deployment.


Questions # 32:

You support a production service that runs on a single Compute Engine instance. You regularly need to spend time on recreating the service by deleting the crashing instance and creating a new instance based on the relevant image. You want to reduce the time spent performing manual operations while following Site Reliability Engineering principles. What should you do?

Options:

A.

File a bug with the development team so they can find the root cause of the crashing instance.


B.

Create a Managed Instance Group with a single instance and use health checks to determine the system status.


C.

Add a Load Balancer in front of the Compute Engine instance and use health checks to determine the system status.


D.

Create a Stackdriver Monitoring dashboard with SMS alerts to be able to start recreating the crashed instance promptly after it has crashed.


Questions # 33:

Your team is building a service that performs compute-heavy processing on batches of data The data is processed faster based on the speed and number of CPUs on the machine These batches of data vary in size and may arrive at any time from multiple third-party sources You need to ensure that third partiesare able to upload their data securely. You want to minimize costs while ensuring that the data is processed as quickly as possible What should you do?

Options:

A.

• Provide a secure file transfer protocol (SFTP) server on a Compute Engine instance so that thirdparties can upload batches of data and provide appropriate credentials to the server• Create a Cloud Function with a google.storage, object, finalize Cloud Storage trigger Write code so that the function can scale up a Compute Engine autoscaling managed instance group• Use an image pre-loaded with the data processing software that terminates th


B.

• Provide a Cloud Storage bucket so that third parties can upload batches of data, and provideappropriate Identity and Access Management (1AM) access to the bucket• Use a standard Google Kubernetes Engine (GKE) cluster and maintain two services one that processes the batches of data and one that monitors Cloud Storage for new batches of data• Stop the processing service when there are no batches of data to process


C.

• Provide a Cloud Storage bucket so that third parties can upload batches of data, and provide appropriate identity and Access Management (1AM) access to the bucket• Create a Cloud Function with a google, storage, object .finalise Cloud Storage trigger Write code so that the function can scale up a Compute Engine autoscaling managed instance group• Use an image pre-loaded with the data processing software that terminates the instances when


D.

• Provide a Cloud Storage bucket so that third parties can upload batches of data, and provideappropriate Identity and Access Management (1AM) access to the bucket• Use Cloud Monitoring to detect new batches of data in the bucket and trigger a Cloud Function that processes the data• Set a Cloud Function to use the largest CPU possible to minimize the runtime of the processing


Questions # 34:

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?

Options:

A.

Load teat the application to profile its performance for scaling.


B.

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


C.

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


D.

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


Questions # 35:

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?

Options:

A.

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


B.

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


C.

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


D.

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


Questions # 36:

Your company recently migrated to Google Cloud. You need to design a fast, reliable, and repeatable solution for your company to provision new projects and basic resources in Google Cloud. What should you do?

Options:

A.

Use the Google Cloud console to create projects.


B.

Write a script by using the gcloud CLI that passes the appropriate parameters from the request. Save the script in a Git repository.


C.

Write a Terraform module and save it in your source control repository. Copy and run the apply command to create the new project.


D.

Use the Terraform repositories from the Cloud Foundation Toolkit. Apply the code with appropriate parameters to create the Google Cloud project and related resources.


Questions # 37:

Your product is currently deployed in three Google Cloud Platform (GCP) zones with your users divided between the zones. You can fail over from one zone to another, but it causes a 10-minute service disruption for the affected users. You typically experience a database failure once per quarter and can detect it within five minutes. You are cataloging the reliability risks of a new real-time chat feature for your product. You catalog the following information for each risk:

• Mean Time to Detect (MUD} in minutes

• Mean Time to Repair (MTTR) in minutes

• Mean Time Between Failure (MTBF) in days

• User Impact Percentage

The chat feature requires a new database system that takes twice as long to successfully fail over between zones. You want to account for the risk of the new database failing in one zone. What would be the values for the risk of database failover with the new system?

Options:

A.

MTTD: 5MTTR: 10MTBF: 90Impact: 33%


B.

MTTD:5MTTR: 20MTBF: 90Impact: 33%


C.

MTTD:5MTTR: 10MTBF: 90Impact 50%


D.

MTTD:5MTTR: 20MTBF: 90Impact: 50%


Questions # 38:

Your development team has created a new version of their service’s API. You need to deploy the new versions of the API with the least disruption to third-party developers and end users of third-party installed applications. What should you do?

Options:

A.

Introduce the new version of the API.Announce deprecation of the old version of the API.Deprecate the old version of the API.Contact remaining users of the old API.Provide best effort support to users of the old API.Turn down the old version of the API.


B.

Announce deprecation of the old version of the API.Introduce the new version of the API.Contact remaining users on the old API.Deprecate the old version of the API.Turn down the old version of the API.Provide best effort support to users of the old API.


C.

Announce deprecation of the old version of the API.Contact remaining users on the old API.Introduce the new version of the API.Deprecate the old version of the API.Provide best effort support to users of the old API.Turn down the old version of the API.


D.

Introduce the new version of the API.Contact remaining users of the old API.Announce deprecation of the old version of the API.Deprecate the old version of the API.Turn down the old version of the API.Provide best effort support to users of the old API.


Questions # 39:

Your organization wants to increase the availability target of an application from 99 9% to 99 99% for an investment of $2 000 The application's current revenue is S1,000,000 You need to determine whether the increase in availability is worth the investment for a single year of usage What should you do?

Options:

A.

Calculate the value of improved availability to be $900, and determine that the increase in availability is not worth the investment


B.

Calculate the value of improved availability to be $1 000 and determine that the increase in availability is not worth the investment


C.

Calculate the value of improved availability to be $1 000 and determine that the increase in availability is worth the investment


D.

Calculate the value of improved availability to be $9,000. and determine that the increase in availability is worth the investment


Questions # 40:

You are investigating issues in your production application that runs on Google Kubernetes Engine (GKE). You determined that the source Of the issue is a recently updated container image, although the exact change in code was not identified. The deployment is currently pointing to the latest tag. You need to update your cluster to run a version of the container that functions as intended. What should you do?

Options:

A.

Create a new tag called stable that points to the previously working container, and change the deployment to point to the new tag.


B.

Apply the latest tag to the previous container image, and do a rolling update on the deployment.


C.

Build a new container from a previous Git tag, and do a rolling update on the deployment to the new container.


D.

Alter the deployment to point to the sha2 56 digest of the previously working container.


Viewing page 4 out of 6 pages
Viewing questions 31-40 out of questions