A team cannot tell which pull requests an agent changed. What should they configure?
Why B is the answer
Traceability, so that agent actions are visible in commits and logs
Accountability needs a record of who or what acted. Agent work should be identifiable in standard artifacts.
In detail
- Traceability makes agent actions visible in commits and logs.
- Use a distinct identity for agent commits.
Use case
An illustrative scenario, not a real incident.
An auditor asks which pull requests an agent changed. Traceability in commits and logs answers it in minutes.
See it in different ways
sequenceDiagram participant D as Developer participant A as Cloud agent participant P as Another reviewer D->>A: Requests a pull request A->>P: Draft pull request P->>P: Approve and run workflows P->>A: Review and merge
sequenceDiagram participant P0 as Agent participant P1 as Commits and logs participant P2 as Auditor P0->>P1: Records each action P2-->>P1: Query the trail P1->>P2: Who changed what
Key point: Make agent actions visible.
Why the other options are wrong
- A. A rule that agents may only work during normal office hours
- Working hours say nothing about which changes an agent made.
- C. A longer branch name that lists every file changed in the branch
- Branch names cannot reliably record this.
- D. A larger runner, so that the agent can finish in less time overall
- Speed does not show who did what.