Parks needs a reusable Layer-4 object for the municipal recreation portal on TCP 8443 so Distributed Firewall rules can name the service instead of typing the port each time. Where is that object created?
Select an answer to reveal the explanation.
Short Explanation
A named service is a city form number: fill it out once in Inventory → Services, then every DFW rule can say “recreation portal” instead of scribbling 8443 again. Load-balancer pools, uplink profiles, and vSphere shaping are not that form.
Full Explanation
NSX Inventory Services are reusable L4 (and other) objects that Distributed Firewall and related policies can reference by name. Load-balancer pools describe backend members, uplink profiles describe host-switch teaming, and vSphere traffic shaping is a port-group QoS setting. None of those replace an Inventory service for TCP 8443 in civic DFW rules.