What should you implement to ensure PoE devices receive their correct power definitions when 802.1X is used on edge ports?

What should you implement to ensure PoE devices receive their correct power definitions when 802.1X is used on edge ports?

• A. Enable AAA to exempt LLDP/CDP information
• B. Globally enable the QoS trust setting for LLDP/CDP
• C. Create device profiles with the correct power definitions
• D. Implement a classifier policy with the correct power definitions

Answer: (C)

Allocating PoE power per device by using device profiles is the way to ensure each edge-port device gets the right power after 802.1X authentication or MAC-based identification. Device profiles let you define the exact PoE power requirements for different device types and automatically apply those settings when a device is connected (or authenticated). This means phones, cameras, and laptops can receive the appropriate wattage without guessing or relying on generic power levels, which is especially important when authentication might delay or alter how the device is identified on the port. The other options don’t directly address per-device PoE power allocation. Exempting LLDP/CDP info from AAA, or trusting LLDP/CDP for QoS, doesn’t configure PoE power. A classifier policy could influence some behaviors, but it isn’t the built-in mechanism specifically designed to map devices to their PoE power definitions. Therefore, using device profiles with the correct power definitions is the best approach.

Allocating PoE power per device by using device profiles is the way to ensure each edge-port device gets the right power after 802.1X authentication or MAC-based identification. Device profiles let you define the exact PoE power requirements for different device types and automatically apply those settings when a device is connected (or authenticated). This means phones, cameras, and laptops can receive the appropriate wattage without guessing or relying on generic power levels, which is especially important when authentication might delay or alter how the device is identified on the port.

The other options don’t directly address per-device PoE power allocation. Exempting LLDP/CDP info from AAA, or trusting LLDP/CDP for QoS, doesn’t configure PoE power. A classifier policy could influence some behaviors, but it isn’t the built-in mechanism specifically designed to map devices to their PoE power definitions. Therefore, using device profiles with the correct power definitions is the best approach.