4 Configuration Management Free Online FlashCards

What is the purpose of configuration management?

It keeps systems consistent with approved requirements and preserves a traceable history of changes.

What kinds of items can configuration management control?

They can include servers, operating systems, applications, network devices, software, and their documentation.

What is a configuration baseline?

It is a documented, formally approved description of a system or component at a particular point in time.

When should a baseline be updated, and what happens to earlier versions?

Update it when approved changes alter the system, and retain prior versions for reference and audit.

Which factors should a change impact and risk assessment consider?

Assess security, availability, compatibility, and dependencies.

What documentation and review does an urgent change still require?

Urgent changes may use an expedited process, but they should still be documented and reviewed afterward.

What information should a configuration version history make clear?

Each change should be attributable and explain what changed and why.

How does `git revert` undo a shared change?

`git revert` creates a new commit that reverses an earlier one, preserving the history of both changes.

What makes a configuration operation idempotent?

Running it again should leave the system in the same desired state rather than repeatedly introducing changes.

What do Ansible check mode and diff mode help verify?

Ansible check mode simulates supported changes, while diff mode can show before-and-after differences. Neither replaces testing or approval.

What is configuration drift?

Configuration drift is a difference between a live system and its approved baseline.

What might explain a detected configuration difference?

It may be unauthorized, an approved change not yet recorded, or an operational exception.