Free RCNI Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

The supportsave command on RUCKUS ICX devices is a comprehensive utility designed to streamline the collection and submission of diagnostic data for technical support cases. Its primary advantage over the show tech-support command is its ability to bundle all relevant information into a compressed file and upload it directly to the RUCKUS support FTP server. This is typically done by specifying a support case number, which automates a critical step in the troubleshooting workflow. The show tech-support command, in contrast, only displays information to the console, requiring the administrator to manually capture the output and transfer it.

A. Uses fewer CPU cycles during execution.

Both commands are resource-intensive as they gather extensive system data; supportsave may even use more CPU due to file compression and network transfer operations.

B. Allows the transfer of collected data to TFTP.

While supportsave does support TFTP, this is not its most unique advantage. The direct-to-RUCKUS upload is a more significant differentiator from show tech-support, whose output can be manually captured and sent via TFTP.

D. Generates automatically after a system crash.

The supportsave command is executed manually by an administrator. Automatic data collection after a system crash is handled by a separate crash dump or post-mortem debugging mechanism.

1. RUCKUS FastIron Command Reference Guide, 8.0.90:

Section: "supportsave" command description: "The supportsave command collects RAS log, OS log, and other critical system information for troubleshooting and saves the information to a file. You can then use the FTP, SCP, or TFTP option to transfer the file to a server. You can also upload the file to the RUCKUS support FTP site." This text explicitly states the capability to upload directly to the RUCKUS support site.

Syntax example: supportsave case-id is shown as a primary use case, confirming the direct integration with the RUCKUS support workflow. In contrast, the show tech-support command description in the same guide only mentions displaying information.

The RUCKUS ICX 7150-48P is one of two specific models in the ICX 7150 family that supports a software-configurable "fanless mode." When this mode is enabled via the Command Line Interface (CLI), the system fans are turned off, allowing the switch to operate silently. This feature is designed for noise-sensitive environments like classrooms or offices. Enabling this mode typically reduces the maximum supported ambient operating temperature and may limit the available Power over Ethernet (PoE) budget to prevent overheating.

A. ICX7150-48PF: This model has a higher PoE budget (740W) which generates more heat, requiring mandatory active fan cooling. It does not support the fanless mode command.

C. ICX7550-24P: The ICX 7550 is a higher-performance switch family. Its hardware design and thermal requirements necessitate active fan cooling and it does not support a fanless mode.

D. ICX7150-48ZP: This model features multigigabit ports and high-power PoE (PoH), both of which generate significant heat, making fanless operation impossible. It does not support fanless mode.

1. RUCKUS FastIron Campus Switch Configuration Guide, 8.0.95.

Section: "Enabling fanless mode"

Content: "The fanless-mode enable command is supported on the ICX 7150-48P and ICX 7150-24P devices only. When fanless mode is enabled, the system fans are turned off. The device can operate at a maximum ambient temperature of 35 degrees Celsius." This directly confirms that the ICX 7150-48P supports this feature.

2. RUCKUS ICX 7150 Switch Family Datasheet.

Section: "Table 2: RUCKUS ICX 7150 Switch Models"

Content: This table details the specifications for each model. It shows the ICX7150-48PF has a 740W PoE budget and the ICX7150-48ZP has 8x 2.5 Gbps ports with 802.3bt (90W) PoE. These higher power and performance characteristics necessitate the constant fan operation not found in the standard ICX7150-48P model.

The show cpu tasks command on a RUCKUS ICX switch provides a detailed, real-time breakdown of CPU utilization for each individual software task or process running on the device. When troubleshooting a high CPU alert, this command is essential as it allows an administrator to pinpoint the exact process consuming excessive CPU cycles. The output typically includes the task name, its status, priority, and the percentage of CPU it is currently using, which is the specific information needed to diagnose the cause of the high utilization.

A. show cpu histogram: This command displays a historical distribution of overall CPU load over time, not the real-time consumption by individual processes.

C. show cpu: This command provides a high-level summary of total CPU utilization over different time intervals (e.g., last second, last minute) but lacks per-process detail.

D. show process: This is not the correct or most specific command on RUCKUS ICX devices for viewing detailed CPU usage by process; show cpu tasks serves this function.

---

1. RUCKUS FastIron Command Reference Guide, 08.0.95

Reference for Correct Answer (B): In the chapter "Show Commands," the description for show cpu tasks states, "Displays CPU utilization for individual software tasks (processes) running on the device." This command's output table includes a "%CPU" column, directly addressing the question's need. (Part Number: 53-1005578-01, Page 1998)

Reference for Incorrect Answer (A): The description for show cpu histogram states, "Displays a histogram of CPU utilization over a period of time." (Part Number: 53-1005578-01, Page 1997)

Reference for Incorrect Answer (C): The description for show cpu states, "Displays the percentage of CPU utilization." The output shows overall utilization, not a process-level breakdown. (Part Number: 53-1005578-01, Page 1996)

2. RUCKUS FastIron Monitoring Configuration Guide, 08.0.90

Reference for Correct Answer (B): In the chapter "Monitoring System Resources," the section "Displaying CPU utilization for individual tasks" explicitly recommends using the show cpu tasks command to "display CPU utilization for individual software tasks (processes) running on the device." (Part Number: 53-1005262-01, Page 21)

On RUCKUS ICX devices, a Layer 3 (IP) address can be assigned to logical or virtual interfaces to enable routing and IP-based management.

Virtual Ethernet (VE): A VE is a logical Layer 3 interface that represents a specific VLAN, enabling inter-VLAN routing.

Loopback: A loopback is a virtual interface that is always active. It is commonly used for stable router identification in routing protocols (like OSPF or BGP) and for management access.

GRE tunnels: A Generic Routing Encapsulation (GRE) tunnel interface is a logical interface that encapsulates traffic over an IP network. The tunnel interface itself requires an IP address to establish the tunnel and route traffic through it.

A. Stack Interface: This is not a standard configurable Layer 3 interface. Management of a RUCKUS ICX stack is performed using an IP address assigned to a Virtual Ethernet or a dedicated management port.

B. VxLAN: VXLAN (Virtual Extensible LAN) is a Layer 2 overlay technology. While its tunnel endpoints (VTEPs) use Layer 3 addresses, the VXLAN segment (VNI) itself represents a Layer 2 domain.

C. Virtual LAN: A VLAN is a Layer 2 broadcast domain. To give it a Layer 3 presence for routing, you must create a corresponding Virtual Ethernet (VE) interface and assign the IP address to the VE.

1. Virtual Ethernet (VE): RUCKUS FastIron Layer 3 Routing Configuration Guide, 08.0.95 | Part Number: 53-1005930-01, Chapter 2: Configuring IP, Section: "Configuring a virtual routing interface", Page 33. "A virtual routing interface, also called a VE, is a logical Layer 3 interface that you can configure on a Layer 3 switch... You must assign an IP address to the virtual routing interface..."

2. Loopback: RUCKUS FastIron Layer 3 Routing Configuration Guide, 08.0.95 | Part Number: 53-1005930-01, Chapter 2: Configuring IP, Section: "Configuring a loopback interface", Page 37. "A loopback interface is a virtual interface that is always up... You can assign an IP address to a loopback interface."

3. GRE tunnels: RUCKUS FastIron Layer 3 Routing Configuration Guide, 08.0.95 | Part Number: 53-1005930-01, Chapter 10: Configuring Tunnels, Section: "Configuring a GRE tunnel", Page 218. The configuration example explicitly shows the ip address command being applied under the interface tunnel context.

4. VLAN vs. VE: RUCKUS FastIron Layer 2 Switching Configuration Guide, 08.0.95 | Part Number: 53-1005928-01, Chapter 3: Configuring VLANs, Page 43. This chapter describes VLANs as Layer 2 constructs. The Layer 3 configuration is handled by VE interfaces as documented in the Layer 3 guide.

5. Stack Management: RUCKUS FastIron Stacking Configuration Guide, 08.0.90 | Part Number: 53-1005561-01, Chapter 3: Stack Management, Section: "Stack management options", Page 37. This section details that stack management is achieved via the management port or an IP address on a VLAN (VE interface). It makes no mention of a configurable "stack-interface".

On the RUCKUS ICX 7550 platform, Layer 3 features are enabled through specific software licenses. The Virtual Router Redundancy Protocol - Extended (VRRP-E) is a fundamental Layer 3 high-availability feature. According to the RUCKUS FastIron software licensing model, VRRP-E is included in the Base Layer 3 license (L3-Base). This license is the minimum requirement to activate VRRP-E, along with other essential routing protocols like OSPFv2 and RIP. The Premium Layer 3 license also includes this feature, but it is not the minimum necessary license.

A. PoD (Ports on Demand) is a license used to activate additional physical network ports on the switch, not for enabling software features like routing protocols.

B. MACSec is a Layer 2 security feature license that enables hop-by-hop encryption and is unrelated to Layer 3 routing or redundancy protocols like VRRP-E.

D. L3-prem (Premium) is an advanced Layer 3 license that includes all Base features plus protocols like BGP and OSPFv3. While it enables VRRP-E, it is not the minimum required license.

1. RUCKUS FastIron Software Licensing Guide, 09.0.10, Page 16, Table 10: "ICX 7550 Feature Licenses". This table explicitly lists "VRRP/VRRP-E" as a feature enabled by the ICX7550-L3-BASE (Base Layer 3) license.

2. RUCKUS ICX 7550 Switch Datasheet, Page 4, "Software" section. The datasheet outlines that the ICX 7550 offers optional Layer 3 routing protocol support (OSPF, VRRP, PIM, BGP) with a software license upgrade, distinguishing between base and premium feature sets. The base set, which is sufficient for VRRP, is the first tier of this upgrade.

RUCKUS ICX devices reserve five specific VLAN IDs for system-level functions, making them unavailable for standard static VLAN configuration. These reserved VLANs are essential for advanced Layer 2 features. The reserved IDs are:

4091: Port-based VLANs

4092: Protocol-based VLANs

4093: IP-subnet-based VLANs

4094: MAC-based VLANs

4095: Reserved for system use (often for discarding frames)

This reservation ensures that these specialized VLAN functions operate without conflicting with user-configured VLANs.

A. 9: This is an incorrect count. The official documentation explicitly lists only five reserved VLAN IDs.

B. 7: This is an incorrect count and does not align with the number of VLANs reserved for system functions.

C. 3: This count is too low and omits some of the VLANs reserved for features like MAC-based or Port-based VLANs.

1. RUCKUS FastIron Layer 2 Switching Configuration Guide, 08.0.95

Reference: Chapter 1: Configuring VLANs, Section: "VLANs", Page 3.

Quote: "The following VLAN IDs are reserved for system use and cannot be used to create static VLANs: 4091, 4092, 4093, 4094, and 4095."

2. RUCKUS Campus Fabric Configuration Guide, 08.0.90

Reference: Chapter 2: Configuring VLANs, Section: "VLAN Overview", Page 21.

Quote: "VLANs 4091 through 4095 are reserved for internal use and cannot be configured." This statement corroborates the reservation of five specific VLAN IDs.

The provided image displays the output of a show spanning-tree command. The section "Root ID" contains information about the Spanning Tree Protocol (STP) root bridge for this instance. The "Priority" field under "Root ID" shows a value of 32768. This value is in decimal format. The question requires this priority to be expressed in hexadecimal. The decimal value 32768 converts to 8000 in hexadecimal (32768 = 8 16³). Therefore, the bridge priority of the root bridge in hexadecimal is 8000.

B. 0: This is incorrect. A hexadecimal value of 0 would correspond to a decimal priority of 0, but the output explicitly shows the priority is 32768.

C. 9c49: This is incorrect. This value corresponds to the first part of the MAC address (9c49.eb00.0000) listed under the "Bridge ID", not the priority value.

D. 20009: This is incorrect. This hexadecimal value corresponds to the decimal value 131081, which has no relevance to the priority shown in the command output.

1. RUCKUS FastIron Layer 2 Switching Configuration Guide, Software Release 08.0.95.

Section: "Displaying STP information" (Chapter 2: Spanning Tree Protocols)

Reference: This guide provides examples of the show spanning-tree command output. It confirms that the "Priority" field displays the decimal value of the bridge priority, which defaults to 32768. The guide states, "The bridge priority. The default is 32768." This confirms the value in the output is the standard decimal representation.

2. RUCKUS FastIron Command Reference, 08.0.95.

Section: show spanning-tree command description.

Reference: This document details the fields in the show spanning-tree output. The "Priority" field under "Root ID" is defined as the priority of the root bridge. The conversion from the displayed decimal value (32768) to hexadecimal (8000) is a standard numerical conversion required to answer the question.

In an 802.1D Spanning Tree Protocol (STP) domain, network-wide timers—specifically the Hello Time, Forward Delay, and Max Age—are determined and dictated by the root bridge. The root bridge embeds these timer values into the Bridge Protocol Data Units (BPDUs) it sends out. All other switches in the STP domain, including the legacy 802.1D switches, receive these BPDUs and adopt the timer values set by the root. To influence the convergence time for these legacy switches, the timers must be modified at their source, which is the root bridge, typically located at the network core in a Core/Aggregation/Edge topology.

A. the route-only port on the upstream gateway: "Route-only port" is not a standard STP term. Furthermore, modifying timers on any non-root device is ineffective as they are overridden by the root bridge's BPDUs.

B. on the two legacy 802.1D switches at the edge: These switches are not the root bridge. Any local timer configuration on them will be ignored and replaced by the values received in BPDUs from the root bridge.

C. on the Aggregation switches connected to the legacy edge switches: Although these switches form the boundary between RSTP and legacy STP, they are not the root bridge and will simply propagate the timer values received from the root.

1. RUCKUS FastIron Command Reference, 8.0.90 (fi-8090-commandref.pdf): In the chapter for Layer 2 Switching Commands, the descriptions for the spanning-tree forward-time, spanning-tree hello-time, and spanning-tree max-age commands explicitly state: "These parameters are significant only on the root bridge. The root bridge sends BPDUs containing these parameters to the other bridges in the network." (See pages related to Spanning Tree global configuration).

2. IEEE Std 802.1D-2004, "IEEE Standard for Local and Metropolitan Area Networks--Media Access Control (MAC) Bridges": Clause 8.4, "Bridge Protocol Data Units (BPDUs)," specifies that Configuration BPDUs carry the timer values (Message Age, Max Age, Hello Time, Forward Delay) and that these values are originated by the Root Bridge for the Spanning Tree. Non-root bridges use these values from the received BPDUs.

3. Kurose, J. F., & Ross, K. W. (2017). Computer Networking: A Top-Down Approach (7th ed.). Pearson. In the section on Link-Layer Switches, the operation of the Spanning Tree Protocol is described, clarifying that the root bridge is responsible for sending configuration messages that dictate the topology and its parameters, including timers, for the entire switched network.

The ipv6 unicast-routing command is the fundamental global configuration command required to enable the IPv6 protocol stack on a RUCKUS ICX device. This command activates the device's ability to process and forward IPv6 unicast packets between its configured interfaces, effectively turning it into an IPv6 router. Without this command, the device will not perform Layer 3 forwarding for IPv6 traffic, even if IPv6 addresses are configured on its interfaces. It is the prerequisite for all other IPv6 routing functions.

A. ipv6 dhcp6-server enable: This command enables the DHCPv6 server service on the device. It is a specific application-level feature and does not enable the core IPv6 routing functionality.

C. ipv6 multicast: This command specifically enables IPv6 multicast routing protocols like PIM-SM. It is a separate feature from unicast routing and requires unicast routing to be enabled first.

D. ipv6 nd proxy: This enables the Neighbor Discovery (ND) proxy feature, a specialized function for specific network designs. It does not enable the global IPv6 routing capability.

1. RUCKUS FastIron Layer 3 Routing Configuration Guide, 08.0.95

Page 439, Section: "Enabling IPv6 routing": "To enable IPv6 routing on a Layer 3 switch, enter the ipv6 unicast-routing command at the global CONFIGURATION level of the CLI. This command globally enables IPv6 routing."

2. RUCKUS FastIron Command Reference, 08.0.95

Page 1688, Command: ipv6 unicast-routing: "This command enables IPv6 routing on a Layer 3 switch... By default, IPv6 routing is disabled on the device. You must enable IPv6 routing before the device can forward IPv6 packets."

3. RUCKUS Campus Fabric Configuration Guide, 08.0.95

Page 411, Section: "Configuring IPv6": The guide details IPv6 configuration steps, starting with the prerequisite of enabling IPv6 routing globally using the ipv6 unicast-routing command before any other IPv6 routing features can be configured.

The ping command is an operational and diagnostic tool used to test network reachability. In the RUCKUS FastIron operating system, such commands are executed from the privileged EXEC mode, which is indicated by the # prompt. The other prompts shown, (config)# and (config-if-...)#, represent global and interface-specific configuration modes, respectively. While in these configuration modes, operational commands like ping can typically be run by prefixing them with the do command (e.g., do ping 1.1.1.1), they cannot be executed directly. The question asks at which prompt the command can be executed, implying direct execution.

A. ICX7150-C12 Router(config-if-mgmt-1)# is the management interface configuration mode. Operational commands cannot be executed directly from this prompt.

B. ICX7150-C12 Router(config)# is the global configuration mode. It is used for system-wide settings, not for executing operational commands directly.

D. ICX7150-C12 Router(config-if-e1000-1/1/1)# is a specific physical interface configuration mode. Operational commands cannot be executed directly from this prompt.

1. RUCKUS FastIron Command Reference, 08.0.95: The documentation for the ping command consistently shows its execution from the privileged EXEC mode. The command syntax examples are presented with the # prompt, such as ICX7150-24P Router# ping 10.20.30.40. This confirms the command's context. (See Chapter: "IP Application Commands", Section: "ping").

2. RUCKUS FastIron Administration Guide, 08.0.95: This guide describes the different Command Line Interface (CLI) modes. It explicitly states that privileged EXEC mode is used for "executing configuration and management commands," which includes diagnostics like ping. In contrast, it defines global configuration mode for making changes that affect the device as a whole. (See Chapter: "Getting Started with the CLI", Section: "CLI command modes").

Internet Group Management Protocol Version 2 (IGMPv2) introduced the explicit "Leave Group" message. This feature allows a multicast client to actively send a request to the local multicast router, signaling its intent to stop receiving traffic for a particular multicast group. Upon receiving this message, the router can initiate a query to see if any other members remain on the subnet. This makes the process of leaving a group significantly faster and more efficient compared to IGMPv1, which relies on a passive timeout mechanism where the router must wait to stop forwarding traffic.

B. IGMPv1: This version lacks an explicit "Leave Group" message. A host simply stops responding to membership queries, and the router only stops forwarding traffic after a timeout period expires.

C. PIM Dense: This is a multicast routing protocol that operates between routers to build distribution trees. It is not used by end-clients on the local subnet to manage group membership.

D. IGMP Snooping: This is a Layer 2 switch feature that optimizes multicast traffic delivery by listening to IGMP messages. It is not the protocol used by the client to send the leave request.

1. RUCKUS FastIron Layer 3 Routing Configuration Guide, 08.0.95, Chapter 25: Configuring IP Multicast, section "IGMPv2", page 628. The document states, "IGMPv2 adds a Leave Group message to the protocol. When a host wants to leave a multicast group, it sends a Leave Group message to the all-routers multicast group (224.0.0.2)."

2. IETF RFC 2236, "Internet Group Management Protocol, Version 2", November 1997, Section 1: Introduction. This RFC, which defines the protocol, explicitly states: "Version 2 of IGMP adds a 'leave group' message to allow a host to inform a router that it wishes to leave a multicast group..."

3. Kurose, J. F., & Ross, K. W. (2017). Computer Networking: A Top-Down Approach (7th ed.). Pearson. In Chapter 4, Section 4.7.2, the text explains the IGMP protocol, noting that IGMPv2 (and v3) added messages that allow a host to explicitly signal it is leaving a group, an improvement over IGMPv1's timeout-based approach.

The RUCKUS ICX 7150-C12P is a compact switch that supports Power over Ethernet Plus (PoE+), compliant with the IEEE 802.3at standard. This standard specifies a maximum power delivery of 30W per port from the Power Sourcing Equipment (PSE). The other listed models (ICX7650, ICX7550, and ICX7150-48ZP) all support higher power standards such as IEEE 802.3bt or Power over HDBaseT (PoH), which allow them to deliver up to 90W per port, thus exceeding the 30W limit.

A. ICX7650: This model supports Power over HDBaseT (PoH), which can deliver up to 90W per port, far exceeding the 30W maximum.

B. ICX7550: This switch series includes models that support the IEEE 802.3bt standard, enabling power delivery of up to 90W on dedicated ports.

C. ICX7150-48ZP: This specific model is a Z-series switch that supports IEEE 802.3bt (PoH), providing up to 90W per port to power high-power devices.

1. RUCKUS ICX 7150 Family Data Sheet. In the "RUCKUS ICX 7150 Switch Models" table, the ICX 7150-C12P is listed with "12× 10/100/1000 Mbps PoE+ ports". The ICX 7150-48ZP is listed with "16× 10/100/1000/2500 Mbps 802.3at/bt (PoH) ports". This document confirms the ICX7150-C12P is limited to PoE+ (30W) while the ICX7150-48ZP supports 802.3bt (up to 90W). (Document available via the official CommScope/RUCKUS website).

2. RUCKUS ICX 7650 Switch Data Sheet. Under "Product Highlights," it states, "Power over HDBaseT (PoH) up to 90 watts per port and IEEE 802.3bt ready, PoE/PoE+." This confirms its ability to exceed 30W per port. (Document available via the official CommScope/RUCKUS website).

3. RUCKUS ICX 7550 Switch Series Data Sheet. The "At a Glance" section specifies, "802.3bt (90W) PoE on dedicated ports to power next generation wireless APs and IoT devices." This confirms its capability to exceed 30W per port. (Document available via the official CommScope/RUCKUS website).

The access point requires the switch port to handle two traffic types: untagged management traffic on the default VLAN (VLAN 1) and 802.1Q tagged guest traffic on VLAN 10. On RUCKUS ICX switches, all ports are, by default, untagged members of VLAN 1. This default state already accommodates the AP's management traffic. The only required change is to add the guest traffic VLAN. The command vlan 10 tagged ethernet 1/1/10 adds port 1/1/10 as a tagged member of VLAN 10, allowing it to process the tagged guest traffic while retaining its default untagged membership in VLAN 1 for management.

A. This command incorrectly configures VLAN 10 for untagged traffic, but the AP will send guest traffic with a VLAN 10 tag.

B. This command removes the port's untagged membership from VLAN 1, which is the management VLAN. This would prevent the AP from communicating with the management network.

D. This command removes untagged membership from VLAN 10. It is an irrelevant action that does not configure the necessary tagged membership for the port.

1. RUCKUS FastIron Layer 2 Switching Configuration Guide, Release 08.0.95, Chapter 3: Configuring VLANs, Page 48, Section: "Default VLAN and default port configuration".

This section states: "By default, all ports on the device are members of the default VLAN (VLAN 1)." This confirms that the port is already correctly configured for the untagged management traffic without any explicit commands.

2. RUCKUS FastIron Layer 2 Switching Configuration Guide, Release 08.0.95, Chapter 3: Configuring VLANs, Page 51, Section: "Adding a port to a VLAN as a tagged member".

This section provides the exact syntax used in the correct answer: vlan followed by tagged ethernet . This command adds the port to the specified VLAN for handling 802.1Q tagged frames, which is the requirement for the guest SSID traffic.

3. RUCKUS FastIron Layer 2 Switching Configuration Guide, Release 08.0.95, Chapter 3: Configuring VLANs, Page 50, Section: "Removing a port from a VLAN".

This section explains the use of the no untagged ethernet command, confirming that its use in option B would remove the port from VLAN 1, thereby breaking management connectivity.

The Link Layer Discovery Protocol (LLDP) is a vendor-neutral protocol used by network devices to advertise their identity, capabilities, and neighbors on a LAN. The show lldp neighbors command on a RUCKUS ICX switch displays a summary of the information received from directly connected LLDP-enabled devices. This output specifically includes the "System Name" (hostname) of each neighboring device, making it the correct command to discover this information.

B. show chassis: This command displays hardware information about the local switch itself, such as its serial number, power supplies, and fan status, not information about attached devices.

C. ping: This is a Layer 3 utility used to test IP reachability to a known IP address or hostname. It does not discover the names of unknown attached devices.

D. show inline power: This command displays the Power over Ethernet (PoE) status for switch ports, including power allocation and consumption, not the system name of the connected device.

1. RUCKUS FastIron Command Reference Guide, 8.0.95:

Page 1519, "show lldp neighbors": This section describes the command and provides sample output. The output table explicitly includes a "System Name" column, which "Displays the system name of the neighbor device." This directly supports answer A.

Page 2011, "show chassis": This section details the command, stating it "displays information about the chassis, including the card cage type, serial number, and power supplies." This confirms the command is for the local device, making B incorrect.

Page 2067, "show inline power": This section describes the command's function to display "information about inline power." This confirms D is incorrect.

The IEEE 802.3bt standard, also known as PoE++ or 4PPoE, significantly increases the power available to end devices. It introduces two new types: Type 3 (up to 60W from the Power Sourcing Equipment - PSE) and Type 4 (up to 90W from the PSE). To manage these higher power levels, the standard extends the classification system defined in previous standards (802.3af/at). The 802.3bt standard defines power classes from 0 to 8. Class 8 is the highest, corresponding to Type 4 devices, and ensures a minimum of 71.3W of power is available at the Powered Device (PD).

B. Class 4 is the highest power class supported by the older IEEE 802.3at (PoE+) standard, not 802.3bt.

C. Class 1 is a valid, low-power class in all PoE standards but is not the highest class available.

D. 16 is not a valid power class defined by any of the IEEE 802.3 PoE standards.

---

1. Official Vendor Documentation (CommScope/RUCKUS):

CommScope. (2020). Power over Ethernet (PoE) in the Enterprise. White Paper (WP-113260-EN). In the table "PoE standards at a glance" on page 3, it clearly shows that IEEE 802.3bt supports Classes 0-8 and delivers up to 71W at the PD for Class 8.

2. Peer-reviewed Academic Publications / Standards Body:

IEEE Std 802.3-2018, IEEE Standard for Ethernet, Section 10, Clause 145. "Type 3 and Type 4 Class and Type discovery, and power control". Table 145-1, "PD power classification," explicitly lists power classes 1 through 8, with Class 8 having a PClassPD range of > 60W to 71.3W.

3. University Courseware / Reputable Institutions:

University of New Hampshire InterOperability Laboratory (UNH-IOL). PoE Classes, Types, and Topologies. This resource, from a leading PoE testing and certification body, includes a table titled "PoE Standards" which specifies that IEEE 802.3bt-2018 includes Classes 5, 6, 7, and 8, with Class 8 being the maximum.