Which feature of a deployment pipeline primarily supports compliance and auditing?

Which feature of a deployment pipeline primarily supports compliance and auditing?

• A. Auditable logs, access controls, and versioned artifacts
• B. Speed
• C. Automated testing only
• D. UI aesthetics

Answer: (B)

Maintaining traceability and governance is what supports compliance and auditing in a deployment pipeline. Auditable logs record who did what and when, creating an immutable history of changes and deployments. Access controls restrict who can approve, deploy, or modify artifacts, enforcing accountability and separation of duties. Versioned artifacts capture the exact components and their versions used in a release, allowing you to reproduce and inspect a specific deployment. Together, these features provide the evidence and control needed for audits, change management, and regulatory reporting. Speed helps with release velocity but doesn’t provide the necessary audit trail. Automated testing improves quality, yet it doesn’t establish who made changes or when. UI aesthetics don’t influence compliance or traceability.

Maintaining traceability and governance is what supports compliance and auditing in a deployment pipeline. Auditable logs record who did what and when, creating an immutable history of changes and deployments. Access controls restrict who can approve, deploy, or modify artifacts, enforcing accountability and separation of duties. Versioned artifacts capture the exact components and their versions used in a release, allowing you to reproduce and inspect a specific deployment. Together, these features provide the evidence and control needed for audits, change management, and regulatory reporting.

Speed helps with release velocity but doesn’t provide the necessary audit trail. Automated testing improves quality, yet it doesn’t establish who made changes or when. UI aesthetics don’t influence compliance or traceability.