OCI 1Z0-1067-25 Glossary: Key Terms
March 31, 2026
OCI 1Z0-1067-25 glossary of monitoring, backups, patching, automation, and recovery terms.
Use this glossary to clean up high-confusion OCI operations terms, then route misses back to the right support page.
High-value terms
- Alarm: The rule that fires when a monitored metric crosses a threshold.
- Audit trail: The history of control-plane actions recorded for review and investigation.
- Log group: The container used to organize logs in OCI Logging.
- Metric: A numeric operational signal collected over time.
- Notification: The message delivery path used when alarms or events need to alert someone or something.
- Resource Manager: OCI’s managed infrastructure-as-code orchestration service.
- Runbook: The documented operations procedure for handling a task or incident.
- Tagging discipline: The consistent labeling practice used for governance, cost tracking, and operations.
- Triage: The first-pass sorting step that decides what deserves attention first.
- Visibility: The ability to observe health, change, and failure signals clearly.
Common confusion pairs
- Metric vs log: Metrics summarize numeric behavior. Logs capture event detail and context.
- Alarm vs notification: An alarm decides when a threshold condition is met. A notification delivers the resulting message.
- Audit vs logging: Audit records control-plane actions. Logging captures broader service and application events.
- Automation vs manual fix: Automation makes repeatable operations safer. Manual fixes may be faster short term but are harder to govern.
- Troubleshooting vs remediation: Troubleshooting identifies cause. Remediation changes the environment to correct it.
Where to review next
- Weekly sequence and weak-spot planning: Study Plan
- Triage, alarm, and logging traps: Cheat Sheet
- Last-week questions: FAQ
- Canonical Oracle and OCI references: Resources
Revised on Sunday, May 10, 2026