Whenever you make an API call, you will then get back:
Solution: A new object (a user, group or app object)

• A.No
• B.Yes

Comment: *

Name: *

Email: *

Verification: *

In an SP-initiated SAML 2.0 flow, the SP will never redirect to Okta if the session is already active Solution: It will always redirect to Okta and in this case only - will promt the user for re-authentication by manually entering Okta credentials

• A.No
• B.Yes

Comment: *

Name: *

Email: *

Verification: *

In order for SAML to work, there is a need of an IDP and an SP and we know that already, but why is it so? Because:
Solution: An SP sends SAML assertions, while the IDP receives and validates them

• A.Yes
• B.No

Comment: *

Name: *

Email: *

Verification: *

Regarding Access Request Workflow, when a user requests an app - he can also include a message to the approver. But you can also designate an approver group.
Solution: Both statements are false

• A.Yes
• B.No

Comment: *

Name: *

Email: *

Verification: *

In Okta's KB articles the set of functions under the 'Provisioning' concept are referred to as CRUD. This is a concept you also meet when referring to CRUD APIs. What about its meaning here, in Okta's vision?
Solution: In 'Provisioning', CRUD stands for Create, Read, Update, Deprovision

• A.Yes
• B.No

Comment: *

Name: *

Email: *

Verification: *