On a Windows machine, which is the right behavior if you try to sign into your Okta org and agentless DSSO is properly configured for it?
Solution: You will be automatically redirected to The Okta Sign In page for your organization, where you need to fill in with your AD credentials
Answer : B
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, if you map those attributes from AD to Okta and then Okta to App, as an example
Answer : A
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
Answer : B
As an Okta admin, when you implement IWA, you have to know how to successfully test it to see if it's working. For this you:
Solution: Open up a command prompt and ping the Okta server handling the requests, information about the server found in Okta IP tables for your own org's Cell
Answer : B
What does it mean: "Mapping Direction AD to Okta"?
Solution: Indicates a schema of attribute values flowing Okta towards AD
Answer : B
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 is different: yml
Answer : B
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
Answer : A