When a user's Okta password is changed:
Solution: All apps that are Provisioning-enabled and have Update Attributes option active under Provisioning settings - will begin to sync the password in respective apps, as password is an attribute of their profile - but only if JIT Provisioning is enabled as well as it has to be a just-in-time action, the moment the user resets the password

• A.Yes
• B.No

Comment: *

Name: *

Email: *

Verification: *

After you turn on Desktop SSO, a default DSSO related routing rule is created. You must configure the network information for this rule.
Solution: The statement is true

• A.Yes
• B.No

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: Yes, but you need to have a SAML 2.0 integrated app or such flow

• A.No
• B.Yes

Comment: *

Name: *

Email: *

Verification: *

As an Okta best-practice / recommendation: Okta encourages you to switch from Integrated Windows Authentication (IWA or DSSO) to agentless Desktop Single Sign-on (ADSSO). Okta is no longer adding new IWA functionality and offers only limited support and bug fixes.
Solution: Only the second statement is true

• A.No
• B.Yes

Comment: *

Name: *

Email: *

Verification: *

When does Okta bring LDAP groups into Okta?
Solution: During both LDAP import and JIT

• A.Yes
• B.No

Comment: *

Name: *

Email: *

Verification: *