Free Cisco 300-715 SISE Actual Exam Questions - Question 7 Discussion
maximum of two devices. There are other guest services in production that rely on the default guest
types. How should this configuration change be made without disrupting the other guest services
currently offering three or more guest devices per user?
B imo. Creating a new guest type to set device limits keeps existing guest types untouched, so other services stay unaffected. This seems cleaner than messing with identity or sponsor groups.
Option A keeps other guest types intact by limiting devices via an identity group.
Seems like option B makes the most sense here. Creating a new guest type specifically for sponsored guests means you can set their device limit independently without messing with the default guest types that other services rely on. This way, existing guests who need three or more devices aren’t affected at all. The key is that guest types usually have separate settings, so this should keep things clean and isolated.
A/C? A keeps existing guest types untouched by targeting identity groups specifically, which feels safer for other services. C’s LDAP tagging might overcomplicate things without clear benefits here.
A imo, creating an ISE identity group is a clean way to manage device limits for specific user sets without touching existing guest types or sponsors. This approach isolates the limit to just that group’s logins, so other guest services with defaults stay untouched. It’s a more targeted change than messing with guest types or sponsor groups that could have wider impact.
B/D? New guest types let you set device limits without touching defaults, but new sponsor groups might be easier to manage just for sponsored guests. Either way, both separate the settings from default guest services.
B