A downtown conference center opens guest Wi-Fi to hundreds of visitors who must register from their own phones with a mobile number and then wait for a staff sponsor to approve each request. Traffic must stay blocked until the visitor enters the approved username and password, and every visitor must hold an individually registered account. Which web authentication design meets these guest access requirements?
Select an answer to reveal the explanation.
Short Explanation
You need central web authentication to send visitors to ISE’s guest self-registration portal, where they provide a mobile number and wait for sponsor approval before traffic is allowed. It’s like a check-in desk: each guest gets an individual account and can’t pass through until they enter their approved username and password.
Full Explanation
Central web authentication with an ISE guest self-registration portal fits the workflow: visitors register on their own phones, provide mobile numbers, and requests go to staff sponsors for approval. The network can keep guest traffic blocked until an approved visitor enters the assigned username and password, while ISE maintains a separate account for each visitor. A self-registration flow that verifies a mobile number and creates a unique account but grants access immediately misses the required sponsor approval; mobile verification is not equivalent to staff authorization. Sponsor-created accounts can provide individual credentials, collect mobile numbers, and ensure approval, but they do not let each visitor register from their own phone as required. A portal using a unique SMS one-time code can support mobile verification, sponsor approval, and individual identities, but it fails the stated requirement to enter an approved username and password. Exam caveat: “central” versus “local” web authentication describes where the portal and policy are handled; the label alone does not guarantee the required approval and credential sequence. Practical check: test a new account end to end and confirm that access remains denied before sponsor approval and until the approved username and password are submitted.