A production city website fails at 2 a.m. and leaders need 24/7 phone access plus a designated Technical Account Manager-style relationship. Which Support direction matches that criticality?
Select an answer to reveal the explanation.
Short Explanation
Broken production site at 2 a.m. needs more than Basic or Developer Support. Step up to an Enterprise-family plan for 24/7 severity handling and TAM-style help.
Full Explanation
When a production city website fails at 2 a.m. and leaders need 24/7 phone access plus a designated Technical Account Manager-style relationship, an Enterprise-family Support plan (Enterprise or Enterprise On-Ramp) matches that criticality. Enterprise-family plans provide higher-severity 24/7 response characteristics and TAM-style engagement unsuitable for production break-fix left on Basic or Developer tiers.
Basic Support provides no technical case support for production break-fix in the way production cities require. Developer Support targets non-production experimentation and business-hours-oriented guidance, not 2 a.m. production severity with TAM engagement. Relying solely on public documentation without a Support plan upgrade leaves the city without contractual production incident pathways. Under-scoped plans are the distractors.
Exam caveat: Basic < Developer < Business < Enterprise On-Ramp/Enterprise in capability and cost. Production 24/7 + TAM-style needs point to Enterprise family; many production workloads land on Business as a minimum—but this stem explicitly asks for TAM-style and 24/7 severity handling characteristic of Enterprise family.
Operational check: review current Support plan before go-live of critical civic sites, escalate plan prior to election or tax deadlines, store TAM/contact runbooks in the incident wiki, open a high-severity case during drills to validate process, and ensure billing owners approve the Support subscription as part of production readiness.