Courseiva

CCNA Profiler Questions

36 questions · Profiler · All types, answers revealed

1
MCQmedium

When setting up a custom endpoint identity group for printers, what is the best practice for assigning devices to that group?

A.Manually add every printer MAC address to the group.
B.Use a Profiling Policy to automatically assign the device to the 'Printers' Identity Group.
C.Import a CSV file periodically.
D.Use an Authorization Policy to bypass profiling.
AnswerB

A Profiling Policy applies matching rules to discovered endpoints and places them into the correct identity group automatically, removing manual assignment errors. This satisfies the best-practise requirement for scalable, consistent printer onboarding in Cisco ISE.

Why this answer

The best practice for assigning devices to a custom endpoint identity group is to use a Profiling Policy. Profiling policies automatically classify endpoints based on collected attributes (e.g., DHCP, HTTP, SNMP) and assign them to the appropriate identity group. This ensures dynamic and scalable management, reducing manual effort and errors.

Exam trap

The trap here is thinking that manual or CSV-based methods are acceptable for large-scale deployments. Candidates might choose manual addition because it seems straightforward, but the best practice is automation through profiling policies.

How to eliminate wrong answers

Option A is wrong because manually adding every printer MAC address is not scalable and prone to error, especially in large networks. Option C is wrong because importing a CSV file periodically is a manual process that does not automatically adapt to changes and can become outdated. Option D is wrong because using an Authorization Policy to bypass profiling does not assign devices to the group; it simply skips profiling, which defeats the purpose of classification.

2
Multi-Selectmedium

Which THREE of the following are true regarding the Cisco ISE Profiler Feed Service?

Select 3 answers
A.It automatically assigns devices to groups.
B.It can be configured to update automatically on a schedule.
C.It downloads updated profiling policies from Cisco.
D.It is mandatory for all deployments.
E.It requires internet access for the PAN node.
AnswersB, C, E

Feed updates can be scheduled, letting the PAN poll Cisco's servers at defined intervals rather than manually triggering each download. This automatic scheduling satisfies the stem by confirming the feed supports recurring, unattended policy refreshes.

Why this answer

Option B is correct because the Profiler Feed Service can be scheduled to poll Cisco's update servers automatically at a configured interval (for example, daily or weekly) so that endpoint profile policies stay current without manual intervention. Option C is correct because the service's core function is to download updated profiling policies and Cisco-provided endpoint profile definitions from Cisco's feed servers to the ISE deployment. Option E is correct because the Policy Administration Node (PAN) is the node that contacts the external Cisco feed servers, so it requires outbound internet access (HTTPS/443) to retrieve those updates.

Option A is not correct because the feed service only supplies profile/policy updates; actual assignment of endpoints to identity groups is performed by ISE's profiling engine and authorization policies, not by the feed itself. Option D is not correct because the Profiler Feed Service is optional — ISE can profile endpoints using built-in and custom policies without ever enabling the feed service.

Exam trap

SISE often tests the misconception that the Profiler Feed Service automatically assigns endpoints to groups or is required for profiling to work, when in fact it only downloads policy updates and is optional.

3
MCQmedium

Which probe is most effective for identifying the specific operating system and browser type of an endpoint connecting via a web portal?

A.HTTP probe
B.DHCP probe
C.MAC OUI probe
D.DNS probe
AnswerA

The HTTP probe inspects the User-Agent string within HTTP traffic, revealing the endpoint's operating system and browser type. This satisfies the stem's web-portal scenario, where HTTP is the only traffic available, unlike NetFlow or DHCP probes.

Why this answer

The HTTP probe is the most effective for identifying OS and browser type because it collects User-Agent strings and other HTTP headers sent by the endpoint's browser during web portal authentication. These headers contain detailed information about the operating system, browser name, and version, which ISE uses to match profiling policies. No other probe provides this level of browser-specific detail.

Exam trap

SISE often tests whether candidates confuse the DHCP probe (which identifies OS via DHCP fingerprinting) with the HTTP probe (which identifies browser and OS via User-Agent) — the question specifically asks for browser type, which only HTTP provides.

How to eliminate wrong answers

Option B is wrong because the DHCP probe collects DHCP fingerprint data (option 55 parameter request list, hostname, etc.), which can identify the OS but not the browser. Option C is wrong because the MAC OUI probe only identifies the hardware manufacturer from the first three bytes of the MAC address — it cannot determine OS or browser. Option D is wrong because the DNS probe captures DNS queries and can infer some application behavior, but it does not reveal browser type or OS version.

4
MCQmedium

A user reports that a device was incorrectly identified as a 'Cisco IP Phone' when it is actually a 'Cisco Access Point'. Which troubleshooting step should you take first?

A.Check the endpoint attributes in Context Visibility to see why it matched that policy.
B.Re-register the device.
C.Delete all profiling policies.
D.Restart the ISE node.
AnswerA

Context Visibility shows the endpoint's profiled attributes and the matching policy, revealing which probe or condition classified it as a Cisco IP Phone. Inspecting this first identifies the misclassification source before editing profiles or policies.

Why this answer

The first troubleshooting step is to check the endpoint's attributes in Context Visibility, which shows the collected profiling attributes, the matched profiling policies, and the confidence scores that led to the 'Cisco IP Phone' classification. This reveals whether the misclassification is due to incorrect attributes (e.g., a stale MAC OUI match) or an overly broad profiling policy, allowing targeted correction.

Exam trap

The trap is jumping to disruptive fixes (re-register, restart, delete policies) instead of using ISE's built-in diagnostic tool (Context Visibility) to identify the root cause of the misclassification.

How to eliminate wrong answers

Option B is wrong because re-registering the device does not address the root cause of misclassification and may disrupt the endpoint's current session. Option C is wrong because deleting all profiling policies is a destructive action that would break profiling for every endpoint, not just the misidentified one. Option D is wrong because restarting the ISE node is a disruptive, non-targeted action that does not diagnose or fix the profiling logic.

5
Multi-Selectmedium

Which THREE of the following are common reasons why an endpoint would be listed as 'Unknown' in Cisco ISE?

Select 3 answers
A.The device is connected to a non-Cisco switch.
B.The endpoint is not using 802.1X.
C.The endpoint has not generated enough traffic to trigger a probe.
D.The necessary probes are disabled on the PSN.
E.No profiling policies match the collected attributes.
AnswersC, D, E

Insufficient traffic means no probe—SNMP, RADIUS, DHCP, or AD—has observed the endpoint, so profiling cannot assign an identity group. Cisco ISE requires collected attributes before classification; without them the endpoint remains Unknown, satisfying the stem's scenario of missing profiling data.

Why this answer

Option C is correct because Cisco ISE profiling relies on collecting attributes from network traffic and other sources; if an endpoint has not generated enough traffic, insufficient attributes are gathered and the endpoint remains in the Unknown state. Option D is correct because profiling probes (such as SNMP, DHCP, RADIUS, NetFlow, and HTTP) must be enabled on the Policy Services Node (PSN); if the required probes are disabled, ISE cannot collect the endpoint attributes needed to identify it. Option E is correct because even when attributes are collected, ISE must match them against configured profiling policies; if no profiling policy matches the collected attributes, the endpoint is classified as Unknown.

Option A is not necessarily correct because ISE can profile endpoints on non-Cisco switches using probes like DHCP, RADIUS, and NetFlow, so the switch vendor alone does not cause Unknown status. Option B is not necessarily correct because ISE can profile endpoints that do not use 802.1X through other probes such as DHCP, SNMP, and NetFlow, so lack of 802.1X alone does not make an endpoint Unknown.

Exam trap

SISE often tests whether candidates conflate authentication requirements with profiling requirements — 802.1X and Cisco-only infrastructure are authentication concerns, not profiling prerequisites, so they are classic distractors.

6
MCQmedium

Which probe is required to collect the 'User-Agent' string from a web browser to assist in profiling a device as a workstation?

A.HTTP
B.RADIUS
C.DHCP
D.DNS
AnswerA

HTTP probes capture the browser's User-Agent header directly during web requests, satisfying the stem's requirement to profile the device as a workstation. RADIUS and SNMP cannot read HTTP headers, and NetFlow records only metadata. HTTP is therefore the only listed probe that exposes the User-Agent string.

Why this answer

The HTTP probe in ISE collects attributes from HTTP traffic, including the User-Agent string sent by web browsers. This string (e.g., 'Mozilla/5.0 ... Windows NT 10.0 ...') is a key fingerprint used to profile a device as a workstation.

Without the HTTP probe, ISE would not see the User-Agent and would have to rely on other probes like DHCP or RADIUS, which do not carry that information.

Exam trap

The trap is confusing which probe collects which attribute — candidates may incorrectly select DHCP or RADIUS for User-Agent, when only the HTTP probe can see HTTP headers.

How to eliminate wrong answers

Option B is wrong because the RADIUS probe collects authentication attributes (username, MAC, NAS port, etc.) but does not inspect HTTP headers like User-Agent. Option C is wrong because the DHCP probe collects DHCP options (hostname, vendor class, parameter request list) but not the browser's User-Agent string. Option D is wrong because the DNS probe collects DNS query and response data (e.g., reverse lookups, domain names) but does not see HTTP headers.

7
MCQeasy

A network administrator is configuring Cisco ISE profiling for a new branch office. The administrator wants to ensure that endpoints are profiled based on information collected from DHCP packets. Which probe must be enabled on the Policy Service node to collect DHCP attributes?

A.DHCP probe
B.SNMP probe
C.HTTP probe
D.RADIUS probe
AnswerA

The DHCP probe captures DHCP packets to extract attributes such as hostname, vendor class identifier, and requested parameters. These attributes are used by the profiling engine to classify endpoints. Enabling the DHCP probe on the Policy Service node is necessary to collect DHCP-based profiling data, making it the correct choice for this scenario.

Why this answer

The DHCP probe is specifically designed to capture DHCP packets and extract attributes like hostname, vendor class, and requested parameters. These attributes are then used by the profiling engine to classify endpoints. For profiling based on DHCP information, enabling the DHCP probe on the Policy Service node is required.

Exam trap

The trap here is confusing the RADIUS probe with the DHCP probe; while both collect endpoint attributes, only the DHCP probe captures DHCP options used for profiling.

8
MCQmedium

You are configuring a DHCP probe on a Cisco ISE node to identify endpoints. Which specific configuration step is required to ensure the ISE node receives DHCP traffic when the client and server are on a different subnet?

A.Configure a DHCP relay agent on the ISE node itself.
B.Enable DHCP Server mode on the Cisco ISE Profiling service.
C.Configure an IP helper-address on the Layer 3 device for the client VLAN pointing to the ISE node.
D.Enable DHCP Snooping on the ISE node interface.
AnswerC

DHCP broadcasts stay within the client subnet, so the Layer 3 device must relay them. An IP helper-address on the client VLAN forwards those requests to the ISE node, letting the probe receive traffic from endpoints on a different subnet.

Why this answer

To ensure the ISE node receives DHCP traffic when the client and DHCP server are on different subnets, you must configure an IP helper-address on the Layer 3 device (e.g., router or switch) for the client VLAN, pointing to the ISE node. This relays DHCP packets to ISE, allowing the DHCP probe to collect profiling data. Thus, option C is correct.

Exam trap

The trap is thinking ISE can relay DHCP or that DHCP snooping can forward packets, when actually an IP helper-address on the network device is required.

How to eliminate wrong answers

Option A is wrong because ISE cannot act as a DHCP relay agent; it only listens for DHCP traffic. Option B is wrong because enabling DHCP Server mode on ISE is not required and would conflict with existing DHCP servers. Option D is wrong because DHCP Snooping is a switch feature that filters DHCP traffic, not a relay mechanism, and ISE does not support it on its interface.

9
MCQmedium

You are configuring a custom profiling policy and notice that the 'Certainty Factor' is too low for the device to be assigned to the correct group. What is the purpose of the Certainty Factor in ISE?

A.To determine the priority of the profiling policy.
B.To force the device to re-authenticate.
C.To indicate the confidence level that the device is correctly profiled.
D.To limit the number of devices in an endpoint group.
AnswerC

The Certainty Factor is a numeric score expressing how confident the profiling conditions are that a device matches an endpoint profile. A low value means the collected attributes are inconclusive, so ISE withholds assignment to the correct group until confidence rises.

Why this answer

The Certainty Factor in ISE is a numerical value (0-100) that represents how confident the profiling engine is that a device belongs to a particular profile. It is calculated based on the number and weight of matched conditions in the profiling policy. A higher certainty factor increases the likelihood that the device will be assigned to the correct group, while a low certainty factor indicates that the collected attributes do not strongly match any profile.

Exam trap

SISE often tests the misconception that Certainty Factor determines policy priority or is used to force reauthentication, when in fact it solely indicates confidence in the profiling result.

How to eliminate wrong answers

Option A is wrong because priority of profiling policies is determined by the order of policies in the policy list, not by the Certainty Factor. Option B is wrong because forcing re-authentication is done through CoA (Change of Authorization) or reauthentication timers, not via Certainty Factor. Option D is wrong because limiting the number of devices in an endpoint group is not a function of the Certainty Factor; endpoint group membership is not limited by this value.

10
MCQmedium

When configuring an SNMP Query probe, why is it recommended to use SNMPv3 instead of SNMPv1/v2c?

A.SNMPv3 is the only version supported by ISE.
B.SNMPv3 is faster.
C.SNMPv3 provides authentication and encryption for the query.
D.SNMPv3 eliminates the need for a community string.
AnswerC

SNMPv3 adds user-based authentication (SHA/MD5) and payload encryption (AES/DES) via the USM and VACM modules, which SNMPv1 and v2c lack entirely. This satisfies the stem's security requirement, preventing credential interception and spoofed responses during queries.

Why this answer

SNMPv3 is recommended over SNMPv1/v2c for SNMP Query probes because it provides authentication and encryption, ensuring that the queries and responses are secure. SNMPv1/v2c use plaintext community strings, which are vulnerable to eavesdropping and unauthorized access. SNMPv3 also supports stronger security models like USM (User-based Security Model).

Exam trap

SISE often tests the misconception that SNMPv3 eliminates community strings entirely or is the only supported version, when in fact it replaces them with user-based credentials and ISE supports multiple versions.

How to eliminate wrong answers

Option A is wrong because ISE supports SNMPv1, v2c, and v3; SNMPv3 is not the only version supported. Option B is wrong because SNMPv3 is not inherently faster; in fact, the added security overhead can make it slightly slower. Option D is wrong because SNMPv3 does not eliminate the need for a community string; it replaces community strings with user-based credentials (username, authentication password, privacy password), but it still requires configuration of those credentials.

11
MCQmedium

What is the function of the 'RADIUS Accounting' probe in the profiling process?

A.To encrypt the session.
B.To collect device attributes contained in RADIUS accounting packets.
C.To act as a RADIUS server.
D.To authenticate the device.
AnswerB

The RADIUS Accounting probe parses accounting packets sent by network devices, extracting attributes such as endpoint identifiers and device details. These attributes feed the profiling engine, satisfying the need to identify and classify endpoints from RADIUS accounting data.

Why this answer

It collects session information from the RADIUS traffic, providing start/stop and attribute data useful for device identification.

12
Multi-Selecthard

A security engineer is configuring a Cisco ISE profiling policy to identify and authorize endpoints. The engineer wants to use the SNMP Query probe to gather attributes from network devices. Which two statements are true regarding the SNMP Query probe in Cisco ISE? (Choose two.)

Select 2 answers
A.The SNMP Query probe can collect attributes such as CDP neighbors and ARP tables from network devices.
B.The SNMP Query probe automatically discovers all network devices and adds them to ISE without manual configuration.
C.The SNMP Query probe requires the network device to have SNMP read-write access enabled for ISE to retrieve data.
D.The SNMP Query probe can be used to profile endpoints that are not directly connected to a Cisco switch, such as wireless clients.
E.The SNMP Query probe can only retrieve attributes from Cisco devices that are running IOS XE.
AnswersA, D

The SNMP Query probe in Cisco ISE can query network devices using SNMP to retrieve information like CDP neighbor details, ARP tables, MAC address tables, and other MIB objects. This data helps profile endpoints by associating them with switch ports and VLANs. It is especially useful when device sensor or other probes are not available. The probe uses SNMP read-only community strings or SNMPv3 credentials configured in ISE to poll the devices.

Why this answer

The SNMP Query probe in Cisco ISE is a powerful profiling method that polls network devices using SNMP read-only credentials to gather endpoint attributes. It can retrieve data such as CDP neighbors, ARP tables, and MAC address tables from switches, and can also query wireless controllers to profile wireless clients. It requires manual configuration of network devices in ISE, including IP addresses and SNMP credentials.

It does not require read-write access, nor does it automatically discover devices. It is not limited to Cisco IOS XE devices, as it can work with any SNMP-enabled device.

Exam trap

The trap here is assuming that the SNMP Query probe requires read-write access or only works with Cisco IOS XE devices, when in fact it only needs read-only access and supports a wide range of SNMP-enabled devices.

13
MCQmedium

Which component of the Cisco ISE Profiling architecture is responsible for comparing collected attributes against defined profiling policies?

A.Monitoring Node (MnT)
B.Feed Service
C.Administration Node (PAN)
D.Policy Service Node (PSN) Profiler Service
AnswerD

The PSN Profiler Service evaluates endpoint attributes collected by probes against the profiling policies, then assigns the matching endpoint profile. This satisfies the stem's requirement for the comparison component, since probes only gather raw data and the PAN neither collects nor matches attributes locally.

Why this answer

The Policy Service Node (PSN) Profiler Service is responsible for collecting endpoint attributes and comparing them against profiling policies to determine the device profile. The PSN hosts the profiler service, which includes the profiling engine that evaluates conditions and assigns certainty factors. The PAN (Administration Node) manages the configuration and policies, but the actual profiling decision is made by the PSN.

Exam trap

SISE often tests the confusion between the PAN's role in policy management and the PSN's role in policy execution, leading candidates to incorrectly select the PAN for profiling decisions.

How to eliminate wrong answers

Option A is wrong because the Monitoring Node (MnT) is responsible for logging, reporting, and troubleshooting, not for comparing attributes against policies. Option B is wrong because the Feed Service is a component that downloads updated profiling policies from Cisco, but it does not perform the comparison. Option C is wrong because the Administration Node (PAN) is the management interface for configuration and policy creation, but it does not execute the profiling logic; that is done by the PSN.

14
MCQhard

You need to profile IoT devices that only support mDNS. Which probe should you enable?

A.mDNS probe
B.DHCP probe
C.SNMP Query probe
D.HTTP probe
AnswerA

The mDNS probe resolves multicast DNS queries on UDP port 5353, which is the only discovery protocol these IoT devices support. Enabling it lets Cisco Identity Services Engine profile them by parsing their mDNS service advertisements, satisfying the stem's constraint that devices support mDNS exclusively.

Why this answer

For IoT devices that only support mDNS (Multicast DNS, used by Bonjour, Chromecast, AirPrint, and similar services), the mDNS probe is the correct choice because it captures mDNS traffic and extracts service and device attributes for profiling. Enabling the mDNS probe allows ISE to identify devices that don't participate in DHCP fingerprinting or RADIUS-based profiling.

Exam trap

SISE often tests whether candidates know which probe maps to which protocol — the trap is selecting a general-purpose probe (DHCP, HTTP) when the device only speaks a specific protocol like mDNS.

How to eliminate wrong answers

Option B is wrong because the DHCP probe requires the device to request an IP via DHCP and send identifiable options — mDNS-only IoT devices may use static IPs or minimal DHCP requests. Option C is wrong because SNMP Query polls network devices for MAC/ARP tables, which doesn't capture mDNS service advertisements. Option D is wrong because the HTTP probe inspects HTTP User-Agent strings, which mDNS-only devices typically don't generate.

15
Multi-Selecthard

Which TWO of the following are necessary to successfully profile devices using the SNMP Query probe?

Select 2 answers
A.SNMP Write community string configured on the device.
B.LLDP-MED enabled on the endpoint.
C.Read access to the MIBs on the target device.
D.SNMP community string or credentials defined in ISE.
E.A static IP address on the target device.
AnswersC, D

The SNMP Query probe reads object identifiers from the device's management information base to gather profiling attributes. Read access to those MIBs is therefore required; without it queries return errors and no endpoint data is collected.

Why this answer

Option C is correct because the SNMP Query probe in Cisco ISE reads information from the device's Management Information Base (MIB) objects to identify attributes such as sysDescr, sysObjectID, and interface details, so read access to those MIBs on the target device is required for profiling to succeed. Option D is correct because ISE must be configured with the matching SNMP community string (for SNMPv1/v2c) or SNMPv3 credentials (username, authentication, and privacy settings) that the target device accepts, otherwise the query will be rejected and no profiling data will be returned. Option A is not needed because SNMP Query profiling only performs read operations (GET/GET-NEXT/GET-BULK); write access is never used.

Option B is not needed because LLDP-MED is an entirely separate profiling method (used by the LLDP-MED probe via CDP/LLDP neighbor data), not part of SNMP Query. Option E is not needed because SNMP Query can target any reachable device by IP address, whether statically assigned or obtained via DHCP.

Exam trap

SISE often tests the misconception that SNMP write access or LLDP-MED is required for SNMP Query profiling, when in fact only read access and credentials are needed.

16
MCQmedium

You need to ensure that only specific ISE nodes perform the NMAP scan probe. Where is this configured?

A.Administration > System > Settings > Profiling Feed
B.Policy > Profiling > Profiling Policies
C.Administration > System > Deployment > [Node Name] > Profiling Configuration
D.Policy > Policy Elements > Results
AnswerC

Profiling configuration is set per node under Administration > System > Deployment, selecting the node and enabling the NMAP scan probe there. This node-level setting ensures only the chosen ISE nodes run the scan, satisfying the requirement to restrict probe execution.

Why this answer

NMAP scan probe enablement is configured per-PSN under Administration > System > Deployment > [Node Name] > Profiling Configuration. This is where you enable or disable individual probes (NMAP, DHCP, RADIUS, SNMP, NetFlow, etc.) on a specific ISE node, allowing you to restrict scanning to dedicated PSNs rather than every node in the deployment.

Exam trap

SISE often tests the distinction between global profiling settings (feeds, policies) and per-node probe configuration, catching candidates who assume probe enablement is a global policy setting.

How to eliminate wrong answers

Option A is wrong because Administration > System > Settings > Profiling Feed controls the download of Cisco-provided OUI and profile feed updates, not per-node probe enablement. Option B is wrong because Policy > Profiling > Profiling Policies defines the matching conditions and policies that assign endpoints to identity groups — it does not control which node runs the NMAP probe. Option D is wrong because Policy > Policy Elements > Results contains reusable authorization results such as authorization profiles and downloadable ACLs, which are unrelated to probe configuration.

17
MCQhard

A security administrator is troubleshooting why a particular endpoint is being profiled as a generic 'Windows Workstation' instead of the more specific 'Windows 10 Enterprise' policy. The administrator checks the Profiling Policies and sees that the 'Windows 10 Enterprise' policy has a minimum certainty factor of 20, while the endpoint's current certainty factor is 18. The administrator also notices that the endpoint has matching attributes for both policies. What is the most likely reason the endpoint is not matching the more specific policy?

A.The endpoint's MAC address is not in the OUI database.
B.The minimum certainty factor for the 'Windows 10 Enterprise' policy is higher than the endpoint's current certainty factor.
C.The endpoint has not been assigned to the correct Endpoint Identity Group.
D.The 'Windows 10 Enterprise' policy is disabled.
AnswerB

Each profiling policy has a minimum certainty factor that must be met or exceeded for the policy to be considered a match. If the endpoint's accumulated certainty factor is 18 and the policy requires 20, the policy will not be selected. Instead, a less specific policy with a lower threshold, such as 'Windows Workstation', may match, explaining the observed behavior.

Why this answer

Profiling policies use a minimum certainty factor to determine whether an endpoint qualifies for that policy. When multiple policies match, the one with the highest certainty factor that meets its minimum threshold is selected. Here, the endpoint's certainty factor of 18 is below the required 20 for the Windows 10 Enterprise policy, so ISE falls back to a less specific policy with a lower threshold.

Exam trap

The trap here is thinking that having matching attributes alone is sufficient, when in fact the accumulated certainty factor must also meet the policy's minimum threshold.

18
Multi-Selecthard

A network security engineer is configuring profiling policies in Cisco ISE to identify and classify endpoints. The engineer wants to ensure that the profiling policies correctly match endpoints based on multiple conditions. Which two statements are true regarding profiling policy conditions and certainty factors? (Choose two.)

Select 2 answers
A.The minimum certainty factor of a profiling policy must be equal to the sum of all condition certainty factors.
B.When multiple profiling policies match, ISE selects the policy with the highest cumulative certainty factor that meets its minimum threshold.
C.A profiling policy can contain multiple conditions, and each condition can have a different certainty factor.
D.Profiling policies can only use a single condition; multiple conditions require separate policies.
E.Certainty factors are only applied to the first matching condition in a policy.
AnswersB, C

Cisco ISE evaluates all profiling policies and calculates a cumulative certainty factor for each based on matched conditions. If a policy's cumulative certainty factor meets or exceeds its minimum threshold, it becomes a candidate. Among all candidates, ISE selects the policy with the highest cumulative certainty factor. This ensures the most specific match is chosen, assuming it meets its threshold.

Why this answer

Profiling policies in Cisco ISE can include multiple conditions, each with its own certainty factor, and the cumulative certainty factor is compared against the policy's minimum threshold. When several policies match, the one with the highest cumulative certainty factor that meets its threshold is selected. These mechanisms allow granular and accurate endpoint classification.

Exam trap

The trap here is assuming that the minimum certainty factor must equal the sum of all condition certainty factors, when it is actually a threshold that can be lower to allow partial matches.

19
MCQmedium

You have created a custom profiler condition that is not matching endpoints correctly. Where should you check the live authentication and profiling logs to verify if the attribute is being received by ISE?

A.Administration > System > Logging
B.Operations > RADIUS Livelogs
C.Policy > Profiling > Profiling Policies
D.Context Visibility > Endpoints
AnswerB

RADIUS Livelogs capture live authentication and authorisation exchanges, showing the actual attributes received from the network access device. Inspecting them confirms whether the profiler condition's attribute arrives and with what value, exposing mismatches that prevent correct endpoint matching.

Why this answer

RADIUS Livelogs under Operations is the real-time troubleshooting view in ISE that shows authentication and authorization requests as they arrive, including the RADIUS attributes (Cisco AV pairs, Calling-Station-ID, etc.) that the NAD sends. When a custom profiler condition fails to match, you need to confirm whether the attribute the condition depends on is actually being received from the network device. RADIUS Livelogs displays the raw attribute payload of each Access-Request, so you can verify attribute presence, spelling, and value before blaming the profiling policy.

Exam trap

SISE often tests the distinction between where you configure a feature (policy, settings) versus where you observe live protocol data — candidates pick the policy page when the question is really asking for the real-time troubleshooting tool.

How to eliminate wrong answers

Option A is wrong because Administration > System > Logging only configures logging targets, severity levels, and local log settings — it does not display live authentication or attribute data. Option C is wrong because Policy > Profiling > Profiling Policies is where you define the conditions and rules themselves, not where you observe whether attributes are arriving from the NAD. Option D is wrong because Context Visibility > Endpoints shows the resulting endpoint inventory and profile assignments after processing, not the raw incoming RADIUS attributes needed to debug a non-matching condition.

20
MCQmedium

You are troubleshooting an issue where IP phones are not being profiled. The SNMP read community string on the switch does not match the one configured in ISE. What is the expected behavior?

A.The endpoint will be profiled based on the MAC OUI only.
B.The SNMP trap probe will still work.
C.The SNMP Query probe will fail to collect CDP/LLDP data from the switch.
D.ISE will automatically update the community string on the switch.
AnswerC

The SNMP Query probe authenticates to the switch using the configured read community string. A mismatch causes the switch to reject the request, so the probe cannot retrieve CDP or LLDP neighbour data and profiling fails.

Why this answer

The SNMP Query probe in ISE polls the switch via SNMP to retrieve CDP/LLDP neighbor data for profiling. If the SNMP read community string configured in ISE does not match the switch, the SNMP query fails and ISE cannot collect that CDP/LLDP data, so profiling is degraded or fails. This is the expected behavior described in option C.

Exam trap

SISE often tests the distinction between SNMP Query and SNMP Trap probes; candidates assume a community string mismatch affects traps, but traps are outbound from the switch and do not depend on ISE's read community string.

How to eliminate wrong answers

Option A is wrong because MAC OUI alone provides only vendor-level profiling, not the rich CDP/LLDP data the SNMP Query probe is meant to collect — and the question asks about the expected behavior of the mismatch, which is query failure. Option B is wrong because SNMP traps are a separate mechanism (SNMP Trap probe) and are not affected by the read community string mismatch in the same way; the question specifically concerns the SNMP Query probe. Option D is wrong because ISE never automatically updates the switch's SNMP community string — that is a manual network device configuration.

21
MCQeasy

Which of the following is NOT a valid probe type in Cisco ISE?

A.SNMP Query
B.ICMP
C.DHCP
D.RADIUS
AnswerB

Cisco ISE supports RADIUS, TACACS+, and REST probes for testing external identity or policy services. ICMP is a network-layer reachability protocol, not an application probe type, so it cannot be configured as a probe in ISE.

Why this answer

Cisco ISE supports several active probe types for endpoint profiling: DHCP, RADIUS, SNMP Query, SNMP Trap, NetFlow, DNS, HTTP, and NMAP, among others. ICMP is not one of the configurable probe types in ISE's profiling configuration — while ISE may send pings internally for reachability, ICMP is not exposed as a profiling probe. Therefore ICMP is the option that is NOT a valid probe type.

Exam trap

The trap here is confusing general network diagnostic protocols (like ICMP/ping) with ISE's specific profiling probe types — candidates assume any protocol ISE 'uses' must be a probe.

How to eliminate wrong answers

Option A is wrong because SNMP Query is a legitimate ISE probe that polls network devices for ARP, MAC, and CDP/LLDP tables. Option C is wrong because the DHCP probe is one of the most commonly used ISE probes, capturing DHCP fingerprint data via SPAN or the NAD. Option D is wrong because the RADIUS probe collects attributes from RADIUS accounting and authentication packets to help profile endpoints.

22
MCQmedium

When a new device connects, you notice it stays in the 'Unknown' profile state. You have confirmed the probes are active. What is the most likely step to fix this?

A.Increase the SNMP timeout.
B.Disable and re-enable the PSN service.
C.Create or update a Profiling Policy to match the collected attributes.
D.Delete the endpoint from the database.
AnswerC

Probes collect endpoint attributes, but Cisco ISE only assigns a profile when a profiling policy matches those attributes. With probes active yet devices stuck at Unknown, the missing or outdated profiling policy is the gap preventing attribute-based classification.

Why this answer

If a device remains in the 'Unknown' profile state despite active probes, it means ISE is collecting attributes but no profiling policy matches those attributes to assign a known profile. Creating or updating a profiling policy to match the collected attributes will allow ISE to classify the device correctly. The other options do not address the root cause: SNMP timeout, PSN service restart, or deleting the endpoint are not relevant to policy matching.

Exam trap

The trap is assuming that active probes automatically lead to profiling. Candidates might overlook that profiling policies must explicitly match the collected attributes. They might also be tempted to troubleshoot probes or services instead of policy configuration.

How to eliminate wrong answers

Option A is wrong because increasing SNMP timeout would only help if SNMP data is not being collected, but the question states probes are active, implying data is collected. Option B is wrong because disabling and re-enabling the PSN service is a drastic step that would affect all endpoints and is unlikely to resolve a single device's profiling issue. Option D is wrong because deleting the endpoint from the database would remove it and force re-profiling, but without a matching policy, it would still remain Unknown.

23
Multi-Selectmedium

Which THREE of the following are considered 'probes' in the Cisco ISE Profiling architecture?

Select 3 answers
A.ICMP Echo
B.DHCP
C.ARP Inspection
D.SNMP Query
E.HTTP
AnswersB, D, E

DHCP is a profiling probe because Cisco ISE consumes DHCP packets relayed from the switch, extracting option 12 hostname, option 60 vendor class and MAC-to-IP bindings to build endpoint profiles. This satisfies the stem's requirement for a genuine probe rather than a collector or feed.

Why this answer

In Cisco ISE profiling, a probe is any mechanism that collects endpoint attribute data to feed the profiling engine, and DHCP, SNMP Query, and HTTP are all valid probe types. DHCP (B) is correct because ISE uses DHCP probes (via DHCP snooping/relay or the DHCP probe on the PSN) to capture DHCP option fields such as Option 55 parameter request list, hostname, and vendor class for endpoint classification. SNMP Query (D) is correct because ISE can actively poll network devices via SNMP to retrieve information like ARP tables, MAC address tables, CDP/LLDP neighbors, and session data, which are used as profiling attributes.

HTTP (E) is correct because the HTTP probe captures User-Agent strings and other HTTP header data from web traffic to help identify endpoint OS and device type. ICMP Echo (A) is not a profiling probe in ISE; it is only used for reachability testing (e.g., in posture or endpoint tests), not for gathering profiling attributes. ARP Inspection (C) is a switch security feature (Dynamic ARP Inspection) rather than an ISE profiling probe; ISE may consume ARP data via SNMP or other probes, but ARP Inspection itself is not classified as a probe.

Exam trap

SISE often tests the distinction between probes and other ISE features, and candidates may confuse security features like ARP Inspection or general protocols like ICMP with profiling probes.

24
MCQmedium

Which attribute is used by the MAC OUI probe to determine the device manufacturer?

A.User-Agent string
B.IP Address
C.DHCP Client ID
D.MAC Address prefix (first 3 bytes)
AnswerD

The first three bytes of a MAC address form the OUI, which the IEEE assigns to a specific manufacturer. The probe reads that prefix and matches it against the OUI registry, so it identifies the vendor without needing the device's full 48-bit address or host portion.

Why this answer

The MAC OUI (Organizationally Unique Identifier) probe inspects the first 3 bytes (24 bits) of a device's MAC address, which is the OUI assigned by the IEEE to a specific manufacturer. ISE maintains an internal OUI-to-vendor mapping database, so when an endpoint's MAC address is seen, the probe matches the prefix to identify the manufacturer (e.g., Apple, Samsung, Cisco). This is why the first 3 bytes are the correct answer.

Exam trap

SISE often tests the misconception that the full MAC address or the IP address identifies the manufacturer, when in fact only the first 3 bytes (OUI) carry vendor information.

How to eliminate wrong answers

Option A is wrong because the User-Agent string is an HTTP header used by the HTTP probe to identify browser/OS information, not the manufacturer from a MAC address. Option B is wrong because the IP address is a Layer 3 logical identifier that can be reassigned and does not encode vendor information. Option C is wrong because the DHCP Client ID is an optional DHCP option (option 61) used for client identification during address assignment, not for OUI-based manufacturer lookup.

25
MCQhard

You want to improve profiling accuracy for endpoints that do not send DHCP options. You decide to use SNMP Trap profiling. What is a critical prerequisite for this to function?

A.The network device must be configured to send SNMP traps to the ISE PSN IP address.
B.The endpoint must support SNMP agents.
C.The ISE node must have the SNMP Query probe enabled.
D.RADIUS Accounting must be disabled.
AnswerA

SNMP Trap profiling depends on receiving unsolicited trap PDUs from network devices, so each device must target the ISE PSN's IP address as a trap receiver. Without that destination configured, no trap reaches ISE and profiling fails, directly satisfying the stem's requirement for endpoints lacking DHCP options.

Why this answer

SNMP Trap profiling requires the network device (switch, WLC, router) to be configured to send SNMP traps to the ISE PSN's IP address, because ISE relies on receiving those traps to extract endpoint attributes like MAC addresses, link up/down events, and CDP/LLDP neighbor data. Without the device actively sending traps to ISE, the SNMP Trap probe receives no data and profiling cannot occur.

Exam trap

The trap is assuming SNMP profiling requires an SNMP agent on the endpoint, when in fact SNMP Trap profiling depends entirely on the network device sending traps to ISE.

How to eliminate wrong answers

Option B is wrong because SNMP Trap profiling collects data from the network infrastructure, not from SNMP agents running on endpoints — most endpoints (printers, IP phones, IoT) don't run SNMP agents anyway. Option C is wrong because SNMP Query is a separate probe that polls devices; enabling it does not satisfy the SNMP Trap prerequisite. Option D is wrong because RADIUS Accounting is independent of SNMP Trap profiling and is often used alongside it for richer attribute collection.

26
MCQeasy

An administrator is configuring profiling in Cisco ISE and wants to ensure that the MAC OUI probe is used to identify the manufacturer of endpoints. Which statement correctly describes the MAC OUI probe?

A.The MAC OUI probe can only identify Cisco devices; it cannot identify devices from other vendors.
B.The MAC OUI probe uses the first 24 bits of the MAC address to determine the device manufacturer.
C.The MAC OUI probe requires the endpoint to be authenticated via 802.1X before it can determine the manufacturer.
D.The MAC OUI probe uses the last 24 bits of the MAC address to determine the device manufacturer.
AnswerB

The MAC OUI probe extracts the first 24 bits (3 bytes) of the endpoint's MAC address, known as the Organizationally Unique Identifier (OUI). This OUI is assigned by IEEE to the device manufacturer. ISE maintains a database of OUIs and maps them to vendor names. This probe is always enabled and provides a basic level of profiling by identifying the manufacturer, such as Cisco, Apple, or Intel. It does not require any additional configuration or network traffic.

Why this answer

The MAC OUI probe is a fundamental profiling method in Cisco ISE that uses the first 24 bits of a MAC address, the OUI, to identify the manufacturer. It does not require authentication or any special configuration; it works with the MAC address available from the initial connection attempt. It can identify devices from any vendor by referencing the IEEE OUI database.

This probe is always enabled and provides a baseline profile that can be enhanced by other probes like DHCP, CDP, or SNMP.

Exam trap

The trap here is confusing the OUI portion with the NIC-specific portion of the MAC address, or assuming that the MAC OUI probe is Cisco-specific when it actually covers all vendors.

27
MCQhard

You are troubleshooting a device that is stuck in the 'Unknown' profile state. You have confirmed that the DHCP probe is receiving packets. What is the next logical step to investigate the failure?

A.Increase the SNMP polling interval.
B.Check the attributes of the endpoint in Context Visibility.
C.Delete the endpoint from the database.
D.Restart the ISE node services.
AnswerB

The DHCP probe confirms the endpoint is reachable, so the failure lies in profiling rather than connectivity. Context Visibility holds the endpoint's attributes and profiling policies; inspecting them reveals whether the correct profile criteria are being matched or misapplied.

Why this answer

When an endpoint is stuck in 'Unknown' despite the DHCP probe receiving packets, the next step is to inspect the endpoint's attributes in Context Visibility to see what ISE actually learned from the probe — such as whether the DHCP class attribute or MAC OUI was populated. This reveals whether the probe data is being parsed correctly or if a profiling condition is failing to match.

Exam trap

The trap is jumping to remediation steps like restarting services or deleting the endpoint instead of first inspecting the collected attributes — profiling troubleshooting always starts with verifying what data ISE actually has.

How to eliminate wrong answers

Option A is wrong because increasing the SNMP polling interval does not address a profiling failure — it only changes how often SNMP data is collected, and SNMP is just one of many probes. Option C is wrong because deleting the endpoint from the database is a destructive action that would not diagnose the root cause and would lose any collected attributes. Option D is wrong because restarting ISE node services is a heavy-handed step that doesn't investigate the specific profiling failure and could disrupt other sessions.

28
Multi-Selecthard

Which TWO of the following are necessary to correctly configure a custom profiling condition based on DHCP attributes?

Select 2 answers
A.Enable HTTP profiling.
B.Configure a static IP on the endpoint.
C.Define a matching operator (e.g., equals, contains).
D.Clear the MAC address table on the switch.
E.Select the correct DHCP attribute from the attribute list.
AnswersC, E

A condition needs a comparison rule to evaluate the collected DHCP attribute against the expected value. Without a matching operator such as equals or contains, the attribute cannot be tested, so the profiling condition never evaluates to true and the endpoint is not classified.

Why this answer

Option C is correct because a profiling condition must specify a matching operator (such as equals, contains, starts with, or matches regex) that determines how the collected DHCP attribute value is compared against the configured value. Option E is correct because the condition must reference a valid DHCP attribute from the available attribute list (for example, DHCP Option 12 hostname, Option 60 vendor class identifier, or Option 55 parameter request list) so the profiler knows which DHCP field to evaluate. Together, selecting the DHCP attribute and defining its matching operator are the two essential components of a custom DHCP-based profiling condition.

Option A is not required because HTTP profiling is a separate profiling method used for HTTP User-Agent attributes, not DHCP. Option B is not required because DHCP profiling relies on the DHCP request/response exchange and does not depend on the endpoint having a static IP. Option D is not required because clearing the switch MAC address table is unrelated to defining a profiling condition and would not affect DHCP attribute matching.

Exam trap

SISE often tests whether candidates confuse the two mandatory building blocks of a profiling condition — the attribute and the operator — with unrelated probe enablement or endpoint IP configuration settings.

29
MCQmedium

A network engineer configures a Cisco ISE deployment with profiler probes enabled on the Policy Service nodes. After deploying a new Cisco Catalyst 9300 switch, the engineer notices that endpoints connected to that switch are not appearing in the Endpoints list, even though they are passing 802.1X authentication. The engineer verifies that the switch is sending RADIUS accounting packets to ISE. Which probe should the engineer verify is enabled to collect endpoint attributes from the switch itself?

A.SNMP probe
B.HTTP probe
C.DHCP probe
D.RADIUS probe
AnswerD

The RADIUS probe collects attributes from RADIUS authentication and accounting packets sent by the network access device, including MAC address, username, and NAS information. Without it, endpoints authenticating via 802.1X would not be profiled from RADIUS data. Enabling this probe on the Policy Service node allows ISE to build endpoint profiles from the switch's RADIUS traffic.

Why this answer

The RADIUS probe is responsible for extracting endpoint attributes from RADIUS authentication and accounting packets. When endpoints authenticate via 802.1X, the switch sends RADIUS messages to ISE, and the RADIUS probe uses those to create or update endpoint profiles. If this probe is disabled, endpoints may authenticate successfully but remain unprofiled, which matches the described symptom.

Exam trap

The trap here is assuming that successful 802.1X authentication automatically guarantees profiling, when in fact profiling requires the RADIUS probe to be enabled to harvest attributes from those same packets.

30
Multi-Selecteasy

Which THREE of the following are standard probes available in Cisco ISE to gather device information?

Select 3 answers
A.SMTP
B.HTTP
C.FTP
D.SNMP Query
E.DHCP
AnswersB, D, E

The HTTP probe is a standard Cisco ISE probe that inspects user-agent strings and HTTP headers from endpoint browser traffic. It satisfies the stem's device-information requirement by supplying profiling attributes such as operating system and browser, which feed policy conditions.

Why this answer

In Cisco ISE, standard probes used for endpoint profiling and gathering device information include HTTP, SNMP Query, and DHCP. Option B (HTTP) is correct because ISE uses HTTP probes to inspect User-Agent strings and other HTTP header data from web requests, which helps identify device type and operating system. Option D (SNMP Query) is correct because ISE sends SNMP queries to network devices to collect system information such as sysDescr, sysObjectID, and interface details for profiling.

Option E (DHCP) is correct because ISE can use DHCP probes to capture DHCP requests and options (for example, option 55 parameter request list, hostname, and vendor class) to fingerprint endpoints. Options A (SMTP) and C (FTP) are not standard ISE probes for device information gathering; SMTP and FTP are application protocols unrelated to ISE profiling probes.

Exam trap

The trap is selecting protocols that are not standard ISE probes, such as SMTP or FTP; candidates must remember the specific probes ISE supports, including HTTP, SNMP Query, and DHCP.

31
MCQmedium

What is the purpose of the 'Endpoint Identity Group' in the context of profiling?

A.To manage authentication credentials.
B.To store device hardware serial numbers.
C.To define which PSN handles the device.
D.To classify devices for use in authorization policy rules.
AnswerD

Endpoint Identity Groups classify profiled endpoints so authorization policy rules can reference them, satisfying the requirement to group devices by identity attributes rather than by static IP or subnet. Profiling feeds discovered attributes into these groups, letting policy conditions match device type, posture, or category during authorization decisions.

Why this answer

The Endpoint Identity Group in Cisco ISE is used to classify devices based on their profiling attributes. These groups are then referenced in authorization policy rules to apply appropriate access controls. For example, a group 'Printers' can be used in an authorization rule to grant printers access to specific network resources.

Thus, its primary purpose is to classify devices for use in authorization policy rules.

Exam trap

The trap here is confusing endpoint identity groups with user identity groups or with other ISE constructs like PSN assignment. Candidates might think endpoint identity groups store credentials or serial numbers, but they are purely for classification in authorization.

How to eliminate wrong answers

Option A is wrong because managing authentication credentials is the role of identity stores (e.g., Active Directory, LDAP), not endpoint identity groups. Option B is wrong because storing hardware serial numbers is not the purpose of endpoint identity groups; they store group membership, not detailed hardware attributes. Option C is wrong because defining which PSN handles the device is related to load balancing and node assignment, not to endpoint identity groups.

32
MCQmedium

You are configuring a device sensor on a Cisco switch to help with ISE profiling. What is the primary benefit of using Device Sensor?

A.It replaces the need for DHCP snooping.
B.It allows the switch to act as a RADIUS server.
C.It enables the switch to send collected device attributes to ISE via RADIUS accounting.
D.It increases the throughput of the switch.
AnswerC

Device Sensor collects attributes such as DHCP, CDP, LLDP and HTTP data from endpoints and forwards them to ISE within RADIUS accounting packets. This enriches ISE profiling without extra probes, satisfying the requirement to profile devices via the switch itself.

Why this answer

The primary benefit of Device Sensor on a Cisco switch is that it collects device attributes (e.g., CDP, LLDP, DHCP, HTTP) and sends them to Cisco ISE via RADIUS accounting packets. This enriches ISE's profiling database, allowing ISE to more accurately identify and classify endpoints. Device Sensor offloads the collection from ISE to the switch, improving scalability and reducing network traffic.

Exam trap

The trap is confusing Device Sensor with DHCP snooping or RADIUS server functionality; candidates must remember that Device Sensor is about collecting and forwarding device attributes to ISE for profiling.

How to eliminate wrong answers

Option A is wrong because Device Sensor does not replace DHCP snooping; DHCP snooping is a security feature that filters DHCP messages, while Device Sensor collects attributes for profiling. Option B is wrong because Device Sensor does not turn the switch into a RADIUS server; the switch remains a RADIUS client. Option D is wrong because Device Sensor does not increase switch throughput; it may add slight overhead due to packet inspection.

33
MCQhard

You are using the Feed Service to update your profiling policies. How can you ensure that custom profiling policies you have created are not overwritten during the update?

A.Custom policies are not affected by Feed Service updates.
B.Place custom policies in the system policy folder.
C.Export custom policies before every update.
D.Disable automatic updates.
AnswerA

Feed Service updates only refresh the built-in Cisco predefined policies; user-created custom policies are stored separately and are never overwritten or removed during a feed synchronisation, so no export or backup step is required to preserve them.

Why this answer

Cisco ISE's Feed Service updates only the system-provided profiling policies that ship with ISE; custom profiling policies created by administrators are stored separately and are not overwritten or removed during a feed update. This design lets organizations receive updated fingerprints for new device types without losing their own customizations.

Exam trap

SISE often tests the misconception that feed updates overwrite all profiling policies, when in fact only system policies are updated and custom policies are preserved.

How to eliminate wrong answers

Option B is wrong because there is no 'system policy folder' concept in ISE profiling — custom policies are simply stored as user-created objects and are inherently separate from feed-managed system policies. Option C is wrong because exporting custom policies before every update is unnecessary; the Feed Service does not touch custom policies, so there is nothing to protect against. Option D is wrong because disabling automatic updates would prevent you from receiving new system fingerprints and is not a mechanism for protecting custom policies — it is an overreaction based on a misunderstanding of how the feed works.

34
MCQhard

You are observing that an endpoint is being profiled as 'Unknown' even though it is clearly a Windows workstation. What is the most likely reason?

A.The device is using a static IP.
B.The necessary probes are not receiving enough attributes to match a policy.
C.The endpoint is not authenticated.
D.The endpoint has a firewall enabled.
AnswerB

Insufficient attributes prevent profiling policies from matching, so the endpoint remains Unknown despite being a Windows workstation. Profiling relies on probes collecting enough identity attributes to satisfy a policy condition; without that threshold, no profile is assigned. This directly addresses the stem's constraint: the workstation is visible but unclassified.

Why this answer

Profiling in ISE relies on collecting attributes from various probes (DHCP, HTTP, RADIUS, SNMP, etc.) and matching them against profiling policies. If the endpoint shows as 'Unknown', the most likely cause is that the probes are not receiving enough attributes — or the attributes received do not match any existing policy condition. Without sufficient attribute data, ISE cannot classify the device even if it is obviously a Windows workstation to a human.

Exam trap

SISE often tests whether candidates blame authentication or IP configuration for profiling failures, when the real issue is almost always missing probe attributes or a policy mismatch — the exam expects you to know profiling is attribute-driven, not auth-driven.

How to eliminate wrong answers

Option A is wrong because a static IP does not prevent profiling; ISE can still profile based on DHCP, HTTP, and other attributes, and static IP is common in some environments without causing 'Unknown' status. Option C is wrong because authentication is separate from profiling — an endpoint can be profiled even if it only does MAC authentication bypass (MAB) or no authentication at all, as long as probes collect attributes. Option D is wrong because a host firewall may block some probes (like SNMP or WMI), but it does not inherently prevent profiling via DHCP/HTTP/RADIUS, and it is not the most likely generic cause.

35
Multi-Selectmedium

Which THREE of the following items must be configured to ensure a successful SNMP Trap profiling implementation?

Select 3 answers
A.Add the network switch to the ISE Network Devices list.
B.Enable the SNMP Trap probe on the ISE PSN.
C.Enable HTTP probe.
D.Configure the network switch to send SNMP traps to the ISE PSN.
E.Configure DHCP Snooping.
AnswersA, B, D

Adding the switch to the ISE Network Devices list registers it as a known NAD, so ISE accepts and processes SNMP trap packets originating from that device's IP address. Without this entry, traps are discarded as untrusted, breaking the profiling feed.

Why this answer

Option A is correct because the switch sending SNMP traps must exist as a Network Device in ISE, which provides the shared secret and device definition ISE uses to authenticate and process incoming SNMP traffic from that switch. Option B is correct because the SNMP Trap probe must be enabled on the ISE PSN that will receive the traps; without this probe running, ISE will not listen for or process SNMP trap notifications. Option D is correct because the switch itself must be configured with the ISE PSN as a trap destination (snmp-server host <PSN-IP> ...), otherwise no traps are ever sent to ISE and profiling data is never collected.

Option C is not required because the HTTP probe is used for HTTP-based profiling (User-Agent, URL data) and is unrelated to receiving SNMP traps. Option E is not required because DHCP Snooping is a Layer 2 switch security feature for DHCP traffic, not a prerequisite for SNMP Trap profiling.

Exam trap

SISE often tests the misconception that enabling the SNMP Trap probe alone is sufficient, causing candidates to overlook the mandatory Network Devices entry and the switch-side trap destination configuration.

36
Multi-Selectmedium

Which THREE of the following are valid methods for collecting endpoint attributes for profiling in Cisco ISE?

Select 3 answers
A.FTP inspection
B.SSH terminal login
C.HTTP User-Agent
D.DHCP Snooping/Helper
E.SNMP Query
AnswersC, D, E

HTTP User-Agent is a valid profiling method because ISE inspects the browser's User-Agent string during HTTP traffic to infer the endpoint's operating system and device type. This satisfies the stem's requirement for an endpoint attribute collection method.

Why this answer

HTTP User-Agent (C) is valid because ISE's HTTP profiling probe captures the User-Agent string from web requests to identify the endpoint's OS and browser. DHCP Snooping/Helper (D) is valid because ISE's DHCP probe collects attributes such as DHCP fingerprint, hostname, and vendor class from DHCP traffic relayed by the switch or helper address. SNMP Query (E) is valid because ISE can poll network devices via SNMP to retrieve endpoint attributes like MAC address, ARP tables, and CDP/LLDP neighbor data.

FTP inspection (A) is not a supported ISE profiling probe, and SSH terminal login (B) is not a profiling collection method in ISE.

Exam trap

The trap here is confusing administrative protocols (SSH, FTP) with profiling probes. Candidates might think any protocol that can gather information is a profiling method, but ISE only supports specific probes like DHCP, HTTP, SNMP, and RADIUS.

Ready to test yourself?

Try a timed practice session using only Profiler questions.