A platform team is deploying agents across three different workflows: (1) auto-formatting code on every commit, (2) proposing architectural refactors for legacy services, and (3) rotating API credentials on a weekly schedule. Which autonomy configuration is MOST appropriate across all three workflows?
Select an answer to reveal the explanation.
Short Explanation and Infographic
You wouldn't require a surgeon to get approval before washing their hands, but you would before performing a procedure. Autonomy should match the risk and reversibility of the action — not be applied uniformly. Formatting is low-risk and reversible, so full autonomy makes sense. Architectural decisions need human judgment. Credential rotation is procedural but security-sensitive, so a supervised-but-scheduled pattern with audit logging fits best.
Full explanation below image
Full Explanation
Tuning agent autonomy is about matching the level of human oversight to the risk profile of each task, considering reversibility, judgment requirements, security sensitivity, and blast radius of errors.
Option C is correct. It demonstrates risk-calibrated autonomy:
- Auto-formatting: Fully autonomous. Code formatting follows deterministic rules (e.g., Prettier, Black), changes are immediately visible in diffs, easily reverted, and low-consequence. Human review here creates friction without adding safety value.
- Architectural refactors: Human-in-the-loop with plan review. These changes affect system design, may introduce breaking changes across service boundaries, and require judgment about trade-offs that extend beyond the agent's context window. A plan artifact reviewed by a human architect before execution is the appropriate pattern.
- Credential rotation: Supervised-but-scheduled. This is a well-defined procedure (generate new secret, update secret manager, deprecate old key, verify) but is security-sensitive. A human should not approve each individual rotation (that defeats the purpose of automation), but the process should run on a schedule with audit logging, anomaly detection, and an override mechanism if the procedure deviates from the expected path.
Option A (all autonomous) is dangerous for workflows 2 and 3. Architectural refactors made autonomously without human review can introduce systemic issues. Credential rotation with full autonomy and no oversight removes the security monitoring layer.
Option B (all supervised) eliminates the efficiency gains that make agents valuable for routine tasks like formatting. Requiring human approval for every Prettier run is operationally untenable.
Option D (trial-period approach) is not a principled autonomy model — it assumes that absence of reported incidents equals absence of risk, which is not valid. Undiscovered errors in architectural refactors may surface weeks later. The 30-day window is arbitrary and the batch promotion ignores per-workflow risk differences.
The exam objective is: 'Plan and implement the degree of agent autonomy, including guardrails.' The principle is risk-calibrated autonomy, not uniform autonomy.