This chapter covers Google Cloud Support Plans and the Service Level Agreements (SLAs) that underpin them. Understanding the differences between Basic, Standard, Enhanced, and Premium support tiers is critical for the GCDL exam, which tests your ability to match support needs to business requirements. Approximately 10-15% of exam questions touch on support plans and SLAs, often asking which tier to recommend for a given scenario or how SLAs apply to specific services.
Jump to a section
Google Cloud support plans are analogous to car insurance tiers: Basic is like liability-only coverage, where you pay a low monthly premium but get minimal help—you can only file a claim via a web form, and response times are slow. Standard is like a mid-tier policy with roadside assistance: you get a dedicated phone number and faster response times for breakdowns (P1 issues), but you still handle most repairs yourself. Enhanced is like comprehensive insurance with a 24/7 concierge: you have a named agent who knows your fleet, you get priority dispatching for critical incidents (15-minute P1 response), and you have access to a library of service manuals (third-party software support). Premium is like having a full-time mechanic on retainer: you get a dedicated account manager, a technical account manager who proactively monitors your vehicles, and the fastest response times (5-minute P1). Each tier adds more people, faster response, and broader coverage, but the core service—fixing what's broken—remains the same; only the speed, availability, and depth of expertise change.
What Google Cloud Support Plans Are
Google Cloud offers four support tiers: Basic (free), Standard ($29/month per user), Enhanced ($15,000/month), and Premium (custom pricing, typically starting at $150,000+/year). Each tier defines the channels available for contacting support, the response times for severity levels, and additional services like third-party software support, technical account management, and infrastructure health reviews. The GCDL exam expects you to know the key differentiators: Basic provides only online case submission with no phone or chat; Standard adds phone and chat but with slower response times; Enhanced includes faster response (15 minutes for P1) and third-party software support; Premium offers a Technical Account Manager (TAM), proactive guidance, and 5-minute P1 response.
How Support Response Times Work
Google defines four severity levels (P1 through P4) based on business impact. P1 is critical (production down, data loss, security incident), P2 is major (significant functionality impaired), P3 is minor (non-critical issues), and P4 is informational. The target initial response times vary by tier:
Basic: P1: 8 hours, P2: 8 hours, P3: 8 hours, P4: 8 hours (all via web only)
Standard: P1: 1 hour, P2: 4 hours, P3: 8 hours, P4: 8 hours (phone/chat available for P1-P2)
Enhanced: P1: 15 minutes, P2: 1 hour, P3: 4 hours, P4: 8 hours (phone/chat for all)
Premium: P1: 5 minutes, P2: 15 minutes, P3: 1 hour, P4: 4 hours (phone/chat for all, plus TAM)
These response times are contractual commitments; failure to meet them may result in service credits. However, response time is not resolution time—it's the time to acknowledge the case and assign a support engineer.
Service Level Agreements (SLAs)
Google Cloud SLAs are separate from support plans. SLAs define uptime guarantees for each service (e.g., Compute Engine: 99.95% for single-instance, 99.99% for multi-zone; Cloud Storage: 99.9% for multi-regional; BigQuery: 99.9% for on-demand queries). If Google fails to meet the SLA, customers can request service credits (typically 10-50% of monthly fees) depending on the duration of the outage. SLAs are measured on a monthly basis. The exam tests your ability to interpret SLA tables and calculate credits.
Key SLA Terms and Default Values
Uptime percentage: Calculated as (Total monthly minutes - Downtime minutes) / Total monthly minutes × 100. Downtime is defined as when the service is unavailable for more than a specified threshold (e.g., 5 consecutive minutes for Compute Engine).
Service credits: For Compute Engine, if uptime < 99.95% but ≥ 99.0%, you get 10% credit; if < 99.0%, you get 25% credit; if < 95.0%, you get 50% credit. These percentages apply to the monthly bill for the affected service.
Exclusions: Scheduled maintenance, customer-caused outages, force majeure, and beta/alpha features are not covered by SLAs.
How SLAs Interact with Support Plans
Support plans and SLAs are independent. You can have Basic support and still receive SLA credits if a service fails to meet its uptime guarantee. However, filing an SLA claim requires opening a support case—which is easier and faster with higher-tier plans. Premium customers typically have a TAM who can help navigate the SLA claim process.
Third-Party Software Support
Enhanced and Premium tiers include support for common third-party software running on Google Cloud, such as Apache, MySQL, Nginx, and Docker. Basic and Standard do not. This is a frequent exam trap: candidates assume all plans include third-party support, but only the two highest tiers do.
Technical Account Manager (TAM) and Customer Success Services
Only Premium includes a dedicated TAM who conducts quarterly business reviews, provides proactive guidance, and assists with incident response. Enhanced includes an assigned support engineer but no TAM. Basic and Standard have no dedicated engineer. The exam often asks which tier provides a TAM—the answer is Premium.
Infrastructure Health Reviews and Training
Premium includes two infrastructure health reviews per year and up to two days of training per year. Enhanced includes one health review. Basic and Standard include none. These are differentiators for enterprise customers.
Case Management and Escalation
All paid tiers (Standard, Enhanced, Premium) allow case creation via web, phone, and chat. Basic is web-only. Escalation paths exist for critical issues: if you are unsatisfied with the support engineer's response, you can request a manager escalation. Premium customers have a faster escalation path through their TAM.
Billing and Scaling
Standard is per-user per-month ($29/user/month). Enhanced is a flat $15,000/month. Premium is custom-priced based on total Google Cloud spend (typically 1-4% of spend). The exam may ask you to calculate the cost for a given number of users or recommend a tier based on budget and needs.
Common Exam Scenarios
A startup with a small team and low budget should choose Standard (or Basic if they can tolerate slow response).
A mid-size company needing faster P1 response and third-party support should choose Enhanced.
An enterprise with critical production workloads requiring a TAM and proactive guidance should choose Premium.
A company that only needs SLA credits and can wait for email responses can use Basic.
SLA Calculation Example
Compute Engine single-instance SLA: 99.95% uptime guarantee. Monthly downtime allowed = (1 - 0.9995) × 43,830 minutes/month = 21.9 minutes. If downtime exceeds 21.9 minutes, credits apply. If downtime is 30 minutes, uptime = (43830 - 30) / 43830 = 99.93%, which is below 99.95% but above 99.0%, so 10% credit.
Multi-Region vs Single-Region SLAs
Services that span multiple zones or regions have higher SLAs. For example, Compute Engine instances in multiple zones (with a load balancer) have a 99.99% SLA, and Cloud Storage multi-regional has 99.95% SLA. The exam may ask which configuration yields the highest uptime guarantee.
SLA Exclusions and Fine Print
Common exclusions: 1) Scheduled maintenance with prior notice, 2) Customer misconfiguration (e.g., insufficient quota, firewall rules blocking traffic), 3) Beta or alpha features, 4) Services not covered by SLA (e.g., some APIs in preview), 5) Force majeure events. The exam loves to test these exclusions—e.g., "Which of the following is NOT covered by the Compute Engine SLA?" Answer: Downtime caused by exceeding quota limits.
Identify Business Requirements
Before choosing a support plan, assess your organization's needs: budget size (small/medium/large), criticality of workloads (production vs. development), required response times for outages, need for third-party software support, and desire for proactive guidance (TAM). For example, a startup with 5 developers and a single web server can tolerate 8-hour response times and no third-party support, so Basic or Standard suffices. An e-commerce company with $1M/day revenue requires 5-minute P1 response and a TAM, so Premium is appropriate.
Select Support Tier
Based on requirements, choose a tier: Basic (free, web-only, 8-hour response for all severities), Standard ($29/user/month, phone/chat for P1-P2, 1-hour P1 response), Enhanced ($15,000/month flat, 15-minute P1, third-party support, one health review), or Premium (custom pricing, 5-minute P1, TAM, two health reviews, training). The exam will present scenarios and ask which tier to recommend. Remember that Basic has no phone or chat, and Enhanced and Premium include third-party software support.
Configure Support Access
For paid tiers (Standard, Enhanced, Premium), administrators grant support access to users via the Google Cloud Console under IAM & Admin > Support > Support Access. Roles like 'Support User' (create cases) and 'Support Manager' (view all cases) are assigned. Basic users automatically have access to submit cases via the console. This step is often overlooked but is required for paid tiers to function.
Open a Support Case
When an issue occurs, the user creates a case via web (all tiers), phone (Standard+), or chat (Standard+). They must specify severity (P1-P4) and provide relevant details (project ID, resource name, error logs). The support system assigns a case ID and routes to the appropriate team. For Premium, the TAM is automatically notified for P1 cases. Response time SLA starts from the moment the case is submitted and acknowledged.
Monitor and Escalate if Needed
If the response time is not met or the solution is unsatisfactory, the user can escalate by requesting a manager or, for Premium, contacting their TAM. Google tracks response times and may issue service credits if SLAs are breached. The case is closed when the user confirms resolution. For SLA claims, the user must request credits within 30 days of the end of the billing month.
Enterprise Scenario 1: Global E-commerce Platform A multinational retailer with $5B annual revenue runs its entire e-commerce platform on Google Cloud, including Compute Engine, Cloud SQL, and Cloud CDN. They have a 99.99% uptime SLA requirement from their customers. They choose Premium support because they need a TAM to coordinate incident response across time zones and ensure 5-minute P1 response. The TAM conducts quarterly business reviews, identifies potential single points of failure (e.g., single-zone deployments), and recommends multi-region configurations. During a major outage caused by a misconfigured firewall, the TAM helps escalate to Google engineering within 10 minutes, resulting in a 30-minute resolution instead of hours. The Premium cost (~$500k/year) is justified by avoiding even one hour of downtime, which costs $570k.
Scenario 2: SaaS Startup with Limited Budget A 20-person SaaS startup with $50k/month GCP spend uses Basic support initially. They experience a database outage that takes 8 hours to get a response. They upgrade to Standard ($580/month for 20 users) to get phone support and 1-hour P1 response. Later, they need help with a third-party tool (Redis) and realize Standard doesn't cover it. They upgrade to Enhanced ($15,000/month) which is a big jump but includes third-party support and faster response. The founder regrets not evaluating third-party needs earlier.
Scenario 3: Government Agency with Compliance Needs A government agency requires a TAM for strategic guidance and needs third-party support for Apache and PostgreSQL. They choose Enhanced because Premium is too expensive for their budget. However, they later find that Enhanced does not include a TAM, so they negotiate a custom Premium plan at a reduced rate. The lesson: Always confirm which features are included in each tier, especially TAM and health reviews.
Common Misconfiguration: A company selects Standard support but expects 15-minute P1 response. They file an SLA claim after a 45-minute response, only to learn that Standard's P1 response is 1 hour. They should have chosen Enhanced for 15-minute response.
GCDL Objective Codes: This chapter maps to Objective 1.2 ("Identify the business value of Google Cloud support plans and SLAs") and indirectly to 1.1 ("Identify the business value of Google Cloud's infrastructure and technology"). The exam tests your ability to match support tiers to business scenarios, interpret SLA tables, and understand exclusions.
Top 4 Wrong Answers: 1. Choosing Basic for a production workload: Candidates think 'free' is always best, ignoring that Basic has no phone support and 8-hour response. The exam will present a scenario where a production system is down and ask for the appropriate tier. The correct answer is at least Standard, if not Enhanced. 2. Assuming all tiers include third-party software support: Many candidates select Standard for a company using Apache, but Standard does not cover third-party software. Only Enhanced and Premium do. 3. Confusing SLA response time with resolution time: The exam may ask 'How quickly will Google resolve a P1 issue?' The correct answer is 'There is no guaranteed resolution time; only initial response time is guaranteed.' Candidates often pick a specific resolution time like '1 hour' which is wrong. 4. Believing SLAs apply to all services: Some services (e.g., beta features, some APIs) are not covered by SLAs. The exam may list services and ask which has an SLA. Candidates need to know that generally, GA services have SLAs, but alpha/beta do not.
Specific Numbers to Memorize:
Basic P1 response: 8 hours
Standard P1 response: 1 hour
Enhanced P1 response: 15 minutes
Premium P1 response: 5 minutes
Standard cost: $29/user/month
Enhanced cost: $15,000/month
Compute Engine single-instance SLA: 99.95%
Compute Engine multi-zone SLA: 99.99%
Cloud Storage multi-regional SLA: 99.95%
BigQuery on-demand SLA: 99.9%
Edge Cases:
If a company has no users (e.g., using service accounts only), Standard is still per-user but can be assigned to administrators. The exam may ask about cost for a team of 10: $290/month.
Enhanced is a flat fee regardless of number of users, so for large teams it can be cheaper than Standard per-user.
Premium pricing is not published; it's negotiated based on spend.
Elimination Strategy: When answering a question about support plans, first eliminate Basic if the scenario mentions 'phone support' or 'fast response.' Eliminate Standard if 'third-party software support' or 'TAM' is needed. Eliminate Enhanced if 'TAM' is required. The remaining tier is likely Premium.
Basic support is free but web-only with 8-hour response for all severities.
Standard support costs $29/user/month and includes phone/chat with 1-hour P1 response.
Enhanced support costs $15,000/month flat and offers 15-minute P1 response and third-party software support.
Premium support offers 5-minute P1 response, a dedicated TAM, and two health reviews per year.
SLAs guarantee uptime (e.g., Compute Engine single-instance: 99.95%) and offer service credits if breached.
SLA credits must be requested within 30 days of the billing month end.
Third-party software support is only available with Enhanced and Premium.
A Technical Account Manager (TAM) is exclusive to Premium support.
SLA response time is not resolution time; only initial response is guaranteed.
Beta/alpha features and customer-caused outages are excluded from SLAs.
These come up on the exam all the time. Here's how to tell them apart.
Basic Support
Free of charge
Web-only case submission
8-hour response for all severities
No phone or chat
No third-party software support
Standard Support
$29/user/month
Phone, chat, and web case submission
1-hour P1 response, 4-hour P2
Includes phone and chat for P1-P2
No third-party software support
Enhanced Support
$15,000/month flat fee
15-minute P1 response
Includes third-party software support
One infrastructure health review per year
No dedicated TAM
Premium Support
Custom pricing (typically 1-4% of spend)
5-minute P1 response
Includes third-party software support
Two health reviews per year
Includes dedicated TAM and training
Mistake
All support plans include phone and chat support.
Correct
Only Standard, Enhanced, and Premium include phone and chat. Basic is web-only (case submission via console).
Mistake
Higher support tiers guarantee faster resolution times.
Correct
SLAs only guarantee initial response time, not resolution time. Resolution depends on issue complexity.
Mistake
SLA credits are automatically applied.
Correct
Customers must request SLA credits by opening a support case within 30 days of the end of the billing month. Credits are not automatic.
Mistake
Third-party software support is included in Standard.
Correct
Third-party software support is only included in Enhanced and Premium tiers. Standard and Basic do not cover it.
Mistake
Basic support includes a Technical Account Manager.
Correct
A TAM is only available with Premium support. Basic, Standard, and Enhanced do not include a dedicated TAM.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Support plans define how you interact with Google Cloud support (channels, response times, additional services like TAM). SLAs are uptime guarantees for specific services (e.g., Compute Engine 99.95%). You can have Basic support and still receive SLA credits if a service fails to meet its uptime guarantee. However, filing an SLA claim requires opening a support case, which is easier with higher-tier plans.
Only Premium support includes a dedicated Technical Account Manager (TAM). The TAM provides proactive guidance, quarterly business reviews, and helps with incident response. Enhanced support includes an assigned support engineer but no TAM. Basic and Standard have no dedicated engineer.
You must open a support case within 30 days of the end of the billing month in which the SLA breach occurred. Provide details of the downtime, including timestamps and affected resources. Google will verify and issue credits (typically 10-50% of the monthly fee for the affected service). Credits are not automatic.
No. Basic support is web-only. You can only submit cases via the Google Cloud Console. Phone and chat are available starting from Standard support. For critical issues, Basic users must wait up to 8 hours for an initial response.
The Compute Engine SLA for a single instance is 99.95% uptime. This allows approximately 21.9 minutes of downtime per month. If uptime falls below 99.95%, you can request credits. For multi-zone deployments, the SLA is 99.99% (about 4.4 minutes of downtime per month).
No. Third-party software support (e.g., Apache, MySQL, Nginx) is only included in Enhanced and Premium tiers. Standard and Basic do not cover third-party software. If you need help with such software, you must upgrade to Enhanced or Premium.
Premium support pricing is custom and typically ranges from 1% to 4% of your total monthly Google Cloud spend. There is no published flat fee. It includes a TAM, two health reviews, training, and the fastest response times (5 minutes for P1).
You've just covered Google Cloud Support Plans and SLAs — now see how well it sticks with free GCDL practice questions. Full explanations included, no account needed.
Done with this chapter?