Okta AD Agents can be successfully and completely configured by:
Solution: Super administrators

• A.No
• B.Yes

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, Delete

• A.Yes
• B.No

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.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 might be seamless for the user, but the redirect is happening

• A.Yes
• B.No

Comment: *

Name: *

Email: *

Verification: *

In an agentless DSSO (Desktop Single Sign-on) scenario Okta is the one decrypting the Kerberos ticket, finds then the user name, authenticates the user and passes back a session to the browser.
Solution: The statement is entirely valid

• A.No
• B.Yes

Comment: *

Name: *

Email: *

Verification: *