A compliance audit requires a complete record of which agent performed which action, in what order, and what the inputs and outputs were for a multi-agent deployment pipeline. What design practice enables this audit trail?
Select an answer to reveal the explanation.
Short Explanation and Infographic
A hospital's surgical record doesn't get filled in after the fact by memory — it's documented in real time, by procedure. Agent audit trails need the same discipline: structured, structured, structured — agent ID, action, inputs, outputs, timestamps — emitted automatically at every step.
Full explanation below image
Full Explanation
Compliance audit trails for multi-agent pipelines require structured, automated, per-step event emission — not manual documentation or inference from git history.
Audit trail event schema: ``json { "event_id": "uuid", "agent_id": "gh-copilot-deploy-agent-v2", "action": "create_pull_request", "timestamp": "2025-10-01T14:32:11Z", "inputs": {"branch": "feature/auth-fix", "base": "main"}, "outputs": {"pr_number": 142, "url": "..."}, "status": "success", "pipeline_run_id": "run-9823" } ``
Why B is correct: Structured event logging emitted automatically at each step provides the complete, immutable, machine-readable record compliance requires. Centralizing in a log store (e.g., GitHub Audit Log, SIEM, S3) enables querying and reporting.
Why A is wrong: Manual documentation after the fact is unreliable, incomplete, and does not scale. Developers may misremember or omit steps, and there is no guarantee of completeness.
Why C is wrong: GitHub Actions' built-in logs capture stdout/stderr but are not structured event logs. They do not automatically record agent ID, semantic action types, structured inputs/outputs, or the relationships between steps in the format compliance requires.
Why D is wrong: Git commit history shows what was committed, not what every agent action was. Many agent actions (API calls, file reads, decisions) leave no git trace. Quarterly reviews are also too infrequent for continuous compliance.