NO.56 When a user’s Okta password is changed:
Solution: All apps that are Provisioning-enabled and have Sync Password option active under Provisioning settings – will begin to sync the password in respective apps

NO.57 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 first statement is true

NO.58 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)

NO.59 What does it mean: “Mapping Direction AD to Okta”?
Solution: Indicates a schema of attribute values flowing AD towards Okta’s Apps directly, Okta just facilitating this end-to-end direct flow

NO.60 Which is a / are best-practice(s) in a SAML 2.0 situation?
Solution: To not link your admin user from the SP via SAML with a user from Okta, if the app (SP) does not provide a SAML bypass URL

NO.61 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 valid, but Okta is not the one doing authentication – IWA Agent and AD Agent are doing that as AD agent verifies the AD user’s identity

NO.62 With agentless DSSO (Desktop Single Sign-on), you still have a need of deploying IWA Agents in your Active Directory domains to implement DSSO functionality.
Solution: The statement is true, but not for the part about: the deployment of IWA Agents into Active Directory domains. The IWA Agents can now be deployed on whichever machine, it’s a unique functionality that only agentless DSSO has and not on-prem DSSO.

NO.63 When does Okta bring LDAP roles into Okta?
Solution: During both LDAP import and JIT

NO.64 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

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

NO.66 When does Okta bring LDAP groups into Okta?
Solution: Only during an LDAP import

NO.67 The SCIM protocol is <response_is_entered_here> for provisioning and managing identity data on the web.
Solution: An application-level SAML protocol

NO.68 Okta has a json representation of objects such as ‘users’, json schema interchanged on API calls, as an example, but what about the format of information regarding of a user going to a SCIM server for creating the user in an On Premises application?
Solution: Format stays the same: json

NO.69 Regarding policies, Okta recommends:
Solution: Include a final catch-all rule that denies access to anything that does not match any of the preceding rules

NO.70 The SCIM protocol is <response_is_entered_here> for provisioning and managing identity data on the web.
Solution: An application-level REST protocol