300-715 · Question #58
The default Cisco ISE node configuration has which role or roles enabled by default?
The correct answer is D. Policy Service Monitoring, and Administration. By default, a fresh Cisco ISE installation on a single node enables all three primary roles: Administration, Policy Service, and Monitoring. This configuration supports full functionality for managing policies, handling authentication/authorization, and collecting operational dat
Question
The default Cisco ISE node configuration has which role or roles enabled by default?
Options
- AAdministration only
- BInline Posture only
- CAdministration and Pokey Service
- DPolicy Service Monitoring, and Administration
How the community answered
(16 responses)- C6% (1)
- D94% (15)
Why each option
By default, a fresh Cisco ISE installation on a single node enables all three primary roles: Administration, Policy Service, and Monitoring. This configuration supports full functionality for managing policies, handling authentication/authorization, and collecting operational data.
Administration only is incorrect because Policy Service and Monitoring roles are also enabled by default.
Inline Posture only is incorrect as Inline Posture is an optional service and not a default core role, nor is it the only one enabled.
'Pokey Service' is not a standard Cisco ISE node role, and while Administration is a default role, this choice includes an invalid service.
When Cisco ISE is deployed as a standalone node (the initial installation), it is configured with all three core services enabled by default: Administration (for managing ISE), Policy Service (for handling authentication/authorization requests), and Monitoring (for logging and reporting). This allows a single node to perform all necessary functions in a small deployment or as a primary node before a distributed deployment.
Concept tested: Cisco ISE default node roles
Source: https://www.cisco.com/c/en/us/td/docs/security/ise/3-1/admin_guide/b_ise_admin_31/b_ise_admin_31_chapter_010.html
Topics
Community Discussion
No community discussion yet for this question.