Which of the following is / are Okta required attributes?

Solution: None of the above

When does Okta bring LDAP roles into Okta?

Solution: During both LDAP import and JIT

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, but you need to have a SAML 2.0 integrated app or such flow

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

When using Okta Expression Language, which of the following will have the output: okta.com

Solution: String.substringBefore( " abc@okta.com " , " @okta.com " )

The SCIM protocol is < response_is_entered_here > for provisioning and managing identity data on the web.

Solution: An application-level SAML protocol

With Okta you federate the ' Office 365 tenant name ' (which is the default Microsoft domain you have) or the ' Office 365 domain ' ?

Solution: You federate with Okta both the ' Office 365 tenant name ' and the ' Office 365 domain '

With Okta Retention Policy, App generated data and reporting based on log data older than how many months is automatically removed (not considering the Backup Data)?

Solution: 6 months

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