An end user account has been changed from an Active Directory mastered user to an Okta mastered user. Is this what the end user must do upon the next login?
Solution: Change email address on user profile
Answer : B
An employee who has left a company used an application that does NOT support lifecycle management. Is this a task generated by Okta to remind the administrator to offboard the employee?
Solution: Deprovisioning task
Answer : A
Employee leaves an organization
As employees leave an organization, a process can be initiated by various departments to deactivate users. The user account needs to be deactivated. Deprovisioning deactivates the user account from theOktaUniversal Directory. Deprovisioning ensures that persons who are no longer in your organization do not have access to sensitive applications and data.
You can deprovision users inOktaor from an external user store, such as AD or a CRM app, such as Salesforce. Typically, user deactivation is triggered from an external user store and it flows intoOkta. In any case, deactivated users are automatically deprovisioned from supported apps. Admins receive an email describing any apps that require them to manually deprovision from users.
https://help.okta.com/en/prod/Content/Topics/Provisioning/lcm/lcm-lifecycle-event-triggers.htm
An Okta Administrator configured the factor enrollment policy to require Okta Verify as a factor and Google Authenticator and Voice Call Authentication as optional factors
Is this what happens when an end user authenticates with Okta?
Solution: The end user must enroll in all three factors and use all three factors when authenticating.
Answer : A
Is this the authentication method or flow that is used when an end user launches a SAML application from the Okta end user home dashboard?
Solution: Service Provider (SP) initiated
Answer : A
Is this a true statement about a General Availability (GA) feature?
Solution: It is available to all eligible customers.
Answer : A
https://developer.okta.com/docs/reference/releases-at-okta/
A feature in General Availability (GA) is new or enhanced functionality that is enabled by default for all customers. Beginning in February 2017, features move from EA (enabled by request) to GA (enabled for all orgs) in a regular cadence:
EA features become GA in preview orgs in the first release of the month.
These same features become GA in production orgs in the first release of the next month.
Features in GA are supported by Okta Customer Support, and issues are addressed according to your Customer Agreement with Okta.
Documentation for features in GA release are not marked with any icons.
Answer : B
Search knowledge articles
Submit a case to Support by clicking the 'Open a Case' button
Join groups (Okta recommends that admins join the 'Admin Pro Tips' group where we post regular content such as onboarding materials, new feature videos, webinars, and more)
https://support.okta.com/help/s/article/Getting-Started-as-a-New-Okta-Administrator?language=en_US
An Okta Administrator needs to ensure that all remote contractors are prompted tor multifactor authentication (MFA) when they attempt to log in to Okta.
Is this a step the administrator should take to meet this requirement?
Solution: Implement Single Sign-On (SSO) at login
Answer : A