Deployment management information and technology
Domain 4: Information and technology
This domain tests the data and tools that make deployments traceable and repeatable. Expect questions on deployment records, CMDB accuracy, pipeline integration, and tool selection.
Core rules
- Key information: deployment records covering what, where, when, by whom, and result; deployment plans and schedules; CI and environment records; test evidence; rollback plans; approval references; and monitoring results.
- A deployment record should link to the change record, affected CIs, artifact version, pipeline run, and verification outcome. This supports audit, incident diagnosis, and continual improvement.
- Tooling includes version control, artifact repositories, CI/CD pipelines, configuration management and orchestration, environment management, monitoring, and ITSM workflow tools. Integration matters more than tool count.
- Data quality is a deployment control: stale CMDB entries, unknown environment differences, and untracked artifacts cause failed deployments. Secrets and access must be controlled, with separation of duties where required.
Worked example
A deployment fails after release. The team searches the deployment record, finds the pipeline run, artifact hash, target CIs, and approver. Monitoring shows configuration drift on one server. Because the CMDB links the CI to the environment, the team rolls back that node and corrects the drift. Without the record, diagnosis would rely on memory.
Traps
- Treating deployment records as optional paperwork.
- Trusting a CMDB that is not maintained.
- Using tools that do not integrate, creating manual handoffs.
- Overlooking artifact versioning and environment baselines.