Okta Certified Consultant - Okta-Certified-Consultant Exam Practice Test

A. Edit the access policy in Okta, when Okta is the Default Authorization Server

B. Have multiple authorization servers in Okta

C. Have custom scopes when Okta is the authorization server

A. No, they cannot change as per studies conducted

B. Those are hard-coded and can never be changed once they are implemented as the whole API structure has to be re-programmed

C. Yes, they can change, for example as a temporary rate limit increase for a customer expecting a higher nr. of people online or self-registrations (for example) in the org, in a proposed timeframe

A. Okta,s AD and LDAP password complexity requirements to match the actual AD and LDAP instances, password complexity requirements

B. To not import attribute values from multiple applications and combine them under the same user profile in Okta UD

C. LDAP-sourced users to always stay LDAP-sourced. Same applying for AD-sourced users

A. Inbound calls from your own custom code to Okta

B. Is a web-service triggering Internet-accessible endpoint which send PUT API calls back to Okta or to your own custom code

C. Outbound calls from Okta to your own custom code

A. Not for Okta, only for the IDPs Okta is configured with

B. They improve end-user sign-in experience, but they do not provide security enhancements

C. Yes

A. It has no limit and can retrieve data since the creation of the specific org from which the token authorizing the API call got issued

B. 30 days

C. 90 days

D. 10 days

E. 180 days

A. Increase the speed of your org on authentication / authorization requests

B. Make your users, authentication requests never hit Okta servers, endpoint anymore as they will be redirected to you, to the server where you have the Sign-In Widget hosted

C. Allow you to customize it

A. No, Okta randomly selects an AD Agent, location is not a factor in this equation

B. Yes, Okta is pinging all the AD Agents to find their location and then it will use the one closest to the user initiating log in requests

C. Yes, this way there will surely be less hops on a traceroute for the requests