When a user signs out of Okta, if they are using IWA, they'll be redirected to the Sign In page and without inputting credentials they'll be signed back in Solution: Statement is true, but then they'll be displayed a 403 HTTP code (Forbidden)

• A.Yes
• B.No

Comment: *

Name: *

Email: *

Verification: *

Once brought into Okta, LDAP roles are represented as:
Solution: Licences

• A.No
• B.Yes

Comment: *

Name: *

Email: *

Verification: *

When a user signs out of Okta, if they are using IWA, they'll be redirected to the Sign In page and without inputting credentials they'll be signed back in Solution: Statement is true

• A.No
• B.Yes

Comment: *

Name: *

Email: *

Verification: *

There might be specific AD attributes, which - apart from others - do not appear in the Okta user profile. Can those extra attributes be mapped and provisioned towards an app?
Solution: No, it is not possible as Okta queries the whole AD schema and retrieves everything that it's able to

• 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: *