Courseiva

CCNA Network Access Device Administration Questions

39 questions · Network Access Device Administration topic · All types, answers revealed

1
MCQmedium

When defining a Shell Profile for a TACACS+ administrator, which setting ensures the user is placed into privilege level 15 immediately upon login?

A.Set 'Attribute' to 'priv-lvl=15' in custom attributes
B.Set the 'Auto-Command' to 'enable 15'
C.Configure the 'Privilege Level' field to 15
D.Enable 'Maximum Privilege' in the command set
AnswerC

Setting the Privilege Level field to 15 in the Shell Profile assigns the maximum TACACS+ privilege directly at authorisation, so the administrator lands in enable mode on login without issuing an enable command. This satisfies the stem's requirement for immediate privilege level 15 placement.

Why this answer

In Cisco ISE's TACACS+ shell profile, the 'Privilege Level' field is the explicit setting that assigns the user's initial privilege level upon login. Setting it to 15 places the administrator directly into privileged EXEC mode without requiring an 'enable' command.

Exam trap

SISE often tests whether candidates know that privilege level is set in the Shell Profile's Privilege Level field, not via custom AV pairs or auto-commands — candidates overcomplicate it by trying to hand-craft priv-lvl attributes.

How to eliminate wrong answers

Option A is wrong because while priv-lvl is the underlying TACACS+ AV pair, ISE exposes it through the dedicated Privilege Level field in the shell profile — manually crafting custom attributes is unnecessary and error-prone. Option B is wrong because Auto-Command runs a command after login (e.g., 'show version') but does not itself elevate privilege; using 'enable 15' as an auto-command is a workaround, not the intended configuration. Option D is wrong because 'Maximum Privilege' is not a valid ISE shell profile setting — privilege is controlled by the Privilege Level field and the command set, not a 'maximum' toggle.

2
MCQmedium

Which attribute in a Shell Profile is used to control whether a user can perform 'enable' commands?

A.Custom Attributes
B.Privilege Level
C.Auto-Command
D.Command Authorization
AnswerB

Privilege Level in the Shell Profile defines the maximum TACACS+ privilege level assigned to the user after authentication, which determines whether enable commands are permitted. Setting it to 15 allows enable; lower values restrict it, directly satisfying the stem's control requirement.

Why this answer

In an ISE Shell Profile, the Privilege Level attribute determines the privilege level assigned to the user on the network device after TACACS+ authorization. On Cisco IOS, privilege level 15 is required to run 'enable' and enter privileged EXEC mode, so this attribute directly controls whether a user can perform enable commands.

Exam trap

The trap is assuming Command Authorization alone governs enable access; candidates forget that privilege level (priv-lvl) is the gatekeeper for entering privileged EXEC mode.

How to eliminate wrong answers

Option A is wrong because Custom Attributes are arbitrary key-value pairs used for policy conditions or RADIUS returns, not a built-in control for enable capability. Option C is wrong because Auto-Command specifies a command that runs automatically upon login (for example, 'show version'), not the privilege level that governs enable access. Option D is wrong because Command Authorization is the mechanism that checks individual commands against a Command Set; it does not itself set the privilege level that determines enable access.

3
MCQmedium

You are implementing TACACS+ device administration for a group of routers. You need to assign specific privilege levels to different users. Where in the ISE policy set is this privilege assignment configured?

A.In the Shell Profile assigned to the Authorization Policy.
B.In the Network Device Group settings.
C.In the Command Set configuration.
D.In the Network Device definition.
AnswerA

Privilege levels for TACACS+ device administration are delivered through the Shell Profile referenced by the Authorization Policy result. The profile contains the actual privilege and command-set values, so assigning it within the authorisation rule is what maps users to their router privilege levels.

Why this answer

Privilege level assignment in ISE TACACS+ is configured in the Shell Profile, which is then referenced by the Authorization Policy. The shell profile contains the Privilege Level field (and other AV pairs) that ISE returns to the network device to set the user's EXEC privilege after authentication.

Exam trap

SISE often tests the confusion between Shell Profile (privilege level and shell attributes) and Command Set (per-command authorization) — candidates mix up which object controls privilege versus which controls allowed commands.

How to eliminate wrong answers

Option B is wrong because Network Device Group settings categorize devices (location, type) for policy matching — they don't assign user privilege levels. Option C is wrong because the Command Set defines which commands are permitted or denied, not the user's privilege level. Option D is wrong because the Network Device definition holds the device's IP, shared secret, and TACACS+ settings — it has nothing to do with per-user privilege assignment.

4
MCQhard

You are troubleshooting a scenario where an admin cannot execute a specific command despite the Command Set having 'Permit' for that command. What is a common reason?

A.The ISE Policy Set has 'Deny' as the default
B.The user is in the wrong AD group
C.The TACACS+ shared secret is incorrect
D.The command is blocked by the switch's local configuration
AnswerD

Cisco ISE authorises commands through the Command Set, but the switch's local configuration, such as a privilege level or parser view restriction, can still deny execution. Authorisation succeeds while the device itself blocks the command, so the admin cannot run it despite the Permit result.

Why this answer

A common reason a permitted command still fails is that the switch's local configuration blocks it. For example, local command authorization, privilege-level restrictions, or AAA command authorization configured locally on the device can deny a command even when ISE's Command Set permits it. The device's local policy takes precedence or acts as an additional gate.

Exam trap

The trap is assuming ISE is the sole authority; candidates forget that the network device's local configuration can independently block a command even when ISE permits it.

How to eliminate wrong answers

Option A is wrong because a default 'Deny' in the Policy Set would affect all commands not explicitly permitted, not a single command that is already permitted in the Command Set. Option B is wrong because AD group membership affects which authorization rule matches, but if the Command Set is already applied and permits the command, the AD group is not the direct cause. Option C is wrong because an incorrect TACACS+ shared secret would break authentication entirely, not selectively block one command.

5
MCQeasy

Which port does Cisco ISE use by default for TACACS+ communication with network devices?

A.TCP 8443
B.UDP 1812
C.UDP 1645
D.TCP 49
AnswerD

TACACS+ uses TCP port 49 for communication between Cisco ISE and network devices. Unlike RADIUS, which uses UDP ports 1812 and 1813, TACACS+ separates authentication, authorisation and accounting over a single TCP connection, making port 49 the default for device administration.

Why this answer

TACACS+ uses TCP port 49 by default for all communication between the network access device and the AAA server such as Cisco ISE. This is a well-known, IANA-registered port specifically assigned to the TACACS+ protocol. ISE listens on TCP 49 for TACACS+ requests from NADs.

Exam trap

The trap is mixing up TACACS+ (TCP 49) with RADIUS ports (UDP 1812/1813 or legacy 1645/1646) — candidates often default to RADIUS ports because RADIUS is more commonly discussed.

How to eliminate wrong answers

Option A is wrong because TCP 8443 is used by ISE for administrative HTTPS/portal access, not TACACS+. Option B is wrong because UDP 1812 is the RADIUS authentication port (and 1813 is accounting), not TACACS+. Option C is wrong because UDP 1645 is the legacy RADIUS authentication port retained for backward compatibility, not TACACS+.

6
MCQeasy

In the context of TACACS+, what is the purpose of the 'Network Device Group'?

A.To enable remote logging
B.To organize devices for policy assignment
C.To set the shared secret for all devices in the group
D.To update the device firmware
AnswerB

Network Device Groups classify TACACS+ clients into logical groupings, such as by location or device type. This grouping lets administrators bind command sets and authorisation policies to whole categories of devices rather than configuring each one individually, satisfying scalable policy assignment.

Why this answer

In TACACS+, a Network Device Group (NDG) is used to logically group network devices (e.g., by location, type, or function) so that policies, command sets, and authorization rules can be applied to the group rather than individual devices. This simplifies management and enables scalable policy assignment.

Exam trap

SISE often tests the purpose of NDGs; candidates may confuse them with device configuration settings like shared secrets or logging, but NDGs are purely for logical grouping and policy application.

How to eliminate wrong answers

Option A is wrong because remote logging is typically configured via syslog or TACACS+ accounting, not through NDGs; NDGs do not enable logging. Option C is wrong because the shared secret is configured per device or globally in TACACS+ server settings, not through NDGs; NDGs are for policy organization. Option D is wrong because firmware updates are not a function of TACACS+ or NDGs; they are handled by device management systems.

7
MCQhard

When troubleshooting TACACS+ authentication issues in Cisco ISE, which log file should you monitor to see the specific request details and the policy match result?

A.System Summary Dashboard
B.Endpoint Context Visibility
C.TACACS+ Livelogs
D.RADIUS Livelogs
AnswerC

TACACS+ Livelogs capture per-request authentication detail, including the matched policy set and authorisation result, which the stem requires. Unlike passive log files, Livelogs stream live request attributes and rule evaluations, so you can pinpoint exactly why a device's TACACS+ authentication attempt succeeded or failed.

Why this answer

TACACS+ Livelogs in Cisco ISE is the dedicated real-time log view that shows TACACS+ authentication and authorization request details, including the policy set and rule that matched. When troubleshooting TACACS+ authentication issues, this is the correct log to monitor because it captures the full request/response exchange and the policy evaluation result. RADIUS Livelogs, by contrast, only show RADIUS traffic and would not display TACACS+ request details.

Exam trap

SISE often tests whether candidates know that TACACS+ and RADIUS have separate Livelogs — picking RADIUS Livelogs for a TACACS+ issue is the classic wrong answer.

How to eliminate wrong answers

Option A is wrong because the System Summary Dashboard provides high-level health and performance metrics, not per-request TACACS+ authentication details or policy match results. Option B is wrong because Endpoint Context Visibility shows endpoint attributes and profiling data, not TACACS+ authentication request logs. Option D is wrong because RADIUS Livelogs only capture RADIUS authentication/authorization exchanges — TACACS+ requests are a separate protocol and will not appear there.

8
Multi-Selectmedium

Which TWO of the following are valid components of a TACACS+ Authorization Policy in Cisco ISE? (Choose two)

Select 2 answers
A.User Password
B.RADIUS attribute list
C.Shell Profile
D.Device Shared Secret
E.Command Set
AnswersC, E

A TACACS+ authorization policy rule binds identity and group conditions to a Shell Profile, which defines the privilege level and session attributes returned to the network device. Shell Profile is therefore a valid policy component, satisfying the stem's requirement for authorised elements.

Why this answer

In Cisco ISE, a TACACS+ Authorization Policy is built from authorization results that define what an authenticated user is permitted to do on a network device, and the two valid components here are the Shell Profile (C) and the Command Set (E). The Shell Profile (C) is correct because it defines the privilege level and shell attributes (such as default privilege, maximum privilege, and auto-command) that ISE returns in the TACACS+ authorization response to control the user's CLI session. The Command Set (E) is correct because it specifies the set of commands (permit/deny with optional arguments) that the user is authorized to execute, and it is referenced by the Shell Profile or applied directly in the authorization result.

User Password (A) is not a TACACS+ authorization component; it is authentication data handled during the authentication phase. RADIUS attribute list (B) is incorrect because RADIUS attributes belong to RADIUS-based authorization, not TACACS+ authorization policy components. Device Shared Secret (D) is incorrect because it is a credential used to secure communication between the network device and ISE, not a component of the authorization policy itself.

Exam trap

SISE often tests whether candidates can distinguish authentication components (passwords, shared secrets) from authorization result components (shell profile, command set) — candidates pick credentials thinking they're part of the authorization policy.

9
MCQmedium

A network engineer is troubleshooting a TACACS+ authentication failure on a Cisco switch. The switch is configured to use Cisco ISE as its TACACS+ server. The engineer runs 'debug tacacs' on the switch and sees that the request is sent but no response is received. Which action should the engineer take first to resolve the issue?

A.Ensure that the switch is configured to use RADIUS for authentication.
B.Verify that the shared secret on the switch matches the one configured in ISE for the switch.
C.Restart the ISE services to clear any temporary glitches.
D.Check if the switch's IP address is in the ISE Identity Group.
AnswerB

If the shared secret does not match, ISE will not respond to TACACS+ requests, and the switch will not receive a response. This is a common cause of TACACS+ failures. The engineer should first check the shared secret on both the switch and ISE. If they differ, the switch's request will be silently dropped by ISE, leading to the observed behavior.

Why this answer

When a TACACS+ request is sent but no response is received, a common cause is a shared secret mismatch. ISE will not respond if the shared secret does not match the one configured on the network device. The engineer should verify the shared secret on both the switch and ISE.

Other steps, such as checking Identity Groups or restarting services, are not relevant to this specific symptom.

Exam trap

The trap here is assuming that ISE will send an error response for a shared secret mismatch; instead, it silently drops the packet, leading to no response.

10
MCQmedium

A network engineer is adding a Cisco Catalyst 9300 switch to Cisco ISE for TACACS+ device administration. The switch will use a shared secret of 'C1sco123'. The engineer wants to ensure that ISE can authenticate and authorize administrative sessions from this device. Where should the shared secret be configured in ISE?

A.In the Network Device definition under Administration > Network Resources > Network Devices.
B.In the TACACS+ Profile under Work Centers > Device Administration > Policy Elements > TACACS Profiles.
C.In the TACACS+ Command Set under Work Centers > Device Administration > Policy Elements > Command Sets.
D.In the External RADIUS Server configuration under Administration > External RADIUS Servers.
AnswerA

The shared secret for a TACACS+ network device is configured directly in the Network Device object in ISE. This secret is used to encrypt the entire TACACS+ packet payload and must match the key configured on the switch with the 'tacacs server' command. Without this, ISE will not process authentication requests from the device.

Why this answer

The shared secret for TACACS+ is a device-specific credential configured in the Network Device object in ISE. It must match the key on the switch. Command Sets and TACACS+ Profiles define authorization results, not authentication credentials.

External RADIUS Servers are for outbound proxying. Therefore, the Network Device definition is the correct place to configure the shared secret.

Exam trap

The trap here is confusing the shared secret, which is configured in the Network Device definition, with authorization policy elements like Command Sets or TACACS+ Profiles.

11
MCQmedium

Which of the following is a best practice when configuring TACACS+ for network administration?

A.Enable command authorization
B.Use RADIUS for command authorization
C.Use a single shared secret for all devices
D.Disable accounting for performance
AnswerA

Command authorization makes the TACACS+ server verify each command against the admin's assigned command set before the device executes it, enforcing least privilege. This satisfies the stem's best-practise requirement by restricting administrators to only the commands their role permits.

Why this answer

Enabling command authorization is a best practice for TACACS+ because it allows the TACACS+ server to authorize each command a user attempts to execute, providing granular control over what administrators can do on network devices. This enforces the principle of least privilege and is a core strength of TACACS+ over RADIUS.

Exam trap

The trap is thinking RADIUS can perform command authorization; candidates may choose RADIUS because it is also an AAA protocol, but only TACACS+ supports per-command authorization.

How to eliminate wrong answers

Option B is wrong because RADIUS does not support command authorization; it is primarily used for authentication and accounting, and its authorization capabilities are limited to attributes like VLAN or ACL, not per-command control. Option C is wrong because using a single shared secret for all devices is a security risk; best practice is to use unique shared secrets per device to limit the impact of a compromised secret. Option D is wrong because disabling accounting for performance is not a best practice; accounting is essential for auditing and compliance, and its performance impact is minimal.

12
MCQmedium

Where are the TACACS+ accounting logs stored and viewed in the ISE management console?

A.Operations > TACACS Livelogs
B.Monitoring > Reports > TACACS
C.Administration > System > Logging
D.Policy > Policy Elements
AnswerA

TACACS+ accounting records stream into the Operations > TACACS Livelogs viewer, which displays command authorisation and accounting events in real time. This satisfies the stem's requirement to locate where accounting logs are stored and viewed within the ISE management console, rather than under RADIUS or reporting sections.

Why this answer

TACACS+ accounting logs in Cisco ISE are viewed under Operations > TACACS Livelogs. This live log view shows real-time TACACS+ authentication, authorization, and accounting events, including command execution details, the user, the device, and the result. It is the primary troubleshooting and auditing interface for TACACS+ activity in the ISE GUI.

Exam trap

SISE often tests the exact menu path for TACACS+ accounting logs, and candidates confuse Operations > TACACS Livelogs with Monitoring > Reports or Administration > Logging.

How to eliminate wrong answers

Option B is wrong because Monitoring > Reports > TACACS is not the correct path for viewing live TACACS+ accounting events; reports are for aggregated/exported data, not real-time livelogs. Option C is wrong because Administration > System > Logging configures ISE's own system logging (syslog targets, log levels), not TACACS+ accounting records. Option D is wrong because Policy > Policy Elements contains reusable policy objects like authorization profiles and command sets, not log data.

13
MCQhard

A user is assigned a Command Set that permits all commands, but they are still receiving 'Access Denied' when running 'reload'. What is the most likely reason?

A.The Command Set is not applied in the Policy Set
B.The device is not authorized for the command
C.The user's privilege level on the device is insufficient
D.The TACACS+ server is unreachable
AnswerC

Command Sets authorise which commands are available, but the device's privilege level (privilege exec level) independently gates execution. A 'reload' requires privilege level 15, so a user at a lower level receives 'Access Denied' despite the Command Set permitting all commands.

Why this answer

Even if a Command Set permits all commands, the user must have a sufficient privilege level on the device to execute privileged commands like 'reload'. If the Shell Profile assigns a low privilege level (for example, priv-lvl 1), the device will reject 'reload' with 'Access Denied' regardless of the Command Set.

Exam trap

The trap is assuming a permissive Command Set is sufficient; candidates overlook that privilege level is enforced first and can block commands even when the command set allows them.

How to eliminate wrong answers

Option A is wrong because if the Command Set were not applied in the Policy Set, the user would typically get a default deny for all commands, not a selective denial of 'reload' while other commands work. Option B is wrong because device authorization is a broad concept; the specific symptom of 'reload' failing while other commands succeed points to privilege level, not device-level authorization. Option D is wrong because an unreachable TACACS+ server would cause authentication or authorization to fail entirely, not just a single command.

14
MCQmedium

Which component in Cisco ISE defines the TACACS+ privilege levels and attributes sent to the network device?

A.Command Set
B.Network Device Group
C.Shell Profile
D.Authorization Policy
AnswerC

A TACACS+ shell profile defines what ISE returns when an administrator starts a shell session: default and maximum privilege levels, attributes such as idle timeout and auto-command, and custom attribute-value pairs for platforms that need them. The Device Administration authorization policy selects which shell profile applies to which users and devices, often alongside command sets that restrict individual commands.

Why this answer

The Shell Profile in Cisco ISE is the authorization component that defines the TACACS+ privilege level (e.g., Privilege 15) and shell attributes such as idle timeout and session timeout that are returned to the network device in the TACACS+ authorization response. It is referenced from the Authorization Policy result and determines the user's shell-level access on the device.

Exam trap

SISE often tests the confusion between Shell Profile (privilege level and shell attributes) and Command Set (per-command authorization), causing candidates to pick Command Set when the question asks about privilege levels.

How to eliminate wrong answers

Option A is wrong because a Command Set defines which individual CLI commands are permitted or denied (via command authorization), not the privilege level or shell attributes. Option B is wrong because a Network Device Group is used to logically group NADs for policy conditions and hit selection, not to define TACACS+ privilege attributes. Option D is wrong because the Authorization Policy is the rule that matches conditions and selects results (Shell Profile, Command Set, etc.), but it does not itself contain the privilege level or shell attributes.

15
Multi-Selectmedium

Which TWO of the following are benefits of using Network Device Groups (NDG)? (Choose two)

Select 2 answers
A.Eliminates the need for shared secrets
B.Automatically updates the device config
C.Simplifies policy management by grouping devices
D.Allows granular policy targeting based on location or role
E.Replaces the need for TACACS+ command sets
AnswersC, D

Grouping network devices into Network Device Groups lets a single policy apply to many devices at once, removing the need to configure each device individually. This directly delivers the simplified policy management benefit named in the option.

Why this answer

Option C is correct because Network Device Groups (NDGs) in Cisco ISE let you organize network access devices into logical collections so that authorization policies and policy sets can be applied to the group as a whole rather than to each device individually, greatly simplifying policy management. Option D is correct because NDGs can be defined by attributes such as location, device type, or role, allowing authorization rules and policy conditions to target specific groups of devices with granular precision. Options A, B, and E are incorrect: NDGs do not eliminate shared secrets (RADIUS/TACACS+ shared secrets are still configured per device), they do not automatically push or update device configurations (that is the role of configuration management tools, not NDGs), and they do not replace TACACS+ command sets, which are still required to control the specific commands an administrator may execute on a device.

Exam trap

SISE often tests the misconception that NDGs are functional configuration objects — candidates assume they push configs or replace secrets, when they are purely a logical grouping mechanism for policy targeting.

16
MCQeasy

Which component in ISE is responsible for mapping an authenticated user to a specific set of permissions and command restrictions in a TACACS+ environment?

A.TACACS+ Authorization Policy
B.TACACS+ Authentication Policy
C.Policy Set
D.Network Device Group
AnswerA

TACACS+ separates authentication from authorization, and the authorization policy is what maps an authenticated identity to per-command permissions and restrictions. It satisfies the stem's requirement to translate a verified user into a specific permission set and command restrictions.

Why this answer

In ISE TACACS+, the Authorization Policy is the component that evaluates the authenticated identity and device attributes and returns the authorization result, including the shell profile and command set that define permissions and command restrictions. Authentication only verifies identity; authorization is what maps the user to a specific permission set.

Exam trap

The trap is conflating authentication with authorization: candidates pick the Authentication Policy because the user was 'authenticated,' but permissions and command restrictions are always an authorization function.

How to eliminate wrong answers

Option B is wrong because the TACACS+ Authentication Policy only validates credentials (via AD, internal users, etc.) and does not assign permissions or command restrictions. Option C is wrong because a Policy Set is the container that groups authentication and authorization policies for matching conditions, not the component that maps users to permissions. Option D is wrong because a Network Device Group is a classification construct used in policy conditions to group devices, not a mechanism for assigning user permissions.

17
Multi-Selecthard

Which THREE of the following items are considered 'results' in an ISE authorization policy? (Choose three)

Select 3 answers
A.Authorization Profile
B.Shared Secret
C.Command Set
D.Shell Profile
E.Network Device Group
AnswersA, C, D

An Authorization Profile is a result, not a condition: it defines what ISE returns after a rule matches, such as VLAN, dACL, SGT or posture settings. It sits in the results section of the authorization policy.

Why this answer

In an ISE authorization policy, the results are the enforcement artifacts that ISE returns to the network access device (NAD) once a matching authorization rule is hit. Option A (Authorization Profile) is correct because it is the primary result object, bundling attributes such as VLAN, dACL, SGT, and reauthentication timers that are pushed to the NAD via RADIUS. Option C (Command Set) is correct because it is a result that defines the set of TACACS+ commands (permit/deny) an authenticated administrator is allowed to run on a device.

Option D (Shell Profile) is correct because it is a TACACS+ result that specifies the privilege level and shell attributes (e.g., default privilege, auto-command) assigned to an admin session. Option B (Shared Secret) is not a result; it is a credential used to secure RADIUS/TACACS+ communication between ISE and the NAD, configured under Network Devices. Option E (Network Device Group) is not a result; it is a condition/attribute used to classify and match NADs within policy rules, not an enforcement outcome.

Exam trap

SISE often tests the distinction between policy conditions (NDGs, identity groups) and policy results (Authorization Profiles, Shell Profiles, Command Sets), so candidates who pick NDG or Shared Secret confuse the input side with the output side of the rule.

18
MCQmedium

How can you verify that ISE is receiving TACACS+ requests from a specific switch?

A.View the Network Device list
B.Check the TACACS Livelogs
C.Run a packet capture on the switch
D.Check the System Summary
AnswerB

TACACS Livelogs display real-time authentication, authorisation and accounting exchanges, showing each request's source device and outcome. Filtering by the switch's IP confirms whether ISE is receiving its TACACS+ traffic, directly satisfying the requirement to verify connectivity from that specific switch.

Why this answer

Cisco ISE provides TACACS+ Livelogs under Operations > TACACS > Live Logs, which show real-time TACACS+ authentication and authorization requests received from network devices. This is the direct way to verify that ISE is receiving TACACS+ requests from a specific switch, including the device name, user, and result.

Exam trap

The trap is choosing configuration views (Network Device list) or packet captures instead of the operational Live Logs that directly show received TACACS+ requests.

How to eliminate wrong answers

Option A is wrong because the Network Device list only shows configured NADs, not whether requests are actually arriving from them. Option C is wrong because a packet capture on the switch shows outbound packets but does not confirm ISE received or processed them. Option D is wrong because the System Summary shows ISE health and performance metrics, not per-request TACACS+ activity.

19
MCQhard

A network administrator is configuring a Cisco ISE TACACS+ Command Set to allow users to execute 'show running-config' but deny all other 'show' commands. Which command set configuration in ISE achieves this?

A.Deny: show *; Permit: show running-config
B.Permit: show running-config; Permit: show *
C.Permit: show running-config; Deny: show *
D.Permit: show *; Deny: show running-config
AnswerC

This configuration explicitly permits the exact command 'show running-config' and then denies all other commands starting with 'show'. In ISE Command Sets, the order of entries matters; the permit for the specific command must come before the deny for the broader pattern. This ensures that only 'show running-config' is allowed among show commands.

Why this answer

In ISE Command Sets, entries are evaluated top-down, and the first match is applied. To permit a specific command and deny all others in a category, you must place the permit for the specific command before the deny for the broader pattern. The correct configuration permits 'show running-config' and then denies 'show *', ensuring only that specific command is allowed.

The reverse order would deny the specific command as well.

Exam trap

The trap here is misunderstanding the order of evaluation in Command Sets; the first matching entry wins, so a broad deny before a specific permit will block the permitted command.

20
Multi-Selecthard

Which THREE of the following are characteristics of the TACACS+ protocol? (Choose three)

Select 3 answers
A.Uses TCP port 49
B.Encrypts the entire packet body
C.Only encrypts the password field
D.Uses UDP port 1812
E.Separates authentication, authorization, and accounting
AnswersA, B, E

TACACS+ establishes its connection over TCP port 49, satisfying the stem's requirement for a defining transport characteristic. Unlike RADIUS, which uses UDP ports 1812 and 1813, TACACS+ relies on TCP to provide reliable, connection-oriented delivery, separating authentication, authorisation and accounting into distinct functions.

Why this answer

Option A is correct because TACACS+ operates over TCP and uses well-known port 49 for its communications between the client (NAS) and the TACACS+ server. Option B is correct because TACACS+ encrypts the entire body of the packet, not just credentials, providing confidentiality for all payload data exchanged. Option E is correct because TACACS+ is designed to separate the AAA functions—authentication, authorization, and accounting—into distinct processes, allowing each to be handled independently.

Option C is not correct because encrypting only the password field is characteristic of RADIUS, not TACACS+. Option D is not correct because UDP port 1812 is used by RADIUS authentication, whereas TACACS+ uses TCP port 49.

Exam trap

The trap is mixing up RADIUS and TACACS+ characteristics — candidates often remember 'TACACS+ encrypts everything' but then incorrectly assign UDP 1812 or password-only encryption to it under time pressure.

21
MCQeasy

What is the benefit of using multiple TACACS+ Policy Sets?

A.To increase the speed of authentication
B.To reduce the need for shared secrets
C.To increase the number of users allowed
D.To segment policies by device type or user group
AnswerD

Multiple TACACS+ policy sets let administrators apply distinct rule sets matched by device type or user group, rather than one monolithic policy. This segmentation satisfies the requirement to tailor authorisation per device category or user population.

Why this answer

Multiple TACACS+ Policy Sets allow you to segment policies by device type or user group, so different sets of rules can be applied to different network devices or administrative roles. This provides granular control over command authorization and accounting for diverse device populations.

Exam trap

SISE often tests the purpose of multiple TACACS+ Policy Sets, so candidates who pick 'increase speed' or 'reduce shared secrets' confuse organizational segmentation with performance or security mechanics.

How to eliminate wrong answers

Option A is wrong because multiple policy sets do not increase authentication speed — they add organizational structure, not performance. Option B is wrong because shared secrets are configured per network device, not per policy set, so policy sets do not reduce the need for them. Option C is wrong because the number of users allowed is determined by licensing and the identity store, not by the number of policy sets.

22
MCQhard

If a user is authenticated via TACACS+ but no authorization policy matches, what is the default behavior?

A.The user is granted read-only access
B.The user is prompted to re-authenticate
C.The user is granted full access
D.The user is rejected
AnswerD

TACACS+ applies a default-deny model: if authentication succeeds but no authorization policy rule matches the request, ISE returns a deny, so the user is rejected rather than granted access. There is no implicit permit fallback in the policy set.

Why this answer

In TACACS+, authorization is a separate process from authentication. If a user authenticates successfully but no authorization policy matches, the default behavior is to reject the user — access is denied. This is because TACACS+ authorization must explicitly permit commands or services; absence of a matching rule results in a deny.

Exam trap

The trap is assuming a fallback like read-only or full access — candidates forget that TACACS+ authorization is default-deny when no policy matches.

How to eliminate wrong answers

Option A is wrong because TACACS+ does not default to read-only access; there is no implicit read-only fallback. Option B is wrong because re-authentication is not triggered by a missing authorization policy — the user is already authenticated. Option C is wrong because granting full access would be a security risk and is not the default; TACACS+ follows a default-deny model for authorization.

23
Multi-Selecthard

Which TWO methods can be used to verify that a TACACS+ request from a network device is reaching the Cisco ISE PSN?

Select 2 answers
A.Checking the Network Device Group membership list.
B.Reviewing the Operations > TACACS Livelogs in the ISE GUI.
C.Viewing the Policy Set order of precedence.
D.Executing a packet capture (TCP dump) on the ISE PSN interface.
E.Checking the switch console logs for AAA server status.
AnswersB, D

TACACS Livelogs under Operations display TACACS+ authentication and authorisation requests in real time as the PSN processes them. Seeing the device's request appear confirms it reached the PSN, satisfying the stem's verification requirement without needing CLI access.

Why this answer

Option B is correct because the Operations > TACACS Livelogs page in the ISE GUI shows TACACS+ authentication and authorization requests as they arrive at the PSN, confirming the request reached ISE. Option D is correct because running a packet capture (tcpdump) on the PSN interface lets you see the inbound TCP port 49 traffic from the network device, directly proving the TACACS+ request arrived. Option A is wrong because Network Device Group membership only defines device classification, not whether a request reached the PSN.

Option C is wrong because Policy Set order of precedence controls rule evaluation, not request arrival. Option E is wrong because switch console AAA server status shows local client-side state, not whether the request reached the ISE PSN.

Exam trap

SISE often tests the distinction between configuration-level artifacts (device groups, policy sets) and runtime evidence (Livelogs, packet captures) — candidates pick configuration screens thinking they prove traffic flow.

24
MCQeasy

Which menu path in Cisco ISE is used to define a new Network Device Group?

A.Operations > TACACS Livelogs
B.Administration > Identity Management
C.Policy > Policy Elements > Results
D.Administration > Network Resources > Network Device Groups
AnswerD

Administration > Network Resources > Network Device Groups is the exact path where Cisco ISE stores device group definitions, satisfying the requirement to define a new Network Device Group. Groups created here feed into authorisation policy conditions and device registration, so the hierarchy is available immediately for policy evaluation.

Why this answer

The correct menu path to define a new Network Device Group in Cisco ISE is Administration > Network Resources > Network Device Groups. This is where you create and manage groups that can be used to logically group network devices for policy conditions and authorization rules.

Exam trap

SISE often tests menu path memorization; candidates may confuse the Network Device Groups location with Identity Management or Policy Elements, leading to incorrect answers.

How to eliminate wrong answers

Option A is wrong because Operations > TACACS Livelogs is used to view live TACACS+ authentication and authorization logs, not to configure device groups. Option B is wrong because Administration > Identity Management is where you configure identity sources such as Active Directory, LDAP, or internal users, not network device groups. Option C is wrong because Policy > Policy Elements > Results is where you define authorization results (e.g., dACLs, VLANs, SGTs) that are referenced in policies, not network device groups.

25
Multi-Selectmedium

Which TWO of the following are true regarding TACACS+ command sets? (Choose two)

Select 2 answers
A.They support explicit 'permit' and 'deny' rules
B.They only support exact command matching
C.They are used to define the privilege level of the session
D.They are defined in the Identity store
E.They can use regular expressions for command matching
AnswersA, E

TACACS+ command sets are ordered lists of permit and deny entries applied per command or command argument, letting administrators allow specific privileged commands while blocking others. This explicit allow/deny structure is what enables granular authorisation on Cisco devices.

Why this answer

Option A is correct because TACACS+ command sets are built from explicit permit and deny statements that authorize or block specific commands (or command arguments) for a user or group after authentication and authorization succeed. Option E is correct because TACACS+ command sets support regular expression matching, allowing patterns such as 'show.*' to match multiple related commands rather than requiring each command to be listed individually. Option B is wrong because TACACS+ command matching is not limited to exact matches; it also supports regular expressions and partial/argument-based matching.

Option C is wrong because the privilege level of a session is set by the TACACS+ authorization response (for example, the 'priv-lvl' attribute), not by the command set itself. Option D is wrong because command sets are defined in the TACACS+ server's policy configuration (such as the device/group configuration on Cisco ISE or a TACACS+ daemon), not in the identity store that holds user credentials.

Exam trap

SISE often tests the misconception that TACACS+ command sets only support exact command matching, confusing them with simpler authorization methods, when in fact they support regular expressions and explicit permit/deny rules.

26
MCQeasy

You are configuring a Network Device Group in Cisco ISE to organize devices by geographical location. Which menu path should you navigate to in order to create a new Network Device Group?

A.Operations > Network Devices > Device Groups
B.Administration > Network Resources > Network Device Groups
C.Administration > System > Settings > Device Groups
D.Policy > Policy Elements > Network Device Groups
AnswerB

Network Device Groups are created under Administration > Network Resources > Network Device Groups, where hierarchical groups such as location or device type are defined and assigned. This menu path satisfies the stem's requirement to organise devices by geographical location.

Why this answer

Network Device Groups (NDGs) in Cisco ISE are created under Administration > Network Resources > Network Device Groups. This location houses the hierarchical grouping structure (e.g., Device Type, Location) used to organize network access devices for policy conditions. Navigating here lets you create new group hierarchies such as Location#All Locations#SanJose that can then be referenced in authorization policy rules.

Exam trap

SISE often tests the exact menu path for Network Device Groups, and candidates confuse it with Policy > Policy Elements or Administration > System > Settings.

How to eliminate wrong answers

Option A is wrong because Operations > Network Devices does not exist as a menu path in ISE; Operations contains Livelogs, Troubleshoot, and Dashboard views, not device configuration. Option C is wrong because Administration > System > Settings contains global system settings like SMTP, logging, and certificates, not device group definitions. Option D is wrong because Policy > Policy Elements contains reusable policy objects like authorization profiles and conditions, but Network Device Groups are defined under Administration > Network Resources, not Policy Elements.

27
MCQhard

An administrator notices that TACACS+ authentication is failing for devices. The logs show 'RADIUS request received'. What is the most likely cause?

A.The NAD is configured for RADIUS authentication instead of TACACS+.
B.The TACACS+ service is disabled on the ISE Policy Service Node.
C.The ISE policy set is missing a TACACS+ rule.
D.The shared secret between ISE and the NAD is mismatched.
AnswerA

The log entry 'RADIUS request received' indicates the NAD is sending RADIUS, not TACACS+, so ISE cannot process it as TACACS+. Reconfiguring the NAD to use TACACS+ satisfies the stem's requirement for successful TACACS+ authentication.

Why this answer

The log message 'RADIUS request received' indicates that ISE is receiving RADIUS packets, not TACACS+ packets, from the network access device. This means the NAD is configured to use RADIUS for authentication instead of TACACS+. The fix is to reconfigure the NAD to use TACACS+ (or correct the AAA server group) so that TACACS+ requests are sent to ISE.

Exam trap

The trap is focusing on ISE-side TACACS+ configuration (service, policy, secret) when the log clearly shows RADIUS traffic — the root cause is the NAD using the wrong protocol.

How to eliminate wrong answers

Option B is wrong because if the TACACS+ service were disabled on the PSN, ISE would not receive TACACS+ requests, but the log would not show 'RADIUS request received' — it would show no TACACS+ activity or a service error. Option C is wrong because a missing TACACS+ policy set would still result in TACACS+ requests being received and logged, not RADIUS requests. Option D is wrong because a shared secret mismatch would cause TACACS+ authentication failures with decryption errors, not a RADIUS request log.

28
MCQeasy

A network administrator is adding a new Cisco IOS router to Cisco ISE for TACACS+ device administration. The administrator needs to ensure that ISE recognizes the router and accepts its TACACS+ requests. What must be configured in ISE for the router?

A.Add the router as a Network Device with its IP address and shared secret.
B.Create an Authorization Policy that permits all commands.
C.Add the router to an Identity Group.
D.Configure a RADIUS server on the router pointing to ISE.
AnswerA

In Cisco ISE, each network device that communicates with ISE must be defined as a Network Device. This includes specifying the device's IP address and a shared secret. The shared secret must match the one configured on the router. Without this, ISE will not recognize the device and will reject TACACS+ requests. This is a fundamental step for device administration.

Why this answer

For Cisco ISE to accept TACACS+ requests from a router, the router must be defined as a Network Device in ISE. This configuration includes the device's IP address and a shared secret that matches the one on the router. Without this, ISE will not process the requests.

Authorization policies and other settings are applied after the device is recognized.

Exam trap

The trap here is confusing user identity groups with network device groups; network devices must be added under Network Resources, not Identity Management.

29
MCQmedium

When configuring a Shell Profile, what is the purpose of the 'Common Tasks' section?

A.To define custom protocol commands
B.To simplify configuration of standard attributes
C.To configure device-specific command sets
D.To manage user group membership
AnswerB

Common Tasks presents tick-box shortcuts for frequently used Shell Profile attributes, such as default privilege level and auto-command, so administrators avoid manually entering each TACACS+ attribute-value pair. This simplifies configuration of standard attributes, exactly as the stem describes.

Why this answer

The Common Tasks section in a Cisco ISE Shell Profile provides pre-populated, standard shell attributes (such as default privilege level, idle timeout, and session timeout) that administrators can enable with a checkbox instead of manually entering each TACACS+ AV pair. It simplifies configuration of commonly used standard attributes.

Exam trap

SISE often tests the confusion between Shell Profile Common Tasks (standard shell attributes) and Command Sets (per-command authorization), causing candidates to pick command-related answers for a shell-attribute question.

How to eliminate wrong answers

Option A is wrong because custom protocol commands are defined in Command Sets, not in the Shell Profile's Common Tasks section. Option C is wrong because device-specific command sets are separate authorization objects referenced from the Authorization Policy, not configured inside the Shell Profile. Option D is wrong because user group membership is managed in Active Directory or ISE internal identity stores, not in the Shell Profile.

30
MCQhard

A network engineer is deploying TACACS+ device administration with Cisco ISE for a large number of Cisco IOS routers. The engineer wants to centralize the authorization of commands so that users in different groups have different command privileges. The engineer has already configured authentication and authorization policy sets in ISE. Which additional configuration is required on the Cisco IOS routers to ensure that command authorization is enforced by ISE?

A.Configure 'aaa accounting commands 15 default start-stop group tacacs+' on each router.
B.Configure 'aaa authorization exec default group tacacs+ if-authenticated' on each router.
C.Configure 'tacacs-server directed-request' on each router.
D.Configure 'aaa authorization commands 15 default group tacacs+ if-authenticated' on each router.
AnswerD

This command enables command authorization for privilege level 15 commands, sending authorization requests to TACACS+ servers. The 'if-authenticated' keyword allows the command if the user has been authenticated, even if the TACACS+ server is unreachable, providing a fallback. Without this command, command authorization is not enforced, and users may execute commands based on their privilege level alone.

Why this answer

To enforce command authorization via TACACS+, the router must be configured with an AAA authorization method list for commands. The command 'aaa authorization commands 15 default group tacacs+ if-authenticated' sends authorization requests for privilege level 15 commands to ISE. The 'if-authenticated' fallback ensures that if the TACACS+ server is unreachable, commands are still allowed for authenticated users.

Without this, command authorization is not performed, and users can execute any command permitted by their privilege level.

Exam trap

The trap here is confusing EXEC authorization with command authorization; EXEC authorization only controls session establishment and privilege level assignment, not per-command enforcement.

31
MCQeasy

A network engineer is configuring a Cisco router to use TACACS+ for device administration with Cisco ISE. The engineer wants to ensure that if the TACACS+ server is unreachable, the router falls back to local authentication. Which command should be configured on the router?

A.aaa authentication login default group tacacs+ local
B.aaa authentication login default local group tacacs+
C.aaa authentication login default group tacacs+ none
D.aaa authentication login default group tacacs+ enable
AnswerA

This command configures the router to use TACACS+ first and then fall back to the local user database if the TACACS+ servers are unreachable. The 'local' keyword at the end ensures that local authentication is attempted only if the TACACS+ method fails or times out. This provides a failover mechanism.

Why this answer

The correct command is 'aaa authentication login default group tacacs+ local', which attempts TACACS+ authentication first and falls back to the local user database if TACACS+ is unavailable. The order of methods is critical: TACACS+ before local. Using 'none' would disable authentication, 'local' first would bypass TACACS+, and 'enable' would use the enable password instead of local users.

Exam trap

The trap here is reversing the order of authentication methods, such as putting 'local' before 'tacacs+', which would not provide the desired fallback behavior.

32
MCQmedium

If a user is assigned a Shell Profile with a specific 'Auto-Command' configured, what happens when they log into the network device?

A.The user is immediately disconnected
B.The user is prompted to run the command manually
C.The command is executed on the device upon login
D.The shell profile is ignored
AnswerC

The Shell Profile's Auto-Command runs automatically once authentication succeeds, satisfying the requirement that a predefined command execute at login. Cisco ISE pushes this attribute to the network device during authorisation, so the device executes it immediately without user input, which is precisely the behaviour the scenario describes.

Why this answer

When a user is assigned a Shell Profile with an 'Auto-Command' configured in Cisco ISE, that command is automatically executed on the network device immediately after the user successfully logs in via TACACS+. This is often used to restrict users to a specific menu or command, enhancing security and simplifying access.

Exam trap

SISE often tests the behavior of shell profiles; candidates may think auto-command requires manual execution or is a prompt, but it is automatically executed upon login.

How to eliminate wrong answers

Option A is wrong because the user is not disconnected; the auto-command is executed to provide a controlled session. Option B is wrong because the command is not prompted for manual execution; it runs automatically. Option D is wrong because the shell profile is not ignored; the auto-command is a feature of the shell profile and is applied upon login.

33
MCQmedium

Which statement best describes the role of the TACACS+ 'Accounting' feature?

A.It validates user credentials
B.It limits the commands a user can run
C.It encrypts the communication channel
D.It records command execution details
AnswerD

TACACS+ Accounting logs session activity, including the exact commands executed by users on network devices, plus timestamps and user identities. This command-level record-keeping distinguishes it from Authentication and Authorisation, and exceeds RADIUS accounting's typically coarser start/stop session data.

Why this answer

TACACS+ separates AAA functions into distinct roles: Authentication verifies identity, Authorization determines what a user may do, and Accounting logs what the user actually did. The Accounting feature specifically records command execution details such as the command entered, the user, timestamp, and result, sending them to the TACACS+ server for auditing. This makes it the mechanism for tracking administrative activity on network devices.

Exam trap

SISE often tests the confusion between the three AAA components — candidates frequently pick Authorization (command limiting) when the question actually asks about Accounting (logging/auditing).

How to eliminate wrong answers

Option A is wrong because validating user credentials is the function of TACACS+ Authentication, not Accounting. Option B is wrong because limiting which commands a user can run is the function of TACACS+ Authorization (via command sets), not Accounting. Option C is wrong because encryption of the TACACS+ communication channel is a transport-layer property of the protocol itself (TACACS+ encrypts the entire payload using a shared secret), not a function of the Accounting feature.

34
Multi-Selecthard

Which THREE items are configurable within a TACACS+ Shell Profile in Cisco ISE?

Select 3 answers
A.Shared Secret
B.RADIUS Service Type
C.Idle Timeout
D.Default Privilege Level
E.Auto-command
AnswersC, D, E

Idle Timeout is configurable in a TACACS+ Shell Profile, defining how long an authenticated session may remain inactive before the device terminates it. This satisfies the stem's requirement for a shell-profile attribute, alongside privilege level and auto-command.

Why this answer

In Cisco ISE, a TACACS+ Shell Profile defines the authorization attributes returned to a network device for a shell session, and it includes the Idle Timeout (C), which sets the inactivity period in minutes before the session is terminated, the Default Privilege Level (D), which assigns the initial privilege level (0-15) for the user's EXEC session, and the Auto-command (E), which specifies a command to run automatically upon login. These three attributes are all configurable fields within the Shell Profile's authorization settings. The Shared Secret (A) is not part of a Shell Profile; it is configured on the TACACS+ device/network access device definition to secure communication between ISE and the NAD.

The RADIUS Service Type (B) is a RADIUS authorization attribute and is not applicable to TACACS+ shell profiles, which use TACACS+ AV pairs instead.

Exam trap

SISE often tests whether candidates confuse TACACS+ Shell Profile attributes with RADIUS attributes or global TACACS+ settings like the Shared Secret, catching those who blur the two protocols.

35
MCQmedium

You are configuring a TACACS+ command set to restrict an administrator from running 'show running-config' on Cisco switches. Which match condition ensures that this specific command is blocked while allowing other 'show' commands?

A.Deny 'show' and permit 'show running-config'
B.Deny 'show running-config' and permit all other commands
C.Permit 'show.*' and deny 'show running-config'
D.Set the command privilege level to 0
AnswerB

TACACS+ command sets evaluate commands sequentially, so explicitly denying 'show running-config' before permitting the remaining 'show' commands blocks only that variant. Ordering matters: a broad permit placed first would authorise the restricted command before the deny is reached.

Why this answer

To block a specific command like 'show running-config' while allowing other 'show' commands, the command set must explicitly deny 'show running-config' and then permit all other commands. TACACS+ command sets are evaluated top-down, so the deny rule for the specific command must come before a permit-all rule. This ensures only that command is blocked.

Exam trap

The trap is rule ordering — candidates forget that TACACS+ command sets are first-match and place the permit-all rule before the specific deny, which allows the blocked command.

How to eliminate wrong answers

Option A is wrong because denying 'show' and permitting 'show running-config' would block all show commands except the one you want to block, which is the opposite of the requirement. Option C is wrong because permitting 'show.*' first would allow 'show running-config' before the deny rule is evaluated, since TACACS+ processes rules in order. Option D is wrong because setting privilege level 0 does not block a specific command; it changes the privilege level and does not provide granular command filtering.

36
Multi-Selectmedium

Which TWO of the following are true about Shell Profiles? (Choose two)

Select 2 answers
A.They replace the need for accounting
B.They can include custom attributes for specific vendors
C.They define the command set to be used
D.They define the initial privilege level
E.They are used for RADIUS authentication only
AnswersB, D

Shell Profiles support vendor-specific attributes, letting you define custom RADIUS dictionary entries for non-standard attributes that particular network access devices require. This satisfies the stem's constraint by extending authorisation beyond built-in attributes, enabling granular policy enforcement for third-party vendors whose attributes Microsoft Entra ID does not natively recognise.

Why this answer

Shell Profiles in Cisco ISE (TACACS+) are policy elements that define the authorization attributes returned to a network device after successful authentication. Option B is correct because Shell Profiles can include custom attributes (such as Cisco AV pairs) tailored to specific vendors, allowing device-specific authorization behavior. Option D is correct because Shell Profiles define the initial privilege level (for example, privilege level 15) assigned to the user's session upon login.

Option A is incorrect because accounting is a separate TACACS+ function that logs user activity and is not replaced by Shell Profiles. Option C is incorrect because the command set is defined by Command Sets, not Shell Profiles, although both are authorization policy elements. Option E is incorrect because Shell Profiles are used with TACACS+ authorization, not exclusively with RADIUS authentication.

Exam trap

The trap is confusing shell profiles with command sets or accounting. Candidates might think shell profiles define the command set, but that's a separate configuration. Also, shell profiles are for TACACS+, not RADIUS.

37
MCQmedium

How does Cisco ISE handle requests that do not match any configured TACACS+ Authorization Policy?

A.It defaults to local switch authentication
B.It prompts the user to select a profile
C.It permits access with default privileges
D.It denies access
AnswerD

Unmatched TACACS+ authorisation requests trigger ISE's implicit deny, returning an ACCESS-REJECT to the network device. This satisfies the default-deny constraint: no explicit rule means no authorisation, so the session cannot proceed. Unlike authentication, authorisation requires a matching policy set; absent one, ISE withholds all privileges rather than permitting fallback access.

Why this answer

Cisco ISE uses a default-deny model for TACACS+ authorization: if an authorization request does not match any configured policy rule, ISE returns a deny, and the device will not grant the requested command or privilege. This mirrors the implicit deny at the end of an ACL and ensures no unauthorized access is granted by omission.

Exam trap

SISE often tests the implicit deny in TACACS+ authorization, so candidates who assume ISE 'fails open' or falls back to local authentication on a policy miss will choose the wrong answer.

How to eliminate wrong answers

Option A is wrong because ISE does not fall back to local switch authentication on a policy miss; local fallback only occurs if the device is configured for it and ISE is unreachable, not when a policy simply does not match. Option B is wrong because TACACS+ authorization is a machine-to-machine exchange with no interactive prompt to select a profile. Option C is wrong because permitting access with default privileges would be a fail-open behavior, which contradicts ISE's default-deny authorization model.

38
MCQmedium

When adding a network device to ISE, you select the 'TACACS+ Authentication Settings' checkbox. What is the impact of this action?

A.It enables RADIUS for this device
B.It enables TACACS+ services for this device
C.It forces the switch to use SNMP
D.It automatically configures the switch via CLI
AnswerB

Ticking TACACS+ Authentication Settings on the network device entry activates the TACACS+ shared secret and service for that node, allowing it to send device-administration authentication requests to ISE. Without it, only RADIUS-based services are processed for that device.

Why this answer

When adding a network device in ISE, checking the 'TACACS+ Authentication Settings' checkbox enables TACACS+ services for that device, allowing ISE to process TACACS+ authentication, authorization, and accounting requests from it. This is separate from RADIUS configuration, which is controlled by the RADIUS settings on the same device entry. Enabling TACACS+ is a prerequisite for using ISE for device administration (AAA) on that network device.

Exam trap

SISE often tests the confusion between RADIUS and TACACS+ enablement on a network device, where the TACACS+ checkbox only enables TACACS+ services, not RADIUS.

How to eliminate wrong answers

Option A is wrong because the checkbox specifically enables TACACS+, not RADIUS; RADIUS is enabled via a separate RADIUS settings section on the device configuration. Option C is wrong because SNMP is a monitoring protocol and is not enabled or forced by the TACACS+ checkbox. Option D is wrong because ISE does not automatically configure the switch via CLI; the checkbox only enables ISE to accept TACACS+ requests from the device, and the device must be manually configured to point to ISE.

39
Multi-Selecthard

When setting up TACACS+ for network administration, which THREE configurations must be present on the Cisco network device? (Choose three)

Select 3 answers
A.AAA authentication/authorization commands
B.Local user database for all commands
C.RADIUS server configuration
D.Shared secret matching the ISE configuration
E.TACACS+ server group configuration
AnswersA, D, E

AAA commands define which method lists apply to login and exec sessions, directing the device to consult TACACS+ for authentication and authorisation. They are the enforcement point that activates the configured server group on the network device.

Why this answer

Option A is correct because the device must be configured with AAA commands such as 'aaa new-model' and 'aaa authentication login' / 'aaa authorization exec' to actually invoke TACACS+ for administrative access. Option D is correct because the TACACS+ shared secret (key) configured on the Cisco device must exactly match the key configured on the ISE/TACACS+ server, otherwise authentication packets are rejected. Option E is correct because you must define a TACACS+ server group (e.g., 'aaa group server tacacs+') and add the TACACS+ server host(s) to it so the AAA method lists can reference that group.

Option B is not required because a local user database is only a fallback for when the TACACS+ server is unreachable, not a mandatory part of TACACS+ administration. Option C is not required because RADIUS is a separate AAA protocol and is not needed when implementing TACACS+.

Exam trap

SISE often tests the required TACACS+ device-side configuration elements, and candidates mistakenly include optional local fallback or confuse RADIUS server configuration with TACACS+ server group configuration.

Ready to test yourself?

Try a timed practice session using only Network Access Device Administration questions.