Okta-Certified-Administrator Dumps for Pass Guaranteed – Pass Okta-Certified-Administrator Exam 2022 [Q75-Q96]

NO.75 You just re-enabled IWA DSSO and notice it’s not behaving as it should. What is an aspect you should keep in mind?
Solution: That when re-enabling IWA DDSO the Identity Provider (IDP) routing rules must be manually reactivated

NO.76 Which of the following is / are Okta required attributes?
Solution: countryCode

NO.77 Which of the following is / are true?
Solution: If an MFA factor is set to ‘required’ and another MFA factor set to ‘optional’, then users can enroll into both factors and then can use either of them for successful logins

NO.78 What does it mean: “Mapping Direction AD to Okta”?
Solution: Indicates a schema of attribute values flowing AD towards Okta

NO.79 The SCIM protocol is <response_is_entered_here> for provisioning and managing identity data on the web.
Solution: An application-level REST protocol

NO.80 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, but not for the part about: the deployment of IWA Agents into Active Directory domains. The IWA Agents can now be deployed on whichever machine, it’s a unique functionality that only agentless DSSO has and not on-prem DSSO.

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

NO.82 What does SCIM stand for?
Solution: System for CRSF-domain Identity Management

NO.83 How can SAML provision attributes via JIT? Or even create users?
Solution: By including specific information in the GET API call

NO.84 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

NO.85 When does Okta bring LDAP groups into Okta?
Solution: During both LDAP import and JIT

NO.86 Can you map the Okta user ID as an Office 365 Immutable ID?
Solution: Done via mappings, by pushing from Okta to Office 365: user.getInternalProperty(“id”)

NO.87 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 is different: xml

NO.88 Which port and which of the: ‘http’ or SSL enabled connections does Okta recommend?
Solution: Port 443 and http connections

NO.89 Okta AD Agents can be successfully and completely configured by:
Solution: Organization administrators

NO.90 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 The Okta Sign In page for your organization, where you need to fill in with your AD credentials

NO.91 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 false

NO.92 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, if you map those attributes from AD to Okta and then Okta to App, as an example

NO.93 The SCIM protocol is <response_is_entered_here> for provisioning and managing identity data on the web.
Solution: An application-level TLS protocol

NO.94 With Okta Retention Policy, App generated data and reporting based on log data older than how many months is automatically removed (not considering the Backup Data)?
Solution: 3 months

NO.95 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

NO.96 Provisioning actions between cloud-based apps / on-premises apps and Okta are completed by using:
Solution: The SCIM standard