Question 1

The Okta RADIUS Server agent:

Options :

A : Communicates via UDP, over default port 1812 and does not support multiple ports simultaneously

B :

Communicates via TCP, over default port 636 and does not support multiple ports simultaneously

C : Communicates via UDP, over default port 1812 and supports multiple ports simultaneously

D : Communicates via UDP, over default port 1812 and supports multiple ports simultaneously

E : Communicates via TCP, over default port 443 and does not support multiple ports simultaneously

Answer: D

Question 2

If a Network Zone is blocked, clients from those blocked list zone cannot access:

Options :

A : Any org URL and are blocked prior to any type of policy evaluation

B : Any org URL but are blocked after they face policy evaluations, for them to not think they got on the block list, hence not possibly knowing this step of a reversed engineering at a Networking level

C : The Org through Inbound SAML SSO or any app through SP-initiated SSO, but can log into their End-User Panel in Okta and that-s about it

Answer: A

Question 3

You should use Okta RADIUS Server agent for authentication, when authentication is being performed by:

Options :

A : VPN devices that don’t support SAML

B : AD DCs that don't support SAML

C :

Virtual Desktops and Reverse Proxies that don’t support SAML

Answer: A,C

Question 4

Which Okta feature / solution offers you the possibility to maintain alternate authentication for off-network users, while keeping Okta for on-network users' authentication requests?

Options :

A : Desktop Single-Sign On

B : Routing Rules

C : Agentless DSSO

D : Device Trust

E :

On-Prem MFA Agent

F : Org to Org

Answer: B

Question 5

The Okta Sign-In widget doesn't make Cross-Origin requests as it uses stateless API requests

Options :

A : Statement is True

B :

Statement is False

C : Okta has no editable options for Cross Origin Access, hence statement is False

Answer: A