Explanation
C: Segment. This is correct. A segment is a logical construct that represents a layer 2 broadcast domain and a layer 3 subnet in NSX. A segment can be used to group and connect virtual machines, containers, or bare metal hosts that belong to the same application or service. A segment can also be used as the scope of a distributed firewall rule, which means that the rule will apply to all the traffic that enters or exits the segment12 E: Group. This is correct. A group is a logical construct that represents a collection of objects in NSX, such as segments, segment ports, virtual machines, IP addresses, MAC addresses, tags, or security policies. A group can be used to define dynamic membership criteria based on various attributes or filters. A group can also be used as the scope of a distributed firewall rule, which means that the rule will apply to all the traffic that matches the group membership criteria32

Explanation
According to the VMware NSX 4.x Professional documents and tutorials, an NSX Manager is a standalone appliance that hosts the API services, the management plane, control plane, and policy management. The NSX Manager has three built-in roles: policy, manager, and controller2. The policy role handles the declarative configuration of the system and translates it into desired state for the manager role. The manager role receives and validates the configuration from the policy role and stores it in a distributed persistent database. The manager role also publishes the configuration to the central control plane. The controller role implements the central control plane that computes the network state based on the configuration and topology information3.
The other roles (master, cloud, and zookeeper) are not valid NSX Manager roles.

Explanation
According to the VMware NSX Documentation, Partner SVM is a valid insertion point for north-south network introspection. Network introspection is a feature that allows you to insert third-party network services into the data path of your traffic. Partner SVM stands for Partner Service Virtual Machine and is a virtual appliance that runs on an NSX Edge node and provides network services from a partner solution.
https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.2/administration/GUID-53D6C480-7AD3-4B23-92

Explanation
From the NSX UI the status of the VMware Identity Manager Integration must be "Enabled". According to the VMware NSX Documentation1, after configuring VMware Identity Manager integration, you can validate the functionality by checking the status of the integration in the NSX UI. The status should be "Enabled" if the integration is successful. The other options are either incorrect or not relevant.

Explanation
ccording to the VMware NSX Documentation, these are the three parameters that must match in order to establish an OSPF neighbor relationship with an upstream router on a tier-0 gateway:
MTU of the Uplink: The maximum transmission unit (MTU) of the uplink interface must match the MTU of the upstream router interface. Otherwise, OSPF packets may be fragmented or dropped, causing neighbor adjacency issues.
Subnet mask: The subnet mask of the uplink interface must match the subnet mask of the upstream router interface. Otherwise, OSPF packets may not reach the correct destination or be rejected by the upstream router.
Area ID: The area ID of the uplink interface must match the area ID of the upstream router interface.
Otherwise, OSPF packets may be ignored or discarded by the upstream router.