A downtown hotel is hosting a two-day fintech conference. Attendees must be approved by a hotel staff member before they reach the internet, each guest account must be valid for no more than one day, and check-in happens at a lobby kiosk. Which guest access design should the hotel administrator use for the conference attendees?
Select an answer to reveal the explanation.
Short Explanation
At the lobby kiosk, use sponsor approval so a staff member can approve each guest before you grant internet access. Set each account to expire after one day—it’s like a daily room key that won’t keep working tomorrow.
Full Explanation
A guest self-registration portal lets the attendee submit a registration request, and ISE can require sponsor approval before granting access. Set the guest account validity to one day to meet the time limit. The lobby kiosk can be used for the attendee’s registration; staff then approve the request. Self-registration without sponsor approval fails the staff-approval requirement. Seven-day accounts exceed the one-day limit, and creating sponsored accounts in advance from the office removes the required lobby kiosk check-in. Portal and guest-type labels can vary between ISE versions, so verify the configured registration and approval flow in the GUI. Test the flow and confirm the approval record and account expiration in the guest user record.