CSI Change Management & Deployment Flashcards

What is the purpose of a 'deployment runbook'?

Answer: Providing step-by-step instructions for executing a deployment, including verification checks and rollback steps

A deployment runbook is a detailed operational guide that ensures deployments are executed consistently, with clear verification and rollback procedures.

In change management, 'impact analysis' is performed to:

Answer: Identify which systems, users, and processes will be affected by a proposed change

Impact analysis maps the downstream effects of a proposed change, helping the CAB evaluate risk and coordinate affected teams.

A 'maintenance window' for deploying integration changes is scheduled during off-peak hours primarily to:

Answer: Minimize user impact and provide time to resolve issues before business-critical hours

Off-peak maintenance windows reduce the blast radius of deployment issues by limiting exposure to users during the highest-risk period.

Which change management metric measures the percentage of changes that cause unplanned outages or incidents?

Answer: Change failure rate (also called change-induced incident rate)

Change failure rate tracks how often changes introduce incidents, serving as a key DORA metric for deployment and change management maturity.

When decommissioning a legacy system during an integration project, the MOST critical first step is to:

Answer: Confirm all data has been migrated and validated in the new system before retiring the old one

Data validation in the target system must be confirmed before decommissioning to prevent permanent data loss.

A system integrator uses 'smoke testing' immediately after a production deployment to:

Answer: Quickly verify that critical integration paths are working before declaring the deployment successful

Smoke testing runs a minimal set of critical checks immediately after deployment to confirm the system is functional before deeper testing or full traffic is enabled.