Professional Cloud DevOps Engineer Free Practice Questions — Page 9
Question 81
You are configuring Cloud Logging for a new application that runs on a Compute Engine instance with a public IP address. A user-managed service account is attached to the instance. You confirmed that the necessary agents are running on the instance but you cannot see any log entries from the instance in Cloud Logging. You want to resolve the issue by following Google-recommended practices. What should you do?
A. Export the service account key and configure the agents to use the key.
B. Update the instance to use the default Compute Engine service account.
C. Add the Logs Writer role to the service account.
D. Enable Private Google Access on the subnet that the instance is in.
Show Answer
Correct Answer: C
Explanation: A user-managed service account must have the appropriate IAM permissions to write logs. The Cloud Logging agent uses the attached service account's credentials via the metadata server, so exporting a service account key is not recommended. Switching to the default Compute Engine service account is unnecessary and contrary to least-privilege practices when a user-managed service account is already attached. Private Google Access is only needed for instances without external IPs; the instance has a public IP. Granting the Logs Writer role (roles/logging.logWriter) to the attached service account enables the agent to send logs to Cloud Logging.
Question 82
Your company runs applications in Google Kubernetes Engine (GKE) that are deployed following a GitOps methodology. Application developers frequently create cloud resources to support their applications. You want to give developers the ability to manage infrastructure as code, while ensuring that you follow Google-recommended practices. You need to ensure that infrastructure as code reconciles periodically to avoid configuration drift. What should you do?
A. Install and configure Config Connector in Google Kubernetes Engine (GKE).
B. Configure Cloud Build with a Terraform builder to execute terraform plan and terraform apply commands.
C. Create a Pod resource with a Terraform docker image to execute terraform plan and terraform apply commands.
D. Create a Job resource with a Terraform docker image to execute terraform plan and terraform apply commands.
Show Answer
Correct Answer: A
Explanation: Config Connector is the Google-recommended Kubernetes-native approach for managing Google Cloud resources as Kubernetes custom resources. It fits a GitOps workflow because desired state is stored declaratively in Kubernetes manifests and its controllers continuously reconcile actual state with desired state, preventing configuration drift. Cloud Build with Terraform can provision infrastructure, but it does not inherently provide continuous reconciliation. Running Terraform in Pods or Jobs is also not the recommended reconciliation mechanism.
Question 83
You need to enforce several constraint templates across your Google Kubernetes Engine (GKE) clusters. The constraints include policy parameters, such as restricting the Kubernetes API. You must ensure that the policy parameters are stored in a GitHub repository and automatically applied when changes occur. What should you do?
A. Set up a GitHub action to trigger Cloud Build when there is a parameter change. In Cloud Build, run a gcloud CLI command to apply the change.
B. When there is a change in GitHub. use a web hook to send a request to Anthos Service Mesh, and apply the change.
C. Configure Anthos Config Management with the GitHub repository. When there is a change in the repository, use Anthos Config Management to apply the change.
D. Configure Config Connector with the GitHub repository. When there is a change in the repository, use Config Connector to apply the change.
Show Answer
Correct Answer: C
Explanation: Anthos Config Management is the GitOps solution for synchronizing Kubernetes configuration and policy from a Git repository to GKE clusters. Constraint templates and Constraint resources (Policy Controller/Gatekeeper) can be stored in Git, including policy parameters, and ACM automatically reconciles changes across clusters. Config Connector manages Google Cloud resources rather than Kubernetes policy synchronization, Anthos Service Mesh is unrelated, and Cloud Build with gcloud is possible but not the intended managed GitOps approach.
Question 84
You need to introduce postmortems into your organization. You want to ensure that the postmortem process is well received. What should you do? (Choose two.)
A. Encourage new employees to conduct postmortems to team through practice.
B. Create a designated team that is responsible for conducting all postmortems.
C. Encourage your senior leadership to acknowledge and participate in postmortems.
D. Ensure that writing effective postmortems is a rewarded and celebrated practice.
E. Provide your organization with a forum to critique previous postmortems.
Show Answer
Correct Answer: C, D
Explanation: To successfully introduce a postmortem culture, leadership support and positive reinforcement are key. Senior leaders participating in and acknowledging postmortems demonstrates organizational commitment and psychological safety. Rewarding and celebrating high-quality postmortems encourages learning, transparency, and continuous improvement. Assigning postmortems to a dedicated team or only new employees undermines shared ownership, and critique forums are less important than establishing a blameless, supportive culture.
Question 85
You recently noticed that one of your services has exceeded the error budget for the current rolling window period. Your company's product team is about to launch a new feature. You want to follow Site Reliability Engineering (SRE) practices. What should you do?
A. Notify the team about the lack of error budget and ensure that all their tests are successful so the launch will not further risk the error budget
B. Notify the team that their error budget is used up. Negotiate with the team for a launch freeze or tolerate a slightly worse user experience.
C. Escalate the situation and request additional error budget.
D. Look through other metrics related to the product and find SLOs with remaining error budget. Reallocate the error budgets and allow the feature launch.
Show Answer
Correct Answer: B
Explanation: In SRE, when a service has exhausted its error budget, the standard practice is to slow or stop feature releases and prioritize reliability until the service returns within its SLO. The product and engineering teams should negotiate a release freeze or explicitly accept the tradeoff if leadership chooses to prioritize features despite reduced reliability. You do not request additional error budget or reallocate it from unrelated SLOs.
Question 86
You need to create a Cloud Monitoring SLO for a service that will be published soon. You want to verify that requests to the service will be addressed in fewer than 300 ms at least 90% of the time per calendar month. You need to identify the metric and evaluation method to use. What should you do?
A. Select a latency metric for a request-based method of evaluation.
B. Select a latency metric for a window-based method of evaluation.
C. Select an availability metric for a request-based method of evaluation.
D. Select an availability metric for a window-based method of evaluation.
Show Answer
Correct Answer: A
Explanation: The SLO is about latency (requests completed in fewer than 300 ms), not availability. A request-based SLO measures the proportion of individual requests that satisfy the latency threshold over the compliance period (here, a calendar month). A window-based SLO instead measures the proportion of time windows that meet a criterion, which is not what the requirement states.
Question 87
You are the Site Reliability Engineer responsible for managing your company's data services and products. You regularly navigate operational challenges, such as unpredictable data volume and high cost, with your company's data ingestion processes. You recently learned that a new data ingestion product will be developed in Google Cloud. You need to collaborate with the product development team to provide operational input on the new product. What should you do?
A. Deploy the prototype product in a test environment, run a load test, and share the results with the product development team.
B. When the initial product version passes the quality assurance phase and compliance assessments, deploy the product to a staging environment. Share error logs and performance metrics with the product development team.
C. When the new product is used by at least one internal customer in production, share error logs and monitoring metrics with the product development team.
D. Review the design of the product with the product development team to provide feedback early in the design phase.
Show Answer
Correct Answer: D
Explanation: The correct choice is D. SRE principles emphasize engaging early in the product lifecycle ('shift left') to influence architecture and operability before implementation. Reviewing the design allows you to provide feedback on scalability, reliability, observability, cost, capacity planning, and operational risks before they become expensive to change. The other options wait until testing, staging, or production, which is later than recommended for effective operational collaboration.
Question 89
Your CTO has asked you to implement a postmortem policy on every incident for internal use. You want to define what a good postmortem is to ensure that the policy is successful at your company. What should you do? (Choose two.)
A. Ensure that all postmortems include what caused the incident, identify the person or team responsible for causing the incident, and how to prevent a future occurrence of the incident.
B. Ensure that all postmortems include what caused the incident, how the incident could have been worse, and how to prevent a future occurrence of the incident.
C. Ensure that all postmortems include the severity of the incident, how to prevent a future occurrence of the incident, and what caused the incident without naming internal system components.
D. Ensure that all postmortems include how the incident was resolved and what caused the incident without naming customer information.
E. Ensure that all postmortems include all incident participants in postmortem authoring and share postmortems as widely as possible.
Show Answer
Correct Answer: C, E
Explanation: A good internal postmortem should be blameless, document incident severity, causes, and preventive actions, and encourage broad organizational learning. Identifying individuals or teams to blame is contrary to blameless postmortem practices. Including all incident participants in authoring improves accuracy, and sharing postmortems widely helps spread lessons learned. Omitting internal system components is appropriate for broadly shared internal documentation, while customer information is unrelated to defining a good postmortem policy.
Question 90
You are the on-call Site Reliability Engineer for a microservice that is deployed to a Google Kubernetes Engine (GKE) Autopilot cluster. Your company runs an online store that publishes order messages to Pub/Sub, and a microservice receives these messages and updates stock information in the warehousing system. A sales event caused an increase in orders, and the stock information is not being updated quickly enough. This is causing a large number of orders to be accepted for products that are out of stock. You check the metrics for the microservice and compare them to typical levels:
You need to ensure that the warehouse system accurately reflects product inventory at the time orders are placed and minimize the impact on customers. What should you do?
A. Decrease the acknowledgment deadline on the subscription.
B. Add a virtual queue to the online store that allows typical traffic levels.
C. Increase the number of Pod replicas.
D. Increase the Pod CPU and memory limits.
Show Answer
Correct Answer: C
Explanation: The symptoms indicate the consumer service is falling behind processing Pub/Sub messages, creating a growing backlog. If CPU and memory usage are not saturated, increasing per-Pod resources is unlikely to help. Scaling horizontally by increasing the number of Pod replicas allows more messages to be processed concurrently, reducing the backlog and updating inventory faster. Decreasing the acknowledgment deadline does not increase throughput, and adding a virtual queue throttles incoming orders rather than addressing the immediate processing bottleneck.
Question 91
You are developing the deployment and testing strategies for your CI/CD pipeline in Google Cloud. You must be able to:
• Reduce the complexity of release deployments and minimize the duration of deployment rollbacks.
• Test real production traffic with a gradual increase in the number of affected users.
You want to select a deployment and testing strategy that meets your requirements. What should you do?
A. Recreate deployment and canary testing
B. Blue/green deployment and canary testing
C. Rolling update deployment and A/B testing
D. Rolling update deployment and shadow testing
Show Answer
Correct Answer: B
Explanation: Blue/green deployment minimizes deployment complexity and enables very fast rollback by switching traffic between two environments. Canary testing gradually exposes the new version to increasing percentages of real production users, allowing validation under real traffic before full rollout.
$19
Get all 208 questions with detailed answers and explanations
Instant download HTML + PDF delivered the moment payment clears.
Secure Stripe checkout we never see or store your card details.
7-day refund if files are defective see our refund policy.