Correct Answer: The user connects and authenticates, is redirected to the onboarding portal, downloads/configures the native supplicant profile, and the device receives a certificate before being granted its final authorized access
Explanation: The typical flow is authenticate, redirect to onboarding, provision the native supplicant profile, issue a certificate, then grant final authorized access, unlike granting final access before authentication/onboarding, requiring the device be mailed to IT, skipping the portal/certificate steps entirely, using a telephone passphrase, or onboarding via the TACACS+ interface.
Correct Answer: The user connects and authenticates, is redirected to the onboarding portal, downloads/configures the native supplicant profile, and the device receives a certificate before being granted its final authorized access
Explanation: The typical flow is authenticate, redirect to onboarding, provision the native supplicant profile, issue a certificate, then grant final authorized access, unlike granting final access before authentication/onboarding, requiring the device be mailed to IT, skipping the portal/certificate steps entirely, using a telephone passphrase, or onboarding via the TACACS+ interface.