In an SP-initiated SAML 2.0 flow, the SP will never redirect to Okta if the session is already active Solution: It will always redirect to Okta and in this case only - will promt the user for re-authentication by manually entering SP credentials

• A.Yes
• B.No

Comment: *

Name: *

Email: *

Verification: *

Which of the following is / are true?
Solution: If an MFA factor is set to 'required' and another MFA factor set to 'disabled', then users can choose between the two factors when enrolling, but then can use only the first one for successful logins

• A.Yes
• B.No

Comment: *

Name: *

Email: *

Verification: *

When you are trying to federate (via WS-FED) Office 365 with Okta:
Solution: You can choose between SAML 2.0 or OIDC for the current integration

• A.No
• B.Yes

Comment: *

Name: *

Email: *

Verification: *

Can you include / exclude users from specific Network Zones defined in Okta from both Sign On and Password policies?
Solution: Only for Sign On policies you have such granularity

• A.No
• B.Yes

Comment: *

Name: *

Email: *

Verification: *

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

• A.No
• B.Yes

Comment: *

Name: *

Email: *

Verification: *