View Full HP HPE6-A85 Exam Dumps and Practice Test Dumps.

Question 361. What is LLDP-MED designed for?

1. OSPF routing
2. Media endpoint discovery
3. DHCP relay
4. VSF stacking

Correct Answer: 2. Media endpoint discovery

Explanation:

LLDP-MED extends standard LLDP to improve interoperability between network infrastructure and media endpoint devices such as IP phones. It can advertise information relevant to voice deployments, including network policy, capabilities, location, and PoE-related details. On AOS-CX, LLDP-MED support is enabled through interface-level LLDP configuration. The feature is useful because compatible endpoints can automatically learn network characteristics instead of requiring every setting to be entered manually. LLDP-MED is unrelated to OSPF routing, DHCP relay, or VSF stack formation.

Question 362. What does the LLDP-MED network-policy TLV advertise?

1. OSPF cost
2. Switch firmware
3. NTP servers
4. Voice VLAN and QoS information

Correct Answer: 4. Voice VLAN and QoS information

Explanation:

The LLDP-MED Network Policy TLV can advertise information needed by voice endpoints, including the VLAN ID and QoS values such as IEEE 802.1p priority and DSCP. This helps an IP phone learn how voice traffic should be classified and which VLAN it should use. AOS-CX sends this network-policy TLV when a suitable voice VLAN policy is configured. This reduces manual phone configuration and helps maintain consistent voice segmentation and QoS treatment across access ports.

Question 363. Is LLDP enabled by default?

1. Yes
2. No
3. Only on trunks
4. Only on routed ports

Correct Answer: 1. Yes

Explanation:

HPE documents LLDP as enabled by default on active AOS-CX interfaces. By default, the LLDP agent also transmits and receives LLDP information on interfaces unless those behaviors are specifically disabled. This makes neighbor discovery available without requiring administrators to enable the protocol individually on every active port. LLDP is useful for discovering connected switches, phones, APs, and other compatible devices. Administrators can still customize transmission, reception, advertised TLVs, timers, and LLDP-MED behavior where required.

Question 364. Which command stops LLDP transmission?

1. no lldp
2. lldp disable-rx
3. no lldp transmit
4. shutdown lldp

Correct Answer: 3. no lldp transmit

Explanation:

The no lldp transmit command disables LLDP advertisement transmission on the selected interface while allowing administrators to control receive behavior separately. HPE documents LLDP transmit and receive as independently configurable interface functions. This can be useful when a port should listen for neighbor advertisements but should not disclose local device information. Completely disabling LLDP is different because it affects the protocol more broadly. The command does not shut down the physical interface or disable other switching functions.

Question 365. What is the default interface speed mode?

1. Auto-negotiation
2. 100 Mbps half-duplex
3. 1 Gbps fixed
4. 10 Gbps fixed

Correct Answer: 1. Auto-negotiation

Explanation:

On supported AOS-CX Ethernet interfaces, auto-negotiation is the default speed behavior. The interface advertises the speeds supported by both the port and installed transceiver, allowing the link partners to select a mutually supported setting. Administrators can restrict the advertised speeds or configure a fixed speed when required. Auto-negotiation simplifies deployment because endpoints with different capabilities can establish the highest suitable link speed automatically instead of requiring manual configuration on both sides.

Question 366. What does speed 1000-full disable?

1. Full duplex
2. VLAN tagging
3. Flow control
4. Auto-negotiation

Correct Answer: 4. Auto-negotiation

Explanation:

The AOS-CX command speed 1000-full fixes the interface at 1000 Mbps full-duplex and disables auto-negotiation for speed and duplex. Fixed configuration can be useful when interoperating with equipment that requires specific settings, but both ends should be configured compatibly to avoid link or performance problems. HPE’s current command documentation explicitly identifies 1000-full as 1000 Mbps, full duplex, with no auto-negotiation. Returning to speed auto restores the normal negotiation behavior.

Question 367. Which speeds support half-duplex options?

1. 1 and 10 Gbps
2. 10 and 100 Mbps
3. 25 and 40 Gbps
4. 100 and 400 Gbps

Correct Answer: 2. 10 and 100 Mbps

Explanation:

AOS-CX documentation lists half-duplex fixed-speed settings for 10 Mbps and 100 Mbps Ethernet. Higher-speed settings such as 1 Gbps and above are shown as full-duplex options. Half-duplex allows transmission in only one direction at a time and is generally associated with older Ethernet environments. Modern campus networks overwhelmingly use full-duplex operation. When troubleshooting legacy links, however, administrators should verify that both endpoints use compatible speed and duplex settings to avoid performance problems.

Question 368. What does Ethernet flow control use?

1. DHCP messages
2. BPDUs
3. Pause frames
4. OSPF Hellos

Correct Answer: 3. Pause frames

Explanation:

IEEE 802.3x link-level flow control uses pause frames to temporarily request that a link partner stop transmitting traffic when congestion or buffer pressure occurs. AOS-CX can negotiate receive-only or bidirectional flow-control behavior on supported platforms. The exact capability depends on the switch family. Flow control is a Layer 2 mechanism and should not be confused with routing or DHCP. HPE interface statistics can also display pause-frame counters, which are useful when troubleshooting congestion or flow-control behavior.

Question 369. What must auto-negotiated flow control match?

1. VLAN names
2. Hostnames
3. NTP servers
4. Both link partners’ capabilities

Correct Answer: 4. Both link partners’ capabilities

Explanation:

For interfaces using auto-negotiation, link-level flow control is determined through negotiation between the two connected devices. HPE states that both sides must negotiate compatible flow-control behavior for it to take effect. If one side expects a different mode, the desired flow-control operation may not be established. When interfaces do not use auto-negotiation, administrators are responsible for configuring compatible settings manually on both ends. This makes consistent endpoint configuration important when troubleshooting pause-frame behavior.

Question 370. What must LAG members share?

1. Same flow-control setting
2. Different VLAN modes
3. Different duplex modes
4. Different MTUs

Correct Answer: 1. Same flow-control setting

Explanation:

HPE documents that all physical interfaces participating in a LAG must have the same flow-control configuration. A LAG is intended to behave as one logical interface, so inconsistent member settings can produce unpredictable forwarding or negotiation behavior. Administrators should verify compatible speed, aggregation, and flow-control configuration across members and on the remote peer. This consistency requirement is particularly important when troubleshooting an aggregation in which some member links join successfully while others do not behave as expected.

Question 371. What does EEE reduce?

1. VLAN count
2. MAC learning
3. Ethernet power use
4. Route preference

Correct Answer: 3. Ethernet power use

Explanation:

Energy-Efficient Ethernet, or EEE, is designed to reduce electrical power consumption on supported Ethernet links during periods of low traffic. AOS-CX provides an energy-efficient-ethernet interface command on supported platforms. The feature relies on compatible link partners and appropriate link negotiation. EEE does not change VLAN capacity, MAC learning, or routing preference. Its goal is simply to reduce energy use while maintaining normal Ethernet communication when traffic resumes.

Question 372. What does EEE require?

1. Static routing
2. Auto-negotiation with a supported peer
3. VSF
4. DHCP snooping

Correct Answer: 2. Auto-negotiation with a supported peer

Explanation:

HPE states that Energy-Efficient Ethernet negotiation is established only when auto-link negotiation is used with a compatible link partner. Both sides therefore need to support the required EEE behavior before energy-saving operation can be negotiated. Simply enabling the feature on one switch interface does not guarantee that EEE becomes active. Administrators can verify the negotiated state through interface operational information on supported systems. EEE has no dependency on static routing, VSF, or DHCP snooping.

Question 373. What can show interface verify?

1. Speed and duplex
2. RADIUS password
3. User certificate
4. AP license

Correct Answer: 1. Speed and duplex

Explanation:

The AOS-CX show interface output provides extensive physical and operational information, including link state, interface type, MTU, speed, duplex mode, auto-negotiation state, flow control, traffic rates, packet counters, and errors. This makes it one of the first commands to use when troubleshooting a link that is slow, down, or behaving inconsistently. It can quickly reveal whether the interface negotiated an unexpected speed or whether auto-negotiation is disabled.

Question 374. What does link-flap information show?

1. VLAN changes
2. PoE usage
3. Authentication failures
4. Repeated link state changes

Correct Answer: 4. Repeated link state changes

Explanation:

A link flap occurs when an interface repeatedly transitions between up and down states. AOS-CX show interface link-status output includes information such as link transitions, flap counts, and the time of the last state change. Repeated flapping can point to cabling problems, unstable optics, a failing endpoint, or incompatible physical settings. Reviewing this information helps administrators identify intermittent Layer 1 issues that may not be visible when the interface happens to be up at the moment of troubleshooting.

Question 375. What can LLDP-MED advertise for voice?

1. BGP AS number
2. VLAN and DSCP values
3. NTP stratum
4. DHCP pool

Correct Answer: 2. VLAN and DSCP values

Explanation:

LLDP-MED network-policy discovery can advertise information used by voice endpoints, including the voice VLAN ID and QoS markings such as PCP and DSCP values. A compatible IP phone can use this information to place its voice traffic into the intended VLAN and apply the desired traffic marking automatically. This makes access-port deployment simpler and reduces manual configuration on phones. HPE states that the LLDP-MED network-policy TLV is sent when a voice VLAN policy is present.

Question 376. When does AOS-CX send LLDP-MED TLVs?

1. Before link-up
2. On every disabled port
3. After receiving MED from the endpoint
4. Only after DHCP

Correct Answer: 3. After receiving MED from the endpoint

Explanation:

HPE documents that the switch sends LLDP-MED TLVs after it has received a MED TLV from the connected endpoint device. This behavior helps ensure that MED-specific information is exchanged with devices that actually support the extension. LLDP-MED is designed especially for endpoints such as IP phones and other media devices. Normal LLDP can continue to advertise standard discovery information independently. DHCP is not a prerequisite for LLDP-MED exchange because LLDP operates directly at Layer 2.

Question 377. What is LLDP’s last default management-address fallback?

1. DNS address
2. NTP address
3. Gateway address
4. Base MAC

Correct Answer: 4. Base MAC

Explanation:

HPE documents the default LLDP management-address selection order as: configured LLDP management IP address first, then an available SVI, and finally the switch base MAC address if the earlier choices are unavailable. This provides LLDP neighbors with useful management-identification information even when an IP management address has not been selected. The base MAC is therefore the final default fallback in the documented order. DNS, NTP, and gateway addresses are not used as the fallback LLDP management identifier.

Question 378. What does LLDP-MED PoE advertise?

1. OSPF priority
2. Power information
3. Route metrics
4. DHCP leases

Correct Answer: 2. Power information

Explanation:

The LLDP-MED PoE TLV carries power-related information between compatible endpoints and network infrastructure. This is particularly useful for devices such as IP phones that receive electrical power through Ethernet. HPE’s LLDP-MED implementation includes Power Via MDI information and can support power-priority behavior on applicable platforms. The feature helps network devices and powered endpoints communicate power capabilities and requirements through LLDP-MED rather than relying only on basic discovery information.

Question 379. What does full duplex allow?

1. Simultaneous transmit and receive
2. Transmit only
3. Receive only
4. Half-speed operation

Correct Answer: 1. Simultaneous transmit and receive

Explanation:

Full-duplex Ethernet allows both ends of a link to transmit and receive at the same time. This eliminates the collision behavior associated with traditional half-duplex shared Ethernet and provides more efficient use of the link. Modern switched Ethernet normally operates full duplex, especially at Gigabit Ethernet and higher speeds. AOS-CX interface output explicitly reports duplex state, making it easy to verify during troubleshooting. Fixed speed commands for modern high-speed interfaces are also documented as full-duplex operation.

Question 380. Which design BEST supports an IP phone port?

1. Disable LLDP
2. Fixed half duplex
3. LLDP-MED, voice policy, and auto-negotiation
4. Disable PoE

Correct Answer: 3. LLDP-MED, voice policy, and auto-negotiation

Explanation:

An IP phone access port benefits from several complementary technologies. LLDP-MED can advertise voice VLAN and QoS policy information so the phone configures its traffic correctly. PoE-related MED information can assist supported power negotiation, while Ethernet auto-negotiation helps establish compatible speed and duplex settings. Disabling LLDP or PoE would remove useful endpoint services, and forcing legacy half-duplex operation would reduce performance unnecessarily. This combination therefore provides practical automated voice endpoint onboarding on an AOS-CX access switch.