VMware vRealize Network Insight: Install, Configure, Manage [V6.1] — Lesson 3: Search, dashboards, applications, tiers, flows, path analysis, intent, micro-segmentation planning, firewall recommendations, pinboards, alerts, and reports

Learning Objectives

• Break down the prerequisites, components, roles, and decision points involved in Search, dashboards, applications, tiers, flows, path analysis, intent, micro-segmentation planning, firewall recommendations, pinboards, alerts, and reports.
• Complete a controlled activity for Search, dashboards, applications, tiers, flows, path analysis, intent, micro-segmentation planning, firewall recommendations, pinboards, alerts, and reports and capture application dependency map and recommended-policy review.
• Challenge the result with an automatically grouped application combining unrelated workloads that share one port, then justify the corrective action.

Detailed Topics

• Search
• Dashboards
• Applications
• Tiers
• Flows
• Path analysis
• Intent
• Micro-segmentation planning
• Firewall recommendations
• Pinboards
• Alerts
• And reports
• Decision ownership, prerequisites, and acceptance evidence for Search, dashboards, applications, tiers, flows, path analysis, intent, micro-segmentation planning, firewall recommendations, pinboards, alerts, and reports
• Relevant access, security, capacity, dependency, performance, recovery, and support considerations

Instructor Demonstration

The demonstration traces Search, dashboards, applications, tiers, flows, path analysis, intent, micro-segmentation planning, firewall recommendations, pinboards, alerts, and reports from requirement through execution and review. Learners see where evidence should be collected, how application dependency map and recommended-policy review supports validation, and which warning signs require investigation.

Hands-On Exercise

Work through a role-based scenario involving Search, dashboards, applications, tiers, flows, path analysis, intent, micro-segmentation planning, firewall recommendations, pinboards, alerts, and reports. Validate the expected path, test “an automatically grouped application combining unrelated workloads that share one port,” choose the safest corrective action, and capture the reasoning and outcome in application dependency map and recommended-policy review.

1. Record the starting state, assumptions, identities, topology, and expected outcome.
2. Execute the planned workflow and collect evidence at each material checkpoint.
3. Test one valid path, one boundary condition, and the stated failure scenario.
4. Document the correction, retest result, rollback option, and follow-up owner.

Scenario Analysis

• Clarify the service trigger, affected components and roles, prerequisites, and acceptable result for Search, dashboards, applications, tiers, flows, path analysis, intent, micro-segmentation planning, firewall recommendations, pinboards, alerts, and reports.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how application dependency map and recommended-policy review should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

When Search, dashboards, applications, tiers, flows, path analysis, intent, micro-segmentation planning, firewall recommendations, pinboards, alerts, and reports produces an unexpected result, reproduce the issue with the same scope, identity, workload, and time context. Inspect application dependency map and recommended-policy review, test whether “an automatically grouped application combining unrelated workloads that share one port” explains the evidence, apply the smallest reversible correction, and retest an unaffected path for regression.

Validation Checklist

• Configuration and source state used for Search, dashboards, applications, tiers, flows, path analysis, intent, micro-segmentation planning, firewall recommendations, pinboards, alerts, and reports are versioned or otherwise traceable.
• Application dependency map and recommended-policy review shows both baseline and accepted result.
• Security, performance, dependency, and resilience side effects are considered where relevant.
• Recovery steps and handover notes are usable by an operations practitioner.

Lesson Outcome

Learners can apply Search, dashboards, applications, tiers, flows, path analysis, intent, micro-segmentation planning, firewall recommendations, pinboards, alerts, and reports, explain the decisions made, and defend the result with application dependency map and recommended-policy review.