SkillTestPro | CCNP Security 300-715 SISE Practice Test 19

CCNP Security 300-715 SISE Practice Test 19 (Hard) - Endpoint Purge Policies and Context Visibility

CISCO CCNP Security Exam Logo

1 / 10

Which Cisco ISE feature provides administrators with a consolidated dashboard view of endpoint attributes, including identity, device type, location, and compliance status, gathered from multiple ISE services?

Context Visibility

The TACACS+ command set editor, which manages device administration commands rather than endpoint context

The network device group hierarchy editor, which organizes devices by location/type rather than showing endpoint context

The certificate authentication profile page, which maps certificate fields rather than displaying endpoint context

The sponsor portal, which is used for guest account creation rather than endpoint context visibility

The guest portal customization page, which configures guest-facing appearance rather than endpoint context

2 / 10

Which ISE administrative feature allows stale or inactive endpoint records to be automatically removed from the endpoint database after a defined period of inactivity?

Endpoint purge policy

The profiler feed service, which downloads updated profiling rules rather than purging stale endpoint records

The guest type configuration, which defines guest account attributes rather than purging endpoints

The sponsor group configuration, which defines sponsor privileges rather than purging endpoints

The certificate authentication profile, which maps certificate fields rather than purging endpoints

The posture policy, which evaluates compliance rather than purging stale endpoint records

3 / 10

Which risk would most likely result from never configuring an endpoint purge policy in a large, long-running ISE deployment with high endpoint turnover (such as many transient guest or BYOD devices)?

ISE would automatically shut down permanently once the endpoint database reaches any size at all, under normal operating conditions, under normal operating conditions

The endpoint database could grow excessively large over time with stale records, potentially affecting performance and making reporting less useful

All existing authorization policies would automatically be deleted as a result

All network devices would automatically lose RADIUS connectivity to ISE

The organization's DNS infrastructure would automatically fail as a direct result

The profiler feed service would automatically disable itself in response

4 / 10

Which context visibility capability would help an administrator quickly identify all endpoints currently classified under a specific low-confidence or 'unknown' profile for further review?

Physically walking through every building to visually inspect each connected device

Reviewing only the wireless access point's physical firmware version display

Reviewing only the organization's printed employee handbook

Reviewing only the guest portal's background image configuration

Manually calling every single employee in the organization to ask about their device, which does not align with best practices

Filtering or searching the context visibility endpoint list by profile/identity group

5 / 10

Which practice would help ensure that an organization's endpoint purge policy does not inadvertently remove records for devices that are still legitimately in active, if infrequent, use?

Assuming purge policies never affect any legitimately active device regardless of the configured threshold

Purging endpoint records at completely random, undocumented intervals with no defined threshold at all

Setting the purge threshold to zero days so every endpoint record is deleted immediately after each session

Disabling all endpoint identity groups entirely so purging has no relationship to classification

Setting the purge inactivity threshold based on realistic usage patterns (such as devices used occasionally, like seasonal equipment) rather than an arbitrarily short window

Deleting the entire endpoint database manually on a daily basis instead of using a purge policy

6 / 10

Which reporting use case is best supported by ISE's context visibility and endpoint reporting features working together?

Auditing the organization's building access badge log with no ISE integration involved, in most deployment scenarios, which does not align with best practices

Auditing the current mix of device types, compliance states, and identity groups connected to the network at a given time

Auditing the printer's toner level indicator history

Auditing the wireless access point's physical firmware version display exclusively

Auditing the guest portal's background image revision history exclusively

Auditing the organization's unrelated printed employee handbook revision history

7 / 10

Which combination of endpoint lifecycle management practices would help a large enterprise maintain an accurate and performant ISE endpoint database over time?

An extremely aggressive purge policy that removes every endpoint record after a single day regardless of usage pattern

Manual database deletion performed haphazardly with no documented process

Assuming the endpoint database requires no lifecycle management of any kind indefinitely

A realistically tuned purge policy, periodic review of context visibility data for unclassified or low-confidence endpoints, and documented manual overrides where needed

Disabling context visibility entirely to reduce administrative overhead

No purge policy at all combined with never reviewing context visibility data, in accordance with common design practices, which is not the standard approach, under normal operating conditions

8 / 10

Which factor would most influence how an administrator sets the inactivity threshold in an endpoint purge policy?

The organization's typical device usage patterns, including how often legitimate devices such as seasonal or infrequently used equipment reconnect

The color scheme configured for the ISE administrative GUI

The number of parking spaces available in the visitor lot

The font used in the organization's internal newsletter

The specific brand of coffee served in the network operations center, based on standard platform behavior, based on standard platform behavior, which is inconsistent with expected behavior

The average outdoor temperature at the organization's headquarters

9 / 10

Which statement accurately describes why context visibility data is useful input when reviewing or refining profiling and authorization policies over time?

Context visibility data only reflects guest accounts and has no relevance to corporate or IoT endpoints

Context visibility data is only available for a single day before being permanently and automatically deleted

Context visibility data is purely cosmetic and has no relationship to profiling or authorization policy refinement, under normal operating conditions, regardless of the platform version in use

Context visibility data automatically rewrites authorization policy without any administrator involvement

It surfaces real, current classification and compliance patterns across the actual connected endpoint population, helping identify gaps or misclassifications to address

Context visibility data is generated exclusively by the sponsor portal with no relationship to profiling

10 / 10

Which combined use of profiler, context visibility, and purge policy features best supports an organization's ongoing endpoint governance for a network with continuously changing device types?

Regularly reviewing context visibility for new or misclassified device patterns, refining profiling policies accordingly, and maintaining a realistically tuned purge policy to keep the database current

Configuring these features once at initial deployment and never revisiting them again regardless of how the device population changes, in accordance with common design practices, which is not the standard approach

Relying exclusively on the purge policy while ignoring context visibility and profiling policy refinement entirely

Relying exclusively on manual, ad hoc endpoint classification with no use of context visibility or profiling policy review

Disabling the purge policy permanently while also disabling context visibility reporting entirely

Assuming device types connecting to the network never change over time, removing any need for ongoing review

Your score is

The average score is 0%