Okta AD Agents can be successfully and completely configured by:

Solution: Read-only administrators

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 only the 'Office 365 tenant name'

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

How can SAML provision attributes via JIT? Or even create users?

Solution: By including specific information in the assertion

Okta AD Agents can be successfully and completely configured by:

Solution: Super administrators

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

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 false, as this would represent a security concern