Which two actions do you perform when connecting a FEX to a parent switch? (Choose two.)

FEX chassis IDs are typically automatically assigned or derived from the interface it connects to on the parent switch, or pre-defined in the configuration, but not an action you explicitly 'assign' to the FEX itself.

When connecting a FEX in a dual-homed topology for high availability, a vPC (Virtual PortChannel) is typically configured on the parent Cisco Nexus switches. This allows the FEX uplinks to be aggregated into a single logical PortChannel across both parent switches, providing redundancy and active-active forwarding.

FEX devices are zero-touch managed; they receive their configuration directly from the parent Nexus switch upon connection, meaning no pre-configuration on the FEX itself is required.

The FEX serial number is generally discovered automatically by the parent switch or used for licensing purposes, but it is not a manual configuration step required for connecting the FEX.

After physically connecting a FEX to the parent switch, the specific interface(s) on the parent switch must be explicitly configured and associated with the FEX using commands like `fex associate` or `interface fex-ethernet`, defining the FEX ID and its connection.