先試後買

A. Okta is an IdP, hence it cannot be an SP to allow such a flow

B. By creating an Inbound SAML connection with that IdP

C. By only enabling JIT (Just-in-Time) Provisioning at an org-level

A. Statement is False and you even have 4 modes that you can simply enable via GUI: INFO, DEBUG, WARN, ERROR

B. Statement is False

C. Statement is True

A. You can only have one such Agent, so high-availability doesn,t apply in this scenario, but only for AD Agents, IWA Agents, so on

B. You can ensure high-availability by ensuring this On-Prem MFA Agent works on multiple AD forests / domains

C. By installing another one on another Windows Server host

D. By configuring another Service Account on the same On-Prem MFA Agent so that if you lose one, to have another available

A. OpenID Connect protocol, which means you can request ID tokens in addition to OIDC or OAuth 2.0 tokens from the authorization server endpoints

B. OpenID Connect Provider, which means you can request Open ID Connect tokens in addition to access tokens from the authentication server endpoints

C. OpenID Connect Provider, which means you can request ID tokens in addition to access tokens from the authentication server endpoints

D. OpenID Connect Provider, which means you can request ID tokens in addition to access tokens from the authorization server endpoints

A. Back to Okta

B. As an API header

C. Encrypted

D. Unencrypted

A. Yes, as when one goes down due to various reasons, the other may be able to take and process the requests

B. No, as it will cause latency on the requests

C. No, as Okta always uses either one of them to communicate to AD and handle requests, hence rendering the other useless. Thus this can,t be a best-practice

A. Mobil App

B. Single Page App

C. Web App