Which internal Cisco ISE component reduces demand on JVM memory by limiting the number of devices the profiler handles?
A. eventHandlerQueueSize
B. maxEndPointsInLocalDb
C. NetworkDeviceEventHandler
D. forwarderQueueSize
Which internal Cisco ISE component reduces demand on JVM memory by limiting the number of devices the profiler handles?
Most of the questions are from here, but answers for all questions are not right here so you need to make your own effort to find the right answers by studying yourself. 70% of the question are from this site. so practice all questions by doing your own research. I passed my exam using this site and going through the official course.
I made it today with 930 of 1000 Points.
This dump it not valid, all new questions!
The labs are valid.
You will need a test ISE to recreate and exercise the labs.
I used ISE1.3 Patch 8.
Recreate the labs and exercise, the test engine simulating the ISE is clumsy.
B is the correct answer
Failed many new question not from here with score result 769 passing score was 846
Failed 300208. Many new questions not from here
@kv374k good find. I couldn’t find anything about it.
Neither is absolutely correct, IMHO I would chose B.
https://www.cisco.com/c/en/us/td/docs/security/ise/2-2/admin_guide/b_ise_admin_guide_22/b_ise_admin_guide_22_chapter_010101.html
Cisco ISE Profiler Queue Limit Configuration
Cisco ISE profiler collects a significant amount of endpoint data from the network in a short period of time. It causes Java Virtual Machine (JVM) memory utilization to go up due to accumulated backlog when some of the slower Cisco ISE components process the data generated by the profiler, which results in performance degradation and stability issues.
To ensure that the profiler does not increase the JVM memory utilization and prevent JVM to go out of memory and restart, limits are applied to the following internal components of the profiler:
Endpoint Cache—Internal cache is limited in size that has to be purged periodically (based on least recently used strategy) when the size exceeds the limit.
Forwarder—The main ingress queue of endpoint information collected by the profiler.
Event Handler—An internal queue that disconnects a fast component, which feeds data to a slower processing component (typically related to a database query).
Endpoint Cache
maxEndPointsInLocalDb = 100000 (endpoint objects in cache)
endPointsPurgeIntervalSec = 300 (endpoint cache purge thread interval in seconds)
numberOfProfilingThreads = 8 (number of threads)
The limit is applicable to all profiler internal event handlers. A monitoring alarm is triggered when queue size limit is reached.
Cisco ISE Profiler Queue Size Limits
forwarderQueueSize = 5000 (endpoint collection events)
eventHandlerQueueSize = 10000 (events)
Event Handlers
NetworkDeviceEventHandler—For network device events, in addition to filtering duplicate Network Access Device (NAD) IP addresses, which are already cached.
ARPCacheEventHandler—For ARP Cache events.