HPE6-A48 · Question #56
Refer to the exhibits. Exhibit 1 Exhibit 2 A network administrator adds a new Mobility Controller (MC) to the production Mobility Master (MM) and deploys APs that start broadcasting the employees…
The correct answer is B. The digital certificate of the MC is not trusted by the MM. A network administrator adds a Mobility Controller (MC) in the /mm level and notices that the device does not show up in the managed networks hierarchy. The network administrator accesses the CLI, executes the show switches command, and obtains the output shown in the exhibit…
Question
Refer to the exhibits. Exhibit 1 Exhibit 2 A network administrator adds a new Mobility Controller (MC) to the production Mobility Master (MM) and deploys APs that start broadcasting the employees SSID in the West wing of the building. Suddenly, the employed report client disconnects. When accessing the MM the network administrator notices that the MC is unreachable, then proceeds to access the MC's console and obtains the outputs shown in the exhibits. What should the network administrator do next to solve the current problem?
Exhibit
Options
- AThe network administrator added the device using the wrong Pre=shared Key (PSK).
- BThe digital certificate of the MC is not trusted by the MM.
- CThe IP address of the MC does not match the one that was defined in the MM.
- DThe network administrator has not moved the device into a group yet.
How the community answered
(44 responses)- A7% (3)
- B75% (33)
- C16% (7)
- D2% (1)
Explanation
A network administrator adds a Mobility Controller (MC) in the /mm level and notices that the device does not show up in the managed networks hierarchy. The network administrator accesses the CLI, executes the show switches command, and obtains the output shown in the exhibit. What is the reason that the MC does not appear as a managed device in the hierarchy?
Topics
Community Discussion
No community discussion yet for this question.