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
Answer : B
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 you have to issue another API token for the AD / IWA Agents
Answer : B
Once brought into Okta, LDAP roles are represented as:
Solution: Licences
Answer : B
Speaking of Okta Template App and Okta Pluin Template App, which of the following RegEx can you create for an allow list of URLS so that both endpoints for /login or /change_password are accepted under example.com domain?
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
When does Okta bring LDAP roles into Okta?
Solution: During both LDAP import and JIT
Answer : B
Can you include / exclude users from specific Network Zones defined in Okta from both Sign On and Password policies?
Solution: Only for Password policies you have such granularity
Answer : B