Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
A business-critical microservices application deployed across Google Kubernetes Engine (GKE) and managed with Cloud Service Mesh recently experienced significant latency degradation and an elevated rate of HTTP 5xx responses following a new release rollout. The automated deployment pipeline executed a rollback to restore the previous stable application revision.
To verify service functionality and performance metrics post-rollback, determine the incident's root cause, and establish preventive measures for future deployment strategies, what should the SRE team do?
This approach encompasses comprehensive post-rollback system state verification, observability-driven root cause analysis (RCA), and structured post-incident learning consistent with Site Reliability Engineering (SRE) best practices in Google Cloud.
RESPONSE_FLAGS, RESPONSE_CODE, and UPSTREAM_LOCAL_ADDRESS) and distributed traces via Cloud Trace allows engineers to differentiate between application-level failures (e.g., unhandled exceptions or database connection exhaustion) and data-plane routing issues (e.g., Envoy proxy misconfigurations or circuit breaking).Validating post-rollback stability using quantitative metrics and analyzing distributed telemetry provides the definitive evidence needed to understand failures and prevent regressions, making it the most robust operational strategy.
This option deletes historical audit and application telemetry from Cloud Logging, runs an extreme artificial stress test on recently recovered production pods, and forces a redeployment of the broken build without timeout safeguards.
You were conducting destructive chaos engineering or load stress benchmarking in an isolated staging environment with mock data, rather than diagnosing and remediating an active production incident.
This option activates Binary Authorization breakglass to bypass signature verification policies, removes automated progressive release controls (canary gates) from the CI/CD pipeline, and manually alters running containers via interactive terminal sessions.
There was an emergency where critical cryptographic signing keys were inaccessible during an urgent breakfix deployment requiring immediate bypass of image signature enforcement.
This option modifies specific Cloud Service Mesh infrastructure settings by requesting higher backend service quotas, altering DNS resolution modes on external service entry points, and rebooting all GKE nodes across the cluster at once.
ServiceEntry DNS resolution) assumes a specific networking bug without first inspecting logs, metrics, or traces to verify where the issue actually occurred.BackendService limit exhaustion during resource provisioning.The specific root cause was already diagnosed as external non-HTTP load balancer DNS resolution failures and backend service quota exhaustion within the Cloud Service Mesh control plane.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated