What does operational documentation capture?
It records what an organization operates, how systems connect, how routine tasks are performed, and how approved changes are made.
Study 3 Operational Documentation with 12 free online flashcards. Review key terms, definitions, and concepts with this interactive flashcard deck.
What does operational documentation capture?
It records what an organization operates, how systems connect, how routine tasks are performed, and how approved changes are made.
Who should be responsible for an important operational record?
Assign an owner responsible for its accuracy and review.
When is a system change operationally complete from a documentation perspective?
Update and check affected documentation as part of the change; the change is not operationally complete until this is done.
How should documentation detail vary with operational risk?
Match detail to operational risk: critical services may need detailed dependencies and recovery steps, while low-impact components may need only a concise inventory entry and support contact.
What makes a system inventory useful?
It identifies technology assets and their relationships, using unique identities and useful details such as role, owner, platform, dependencies, and lifecycle.
What role do people play in automated asset discovery?
Automated discovery can reveal unknown or changed assets, but people must resolve discrepancies and confirm ownership.
What is a configuration baseline?
A configuration baseline records an approved state for a system or component at a particular point in time.
How are configuration baselines used?
Compare the current state with the intended state and plan, assess, and verify changes. Preserve prior approved versions when needed for audit, troubleshooting, or recovery.
What does a logical network diagram show?
They show networks, segments, security boundaries, services, and permitted or important connections.
What does a service diagram explain?
They show how a service depends on elements such as applications, databases, identity, DNS, storage, external providers, and network paths.
What should a runbook specify for failed or unsuccessful steps?
It should state how to recognize success at important steps, what conditions require stopping, and how to roll back, recover, or escalate.
How should a runbook handle passwords and other secrets?
Do not include passwords or other secrets; direct operators to the approved secrets-management process.