Okta-Certified-Administrator試験無料問題集「Okta Certified Administrator 認定」

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 stays the same: json

In order for SAML to work, there is a need of an IDP and an SP and we know that already, but why is it so? Because:
Solution: An IDP authorizes the users, while the SP authenticates them

Which is a / are best-practice(s) in a SAML 2.0 situation?
Solution: To not use SAML 2.0 and Provisioning via the same App instance in Okta, but integrate the same SP custom domain via two different app instances in Okta, one for SSO, via SAML 2.0 in this case, and one for provisioning on users

When using Okta Expression Language, which of the following will have the output: This is a test Solution: String.join(",", "This", "is", "a", "test")

Once brought into Okta, LDAP roles are represented as:
Solution: Email lists

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, Update, Delete

Can you map the Okta user ID as an Office 365 Immutable ID?
Solution: Not possible and not intended to be possible as it cannot work like this