Which task is required to create steering rules on NSX-V Manager?

Question

Options

• ASelect Steering Rules > 3rd Party Firewalls > Palo Alto Networks and then populate the object
• BConfigure the rule in Panorama and push it to NSX-V Manager.
• CSelect Fabric > Access Policies > Quick Start and follow the prompts
• DAdd a network introspective service and select Redirect to Service under Action.

• A
  92% (22)
• B
  4% (1)
• C
  4% (1)

Explanation

Option A is correct because in NSX-V Manager, creating steering rules requires navigating to Steering Rules > 3rd Party Firewalls > Palo Alto Networks and populating the object - this is the actual workflow within the NSX-V Manager UI to define how traffic is steered to third-party security services.

Why the distractors are wrong:

• B is backwards - Panorama is Palo Alto's centralized management platform; policies are pushed from Panorama to firewalls, not to NSX-V Manager, and this isn't where steering rules are created.
• C describes an ACI (Application Centric Infrastructure) workflow path, not NSX-V; "Fabric > Access Policies > Quick Start" is Cisco terminology, not VMware NSX.
• D describes configuring a network introspection service with a redirect action - this is a related but separate step (service insertion), not the steering rule creation task itself.

Memory tip: Think of it as "Steer the traffic where you want it" - you go to Steering Rules first, then drill down to the specific firewall vendor (Palo Alto Networks). The path mirrors the logical flow: rule type → vendor → object configuration.

No community discussion yet for this question.