What is the purpose of audit logging in deployments?

What is the purpose of audit logging in deployments?

• A. Collect performance metrics for dashboards only.
• B. Store secrets in plaintext for quick auditing.
• C. Log only failed deployments without context.
• D. Record who/what changed, when, and why; supports compliance and incident analysis.

Answer: (D)

Audit logging in deployments provides a traceable record of all changes to the deployment environment, capturing who initiated the change, what was changed, when it happened, and often why it was done. This creates accountability and a foundation for forensic analysis, making it possible to understand incidents, roll back or reproduce decisions, and demonstrate compliance with security and governance requirements. The option that best fits this purpose describes exactly these elements—recording who/what changed, when, and why, and supporting compliance and incident analysis. The other ideas miss the core point: collecting performance metrics is about monitoring system health rather than documenting deployment actions; storing secrets in plaintext is insecure and not an auditing practice; logging only failed deployments without context leaves you with an incomplete, unusable trail.

Audit logging in deployments provides a traceable record of all changes to the deployment environment, capturing who initiated the change, what was changed, when it happened, and often why it was done. This creates accountability and a foundation for forensic analysis, making it possible to understand incidents, roll back or reproduce decisions, and demonstrate compliance with security and governance requirements. The option that best fits this purpose describes exactly these elements—recording who/what changed, when, and why, and supporting compliance and incident analysis. The other ideas miss the core point: collecting performance metrics is about monitoring system health rather than documenting deployment actions; storing secrets in plaintext is insecure and not an auditing practice; logging only failed deployments without context leaves you with an incomplete, unusable trail.