Study guide
8.5 VCF Operations for Networks: Flow Analytics, Path Troubleshooting & Micro-Segmentation Planning
VMware Certified Professional - VMware Cloud Foundation Administrator VCP-VCF 2V0-17.25
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Private Cloud Vision & Architecture
1.1 Private Cloud Principles & The Modern Cloud Operating Model 1.2 VMware Cloud Foundation Architecture & Full-Stack Value Proposition 1.3 Private Cloud Use Cases, Service Models & Workload Strategy
2 Chapter 2: VMware Compute Fundamentals
2.1 ESXi Host & vCenter Architecture and Deployment 2.2 vSphere Cluster Design, High Availability (HA), and DRS 2.3 Virtual Machine Deployment, Advanced Hardware, & Management 2.4 Managing Virtual Machines Through vCenter: Day-2 Operations
3 Chapter 3: VMware Storage Fundamentals
3.1 vSphere Core Storage Architecture: VMFS, NFS, & vVols 3.2 vSAN Architecture: Express Storage Architecture (ESA) vs. Original Storage Architecture (OSA) 3.3 vSAN Cluster Deployment, Storage Pools, & Disk Configurations 3.4 Storage Policy-Based Management (SPBM), Fault Tolerance, & Space Efficiency 3.5 vSAN Resilience & Data Availability: FTT, Fault Domains, and Stretched Clusters 3.6 vSAN Space Efficiency: Compression, Deduplication, TRIM/UNMAP & Reclamation
4 Chapter 4: VMware Network Fundamentals
4.1 VCF Network Architecture & NSX Core Components 4.2 NSX Virtual Network Fabrics, Transport Nodes, & Geneve Overlays 4.3 Edge Clusters, Tier-0/Tier-1 Gateway Routing, & Uplink Connectivity 4.4 NSX Distributed Firewall (DFW) & Distributed Network Services 4.5 VCF 9.0 Virtual Private Clouds (VPCs) & Transit Gateway Connectivity
5 Chapter 5: VCF Deploy and Configure
5.1 VCF Deployment Models: Standard vs. Consolidated & Prerequisites 5.2 VCF Installer Bring-Up & Management Domain Deployment 5.3 VI Workload Domain Deployment, Commissioning Hosts, & Storage Attachment 5.4 vSphere Supervisor Configuration & vSphere Kubernetes Service (VKS) Integration 5.5 VCF Deployment Components & Additional Required Infrastructure 5.6 Deploying & Configuring the VCF Network Gateway 5.7 VCF Networking Deployment: NSX Instances, Transport Fabric & Edge Clusters 5.8 Workload Domain Storage: Principal vs. Supplemental Storage
6 Chapter 6: VCF Manage & Lifecycle Operations
6.1 VCF Fleet Management & Existing vCenter Import Workflows 6.2 Identity Federation, VCF Identity Broker, & RBAC 6.3 Certificate & Password Lifecycle Management in VCF Operations 6.4 Lifecycle Management (LCM), Upgrade Bundles, & Drift Remediation 6.5 License Management in VMware Cloud Foundation
7 Chapter 7: VCF Operations: Architecture, Metrics & Health Diagnostics
7.1 VCF Operations Architecture, Cluster Nodes, & Deployment Options 7.2 Metrics, Properties, Symptom Definitions, & Alerting Mechanics 7.3 Health Diagnostics, Troubleshooting Workflows, & Operational Policies
8 Chapter 8: VCF Operations: Monitoring, Logs & Compliance
8.1 Dashboards, Views, & Management Reporting in VCF Operations 8.2 Storage, Network, and Workload Application Monitoring 8.3 Log Analytics & Troubleshooting with VCF Operations for Logs 8.4 Security Compliance Benchmarks, Hardening, & Configuration Drift 8.5 VCF Operations for Networks: Flow Analytics, Path Troubleshooting & Micro-Segmentation Planning
9 Chapter 9: VCF Consume & Automate: Architecture, Tenancy & Networking
9.1 VCF Automation Architecture, Services, & Automation Use Cases 9.2 Regions, Cloud Zones, Projects, & Multi-Org Tenancy 9.3 Provider Networking, Org Networks, & Content Library Integration
10 Chapter 10: VCF Consume & Automate: Templates, Extensibility & Governance
10.1 Cloud Templates (Blueprints), Schema, & Infrastructure as Code 10.2 Extensibility: Action-Based Extensibility (ABX) & Orchestrator Workflows 10.3 Governance Policies: Approvals, Leases, Resource Quotas, & Day-2 Actions 10.4 Supervisor-Based Services, vSphere Kubernetes Service (VKS), & Modern App Consumption
8.5 VCF Operations for Networks: Flow Analytics, Path Troubleshooting & Micro-Segmentation Planning
Key Takeaways Explain This Topic AI
VCF Operations for Networks is the product formerly branded vRealize Network Insight and then VMware Aria Operations for Networks; the blueprint refers to it as VCF Network Operations.
Its defining capability is visibility across virtual and physical networks together, which distinguishes it from VCF Operations, whose network view stops at the virtual layer.
Flow-based analytics accelerate micro-segmentation planning by revealing which workloads actually communicate, so distributed firewall rules are derived from observed traffic rather than guessed.
The deployment model is a platform appliance for analytics and storage plus one or more collector appliances that gather data from vCenter, NSX, physical switches, routers, and firewalls.
The two products integrate bidirectionally: VCF Operations for Networks alerts surface in VCF Operations, and network information from VCF Operations for Networks is visible there as well.
Last updated: September 2026
8.5 VCF Operations for Networks: Flow Analytics, Path Troubleshooting & Micro-Segmentation Planning
Exam Focus: Two blueprint objectives name this product directly — "identify the use case for VCF Network Operations and VCF Operations (Logs)" and "monitor networks using VCF Network Operations". It is a separate product from VCF Operations , and confusing the two is the central trap in this topic.
Naming: Three Products, One Lineage
This product has been renamed twice, and study material exists under every name:
- Era Name
- vRealize era vRealize Network Insight (vRNI)
- Aria era VMware Aria Operations for Networks
- VCF 9.0 VCF Operations for Networks
The exam objective wording uses "VCF Network Operations" . All four labels describe the same technology. It is listed in the exam guide's minimally qualified candidate component set alongside VCF Operations, VCF Operations for Logs, and VCF Operations HCX — Broadcom expects you to know they are distinct.
The Distinction That Matters: Three Operations Products
Product Answers the question Primary data
VCF Operations "Is my infrastructure healthy, and will it have capacity?" Metrics and properties from vCenter, vSAN, NSX, hosts
VCF Operations for Logs "What did the components say happened?" Syslog event streams
VCF Operations for Networks "What is actually talking to what, over which path?" Network flows plus virtual and physical topology
The discriminator is flows and physical topology . VCF Operations monitors NSX objects and reports their health; it does not assemble an end-to-end path across physical switches, nor does it build a conversation map from observed traffic. That is what VCF Operations for Networks exists to do.
What It Delivers
Broadcom describes VCF Operations for Networks as delivering intelligent operations for software-defined networking and security , helping build an optimised, highly available, and secure network infrastructure across multi-cloud environments. Four capabilities carry the exam weight:
1. Micro-Segmentation Planning
This is the flagship use case. The product accelerates micro-segmentation planning and deployment by observing real traffic and building a map of which workloads communicate, on which ports, and in which direction.
The operational value is concrete: writing distributed firewall policy without this data means guessing an application's dependencies, and a wrong guess in a default-deny model breaks production. Flow analysis converts that guess into evidence, which is why micro-segmentation projects are commonly gated on a flow-collection period before any rule is enforced.
2. Visibility Across Virtual and Physical Networks
The product enables visibility across virtual and physical networks . A path from one VM to another may traverse a virtual segment, a distributed router, a TEP, a physical leaf and spine, another TEP, and a second host. Tools that see only the virtual half cannot tell you where in that chain a problem lies.
3. Managing and Scaling NSX
It provides operational views to manage and scale NSX deployments , surfacing configuration and scale characteristics that are difficult to assess from the NSX UI alone.
4. Reducing Application Migration Risk
Network visibility and analytics minimise risk during application migration . Knowing an application's true dependency set before it moves prevents the classic failure where a migrated tier can no longer reach a dependency nobody documented.
Coverage extends beyond NSX to vCenter, VMware Cloud on AWS, VMware SD-WAN by VeloCloud, and Kubernetes deployments.
Deployment Model: Platform and Collector
The product deploys as two appliance roles:
Role Responsibility
Platform Analytics, data storage, and the user interface. Deployable as a cluster for scale and availability.
Collector (proxy) Gathers data from configured data sources and forwards it to the platform.
Collectors are placed close to the infrastructure they observe, which is what allows a single deployment to cover multiple sites without exposing every device to a central appliance.
Data Sources
A data source is any system the collector polls or receives from:
vCenter for inventory and virtual machine context.
NSX for logical topology, segments, gateways, and firewall rules.
Physical switches and routers for the underlay path.
Firewalls and load balancers for policy context.
Flow data such as NetFlow and IPFIX exported by physical and virtual devices.
Without flow data configured, the product still maps topology but cannot answer the conversation questions that justify deploying it.
Integration with VCF Operations
The two products are designed to be used together rather than chosen between. With VCF Operations you can see the VCF Operations for Networks alerts in VCF Operations, and also see network information in VCF Operations sourced from VCF Operations for Networks.
This is a bidirectional integration, and it is the reason an operator working a health alert in VCF Operations can pivot into network context without changing tools.
Exam Watch: Key Scenarios and Candidate Traps
Important
Match the question to the product. "Which workloads communicate with this database, and on which ports?" is VCF Operations for Networks. "Is this cluster running out of capacity?" is VCF Operations. "What did NSX Manager log at 02:14?" is VCF Operations for Logs.
Warning
Micro-segmentation planning is not a VCF Operations capability. VCF Operations reports on NSX object health and can alert on it, but it does not build the flow-based application dependency evidence that firewall rule design requires.
Tip
Physical plus virtual is the giveaway phrase. Any scenario that requires tracing a path across both the overlay and the physical underlay points at VCF Operations for Networks.