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.

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)

Does Okta require an Agent to sit in-between Okta to SCIM-enabled app on premises requests?

Solution: Yes, and AD Agent

You just re-enabled IWA DSSO and notice it ' s not behaving as it should. What is an aspect you should keep in mind?

Solution: That when re-enabling IWA DDSO a new set of Identity Provider (IDP) routing rules have to be created

You just re-enabled IWA DSSO and notice it ' s not behaving as it should. What is an aspect you should keep in mind?

Solution: That when re-enabling IWA DDSO the Identity Provider (IDP) routing rules must be manually reactivated

When using Okta Expression Language, which of the following will have the output: This is a test

Solution: String.join( " , " , " This " , " is " , " a " , " test " )

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