NEW QUESTION 71
With agentless DSSO (Desktop Single Sign-on), you still have a need of deploying IWA Agents in your Active Directory domains to implement DSSO functionality.
Solution: The statement is true, as agentless DSSO means no AD agents, not no IWA agents

NEW QUESTION 72
When using Okta Expression Language, which of the following will have the output: This is a test Solution: String.append(“This is”, ” a test”)

NEW QUESTION 73
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: Yes, but you need to have a SAML 2.0 integrated app or such flow

NEW QUESTION 74
How can SAML provision attributes via JIT? Or even create users?
Solution: By including specific information in the GET API call

NEW QUESTION 75
As an Okta best-practice / recommendation: Okta encourages you to switch from Integrated Windows Authentication (IWA or DSSO) to agentless Desktop Single Sign-on (ADSSO). Okta is no longer adding new IWA functionality and offers only limited support and bug fixes.
Solution: Only the second statement is true

NEW QUESTION 76
The Okta On-Prem MFA Agent acts as a Radius client and communicates with the RADIUS enabled On-Prem server, including RSA Authentication manager for RSA SecurIDs. This basically allows your organization to leverage Second Factor from a variety of On-Premises multifactor authentication tools.
Solution: The statement is false

NEW QUESTION 77
When does Okta bring LDAP groups into Okta?
Solution: Only during LDAP JIT

NEW QUESTION 78
Whenever you make an API call, you will then get back:
Solution: A new object (a user, group or app object)

NEW QUESTION 79
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’

NEW QUESTION 80
How can SAML provision attributes via JIT? Or even create users?
Solution: By including specific information in the assertion

NEW QUESTION 81
Any … <answer_goes_here>’s credentials verified under “Test API credentials” in an Office365 app integration can allow Okta API integration with Office 365 – permissions which once successfully granted will be used by Okta used for Provisioning related tasks Solution: Office 365 user

NEW QUESTION 82
When you are trying to federate (via WS-FED) Office 365 with Okta:
Solution: You can choose to skip importing user groups and group memberships into Okta

NEW QUESTION 83
On a Windows machine, which is the right behavior if you try to sign into your Okta org and agentless DSSO is properly configured for it?
Solution: You will be automatically redirected to your Load-Balancing Application, if you have one configured, enter credentials for it and then redirected back to Okta org

NEW QUESTION 84
As an Okta best-practice / recommendation: Okta encourages you to switch from Integrated Windows Authentication (IWA or DSSO) to agentless Desktop Single Sign-on (ADSSO). Okta is no longer adding new IWA functionality and offers only limited support and bug fixes.
Solution: Only the first statement is true

NEW QUESTION 85
When you call a GET API call for users / groups / and other such objects, the response is usually Paginated, in case these are a lot of objects returned. What do you do in order to retrieve all objects?
Solution: You call the very same API with the help of a different token, hence will return the next page of objects

NEW QUESTION 86
Can you include / exclude users from specific Network Zones defined in Okta from both Sign On and Password policies?
Solution: You can do this with both policy types mentioned