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: Paste into a browser configured for DSSO the IWA redirect URL along with '/authenticated.aspx' after it, hit 'Enter' and check the message returned
Answer : A
Can you include / exclude users from specific Network Zones defined in Okta from both Sign On and Password policies?
Solution: Only for Sign On policies you have such granularity
Answer : B
Does Okta require an Agent to sit in-between Okta to SCIM-enabled app on premises requests?
Solution: Yes, an Okta Application Integration Agent
Answer : B
What does it mean: "Mapping Direction AD to Okta"?
Solution: Indicates a schema of attribute values flowing AD towards Okta
Answer : A
When using Okta Expression Language, which of the following will have the output: This is a test
Solution: String.join(",", "This", "is", "a", "test")
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 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, Upload, Deprovision
Answer : B