Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A retail organization's primary e-commerce application running in production on Google Cloud suddenly stops serving traffic to customers. The operations team observes the following conditions:
How should the team classify and submit the support case to ensure effective initial triage and the fastest possible response from Customer Care?
In Google Cloud Customer Care, case priority defines the severity and urgency of a technical issue, directly governing target initial response times and support workflows. Priority 1 (P1): Critical Impact is the highest severity classification, reserved for production outages where an application or infrastructure is completely unusable. Initiating a case in the Google Cloud console requires selecting the impacted resource, choosing the appropriate product and sub-category, setting the priority level, and supplying comprehensive diagnostic context.
Waiting on customer response status.Assigning P1 while providing thorough, structured technical context is the only approach that aligns both the support Service Level Objective (SLO) and the triage routing with a critical production outage.
Priority 2 (P2): High Impact is a classification used when production infrastructure is severely impaired or degraded, but business impact is moderate or a workaround is available to mitigate critical impact. Case escalation is an administrative mechanism available to Enhanced Support and Premium Support customers that assigns an Escalation Manager to investigate breakdowns in the support resolution process.
This approach would be appropriate if the production service was merely degraded with a quick workaround already in place (P2), and an existing support case had stalled without updates or failed to meet expectations aligned with business impact, requiring an Escalation Manager to intervene.
Priority 3 (P3): Medium Impact is a support classification for issues that are limited in scope or severity, where service use is only partially impaired and there is no user-visible impact. During case creation in the Google Cloud console, selecting a product category and sub-category is the mechanism used to forward a support ticket to the specialized technical team responsible for that component.
Opening a P3 case (as a single ticket, not duplicates) would be correct if the organization encountered a non-urgent bug in a development environment or a minor administrative inconvenience that had zero visible impact on end users.
Priority 4 (P4): Low Impact is the lowest severity level in Google Cloud Customer Care, designated for consultative inquiries where the service remains fully usable and there is little to no business or technical impact. Cloud Billing support is a support channel included free of charge with Basic Support for all Google Cloud accounts to resolve invoicing, payment, and account billing inquiries. Attaching log files and artifacts is a standard method for providing diagnostic context during case creation.
Using P4 would be appropriate if an engineer wanted non-urgent, consultative advice on cloud best practices with properly redacted artifacts, while the Billing support channel would be correct if an administrator had a question about a monthly invoice.
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