Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

HPE7-A07 Exam - Topic 5 Question 49 Discussion

A customer is evaluating device profiles on a CX 6300 switch. The test device has the following attributes:* MAC address = 81:cd:93:13:ab:31* LLDP sys-desc = iotcontrollerThe test device is being assigned to the ''lot-dev'' role However, the customer requires the "lot-prod'' role be applied.Given the configuration, what is causing the "iot-dev" role to be applied to the device'?
D) The LLDP system description matches the IIdp-group configuration.
A) The test device does not support CDP.
B) The device-profile precedence order is not configured.
C) An external RADIUS server is unreachable.

HPE7-A07 Exam - Topic 5 Question 49 Discussion

Actual exam question for HP's HPE7-A07 exam
Question #: 49
Topic #: 5
[All HPE7-A07 Questions]

A customer is evaluating device profiles on a CX 6300 switch. The test device has the following attributes:

* MAC address = 81:cd:93:13:ab:31

* LLDP sys-desc = iotcontroller

The test device is being assigned to the ''lot-dev'' role However, the customer requires the "lot-prod'' role be applied.

Given the configuration, what is causing the "iot-dev" role to be applied to the device'?

Show Suggested Answer Hide Answer
Suggested Answer: D

In device profile configuration, the device role is often determined by matching attributes such as MAC address, LLDP system description, and CDP information against defined conditions. The test device is being assigned the 'iot-dev' role because its LLDP system description matches the 'iot-lldp' group configuration that is associated with the 'iot-dev' role.


Contribute your Thoughts:

0/2000 characters
Jess
4 days ago
Agreed, D makes sense. It's all about that match.
upvoted 0 times
...
Audrie
10 days ago
I think it's D. The LLDP description matches the group.
upvoted 0 times
...
Leoma
15 days ago
Nah, it’s definitely the LLDP description causing this.
upvoted 0 times
...
Margurite
20 days ago
I think the device-profile precedence order might be off too.
upvoted 0 times
...
Erinn
25 days ago
Wait, could it be the RADIUS server? Seems odd.
upvoted 0 times
...
Tran
1 month ago
Totally agree, that's likely the issue here.
upvoted 0 times
...
Jacklyn
1 month ago
The LLDP sys-desc is "iotcontroller," so it matches the profile.
upvoted 0 times
...
Denny
1 month ago
Totally agree, the LLDP match is likely the culprit!
upvoted 0 times
...
Rusty
2 months ago
Wait, so an unreachable RADIUS server could cause this?
upvoted 0 times
...
Berry
2 months ago
I thought CDP was the only protocol that mattered here?
upvoted 0 times
...
Queen
2 months ago
Definitely a config issue with the device-profile precedence.
upvoted 0 times
...
Teri
2 months ago
The LLDP sys-desc is set to "iotcontroller".
upvoted 0 times
...
Keneth
2 months ago
What if the RADIUS server is down? I feel like that could also lead to the wrong role being applied, but I need to double-check that.
upvoted 0 times
...
Aliza
2 months ago
I'm leaning towards option D because the LLDP sys-desc seems to match the configuration, but I could be wrong.
upvoted 0 times
...
Erick
3 months ago
I think we practiced a question similar to this where the device profile precedence was a factor. Could that be the issue?
upvoted 0 times
...
Camellia
4 months ago
I remember something about LLDP and how it can affect device profiling, but I'm not entirely sure if it's the main reason here.
upvoted 0 times
...

Save Cancel