Strategy question

A coordinated misuse campaign is detected across more than one cloud partner. Design the cross-company incident-response model: detection-to-enforcement handoffs, severity levels, SLAs, and executive escalation. What would you standardize across AWS, Google, and Microsoft, and where would you deliberately allow partner-specific playbooks?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Tests designing an operational incident-response process across multiple external partner companies with different systems and escalation cultures.

Define what counts as a coordinated misuse campaign versus isolated incidents, since that classification drives the whole response.
Standardize severity levels and SLAs so a critical incident gets the same urgency regardless of which cloud surface found it.
Build detection-to-enforcement handoffs specifying who owns each step, since partners may lack authority to act on Anthropic's usage policy directly.
Define executive escalation triggers, for example any campaign touching multiple partners escalates automatically.
Decide what stays partner-specific, like the exact technical enforcement mechanism each platform supports.

Proposes a shared severity taxonomy and SLA clock, with a named example like a severity-one incident requiring a one-hour response.
Plans explicitly for partners disagreeing on severity, with a tiebreaker or joint-escalation path.
Keeps partner-specific playbooks for enforcement mechanics, since each partner's suspension tooling differs.
Includes a post-incident review step that updates the shared playbook across all partners.

Assuming all partners can execute the same enforcement action when their platforms differ.
Requiring unanimous partner agreement before any action, which is too slow for active harm.

Chapters of the AI PM course that teach what this question tests.