Free Preparation Discussions
MENU
Google Professional Cloud DevOps Engineer Exam Questions
- Topic 1: Bootstrapping a Google Cloud organization for DevOps: It discusses the overall resource hierarchy for an organization, infrastructure as code, CI/CD architecture stack in Google Cloud, hybrid, and multi-cloud environments. Moreover, the topic focuses on multiple environments including staging and production.
- Topic 2: Building and implementing CI/CD pipelines for a service: Management and designing of CI/CD pipelines, implementation of CI/CD pipelines, management of CI/CD configuration, and secrets are discussed in this paper. Moreover, it focuses on storage methods and key rotation services, and finally securing the CI/CD deployment pipeline.
- Topic 3: Applying site reliability engineering practices to a service: It deals with velocity, and reliability of the service, service lifecycle, healthy communication, and collaboration for operations. The topic also discusses mitigation of incident impact on users and conducting a postmortem.
- Topic 4: Implementing service monitoring strategies: This topic covers structured and unstructured logs from Compute Engine, GKE, and serverless platforms using Cloud Logging. Its sub-topics include coverage of metrics with Cloud Monitoring, dashboards and alerts in Cloud Monitoring, Cloud Logging platform, and logging and monitoring access controls.
- Topic 5: Optimizing the service performance: It delves into the identification of service performance issues, implementation of debugging tools in Google Cloud, and optimization of resource utilization and costs.
Free Google Professional Cloud DevOps Engineer Exam Actual Questions
Note: Premium Questions for Professional Cloud DevOps Engineer were last updated On Apr. 13, 2025 (see below)
Your team is writing a postmortem after an incident on your external facing application Your team wants to improve the postmortem policy to include triggers that indicate whether an incident requires a postmortem Based on Site Reliability Engineenng (SRE) practices, what triggers should be defined in the postmortem policy?
Choose 2 answers
The best options for defining triggers that indicate whether an incident requires a postmortem based on Site Reliability Engineering (SRE) practices are an external stakeholder asks for a postmortem and data is lost due to an incident. An external stakeholder is someone who is affected by or has an interest in the service, such as a customer or a partner. If an external stakeholder asks for a postmortem, it means that they are concerned about the impact or root cause of the incident, and they expect an explanation and remediation from the service provider. Therefore, this should trigger a postmortem to address their concerns and improve their satisfaction. Data loss is a serious consequence of an incident that can affect the integrity and reliability of the service. If data is lost due to an incident, it means that there was a failure in the backup or recovery mechanisms, or that there was a corruption or deletion of data. Therefore, this should trigger a postmortem to investigate the cause and impact of the data loss, and to prevent it from happening again.
Your application's performance in Google Cloud has degraded since the last release. You suspect that downstream dependencies might be causing some requests to take longer to complete. You need to investigate the issue with your application to determine the cause. What should you do?
Comprehensive and Detailed
Google Cloud Trace is specifically designed to analyze request latency and identify performance bottlenecks across services. Since the issue is related to slow performance after a new release, the best approach is to use Cloud Trace to:
Visualize request latency across services
Pinpoint slow dependencies affecting response time
Analyze performance trends over time
Why not other options?
B (Error Reporting) Focuses on uncaught exceptions and crashes, not latency issues.
C (Cloud Profiler) Helps with CPU and memory analysis, not request tracing.
D (Prometheus for Cloud Monitoring) Useful for metrics collection, but not ideal for debugging specific request latency issues.
Official Reference:
Your company's security team needs to have read-only access to Data Access audit logs in the _Required bucket You want to provide your security team with the necessary permissions following the principle of least privilege and Google-recommended practices. What should you do?
The best option for providing your security team with the necessary permissions following the principle of least privilege and Google-recommended practices is to assign the roles/logging.privateLogViewer role to a group with all the security team members. The roles/logging.privateLogViewer role is a predefined role that grants read-only access to Data Access audit logs and other private logs in Cloud Logging. A group is a collection of users that can be assigned roles and permissions as a single unit. You can assign the roles/logging.privateLogViewer role to a group with all the security team members by using IAM policies. This way, you can provide your security team with the minimum level of access they need to view Data Access audit logs in the _Required bucket.
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?
Your uses Jenkins running on Google Cloud VM instances for CI/CD. You need to extend the functionality to use infrastructure as code automation by using Terraform. You must ensure that the Terraform Jenkins instance is authorized to create Google Cloud resources. You want to follow Google-recommended practices- What should you do?
The correct answer is C)
Answer D is incorrect because it involves using the Terraform module for Secret Manager, which is a service that stores and manages sensitive data such as API keys, passwords, and certificates. While Secret Manager can be used to store and retrieve credentials, it is not necessary or sufficient for authorizing the Terraform Jenkins instance. The Terraform Jenkins instance still needs a service account with the appropriate IAM permissions to access Secret Manager and other Google Cloud resources.
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Tiffiny
11 days agoMaile
13 days agoShaunna
28 days agoRebbecca
1 months agoRebecka
1 months agoMaile
2 months agoTeri
2 months agoFelix
2 months agoMelissia
3 months agoGertude
3 months agoJosue
3 months agoAnika
3 months agoMargurite
4 months agoSelma
4 months agoKristian
4 months agoJanna
4 months agoKirby
4 months agoPhyliss
5 months agoSkye
5 months agoPeggie
5 months agoSharan
5 months agoMollie
6 months agoNovella
6 months agoLynette
6 months agoFiliberto
6 months agoToi
6 months agoKeva
7 months agoBerry
7 months agoMaynard
7 months agoRosenda
8 months agoMicheline
8 months agoHelga
9 months agoJoana
9 months agoSunny
10 months agoAliza
10 months agoTracie
10 months agoJimmy
1 years ago