Unified Assurance V6 – Admin Ed 1 — Lesson 2: Discovery, Inventory, Polling, Events, Alarms, Enrichment, and Correlation

Learning Objectives

• Assess the components, roles, data, dependencies, and expected outcome for discovery, inventory, polling, events, alarms, enrichment, and correlation.
• Operate the required workflow with explicit checkpoints and exception handling.
• Resolve the result through discovery results, alarm flows and explain any residual risk.

Detailed Topics

• Discovery
• Inventory
• Polling
• Events
• Alarms
• Enrichment
• ownership, prerequisites, data, and acceptance criteria for discovery, inventory, polling, events, alarms, enrichment, and correlation
• security, control, integration, performance, recovery, and support implications

Instructor Demonstration

Demonstrate discovery, inventory, polling, events, alarms, enrichment, and correlation within a Unified Assurance platform administered for reliable discovery, event processing, service visibility, reporting, and controlled maintenance. Use representative data and capture discovery results, alarm flows so another practitioner can verify the result.

Hands-On Exercise

Complete a controlled Unified Assurance V6 – Admin Ed 1 activity focused on discovery, inventory, polling, events, alarms, enrichment, and correlation. Introduce a realistic case of missed discovery, isolate the cause, apply a reversible correction, and rerun the acceptance checks.

1. Record the requirement, environment, identities, dependencies, data, controls, and expected result.
2. Perform the workflow and capture course-specific evidence before and after each material change.
3. Test normal, boundary, failure, security, reconciliation, recovery, and operational conditions.
4. Document the root cause, correction, rollback, owner, support action, and next improvement priority.

Scenario Analysis

• Identify who owns the decision, configuration, approval, and production support.
• Estimate how missed discovery would affect users, data, service, or financial results.
• Define evidence for normal operation, a boundary condition, a failed case, and successful recovery.

Troubleshooting Guidance

When discovery, inventory, polling, events, alarms, enrichment, and correlation does not produce the expected result, confirm scope, effective dates, identities, data context, dependencies, and recent changes. Review the most relevant discovery results, alarm flows before editing configuration. Test one reversible hypothesis at a time, verify recovery, and confirm that the fix does not create missed discovery elsewhere.

Validation Checklist

• Prerequisites, ownership, data context, settings, and expected outcomes are documented.
• The result is reproducible and supported by discovery results, alarm flows.
• Security, controls, data quality, integration, performance, recovery, and support conditions are reviewed.
• Exceptions, corrective action, rollback, approvals, monitoring, and handover are recorded.

Lesson Outcome

Learners can apply Discovery, Inventory, Polling, Events, Alarms, Enrichment, and Correlation in a realistic Unified Assurance V6 – Admin Ed 1 situation and defend the result with course-specific evidence.