Refer to the partial exhibit from an HPE Aruba Networking CX 8325: A new port 1/1/44 needs to be configured to connect to a 29301, which has the following configuration: Which configuration would be…

Question

Exhibit

Options

• Ainterface 1/1/44 no shutdown vlan trunk native 10 vlan trunk allowed 1,10,20,30,40,50,55,60 exit
• Binterface 1/1/44 enable vlan trunking vlan trunk native 10 vlan trunk allowed 1,10,20,30,40,50,55,60 exit
• Cinterface 1/1/44 enable vlan trunk native 10 vlan trunk allowed 1,10,20,30,40,50,55,60 exit
• Dinterface 1/1/44 vlan native 10 vlan trunk native 10 vlan trunk allowed 1,10,20,30,40,50,55,60 exit

• A
  74% (42)
• B
  4% (2)
• C
  7% (4)
• D
  16% (9)

Explanation

Option A is correct because HPE Aruba AOS-CX syntax uses no shutdown to activate an interface - not enable - and the vlan trunk native / vlan trunk allowed commands alone implicitly configure the port as a trunk without needing a separate vlan trunking declaration.

Option B fails on two counts: enable is not valid AOS-CX syntax for bringing up an interface, and vlan trunking is a non-existent command in AOS-CX - it's a distractor that mimics older or different vendor CLI patterns.

Option C is almost right structurally but still uses enable instead of no shutdown, which would leave the port administratively down and non-functional.

Option D mixes access-port syntax (vlan native 10) with trunk syntax (vlan trunk native 10), which is contradictory, and it omits no shutdown entirely, so the interface would stay down.

Memory tip: On AOS-CX, remember the pattern "no shutdown + vlan trunk" - if you see enable or vlan trunking on a CX switch config answer, treat it as a red flag. Think: "CX = no, not enable."

No community discussion yet for this question.