Okta Okta Certified Consultant Okta Certified Consultant Online Training
Okta Okta Certified Consultant Online Training
The questions for Okta Certified Consultant were last updated at Apr 01,2025.
- Exam Code: Okta Certified Consultant
- Exam Name: Okta Certified Consultant
- Certification Provider: Okta
- Latest update: Apr 01,2025
When Okta calls your external service, it enforces a default timeout of <response_goes_here> seconds.
- A . 1
- B . 3
- C . 10
- D . 30
In an Inline Hook scenario, when Okta calls your external service, Okta may attempt to retry.
How many retries will Okta perform?
- A . Okta doesn’t retry, no matter the situation
- B . Okta will attempt at most one retry
- C . Okta will attempt to retry 3 times
- D . Unlimited
In an Inline Hook scenario, if the external service responds with a redirect, Okta follows it.
- A . Okta does follow the redirect on the very same request
- B . Okta does not follow the redirect
- C . Okta does follow the redirect, but with a different request to the service
After you’ve created your external service, you have to register its endpoint in Okta.
- A . Statement is True
- B . Statement is False, as only users are registered, not services
- C . Statement is False, as you are using Header-Based authentication and the token you provide in API calls acts as an API token, token which is in fact received from the external service itself, hence there is no need to register the service’s endpoint in Okta as on each and every call the authorization header is passed on and it will know exactly which Okta domain is calling the service, so there is no need for a trust to be established in the Okta side as well
Optional user account fields include a ‘secondary email address’ and a ‘security image’.
- A . Statement is False, as the ‘secondary email address’ is mandatory to have a value assigned
- B . Statement is False, as the ‘security image’ is mandatory to have a value assigned
- C . Statement is True
- D . Statement is False, as both aforementioned attributes would need to have a value assigned
In the context of ASA (Advanced Server Access), the Windows and Unix server usernames are defined in Okta as:
- A . ‘windowsUserName’ and respectively ‘UnixUserName’
- B . ‘osUserName’ and respectively ‘LinuxUserName’
- C . ‘winUserName’ and respectively ‘UserName’
- D . Only users have usernames, not servers, it’s obvious
You can further integrate Advanced Server Access with Okta by configuring SCIM, which allows your:
- A . Advanced Server Access groups (only) to be managed by Okta
- B . Advanced Server Access users (only) to be managed by Okta
- C . Advanced Server Access groups and users to be managed by Okta
- D . Advanced Server Access local Admin to manage the Okta users’ attributes from On-Prem
In order to successfully deploy an Advanced Server Access server, you must:
- A . Simply install the server agent
- B . Simply enroll the server
- C . Install the server Agent and enroll the server
Advanced Server Access Enrollment is the process where the Advanced Server Access Agent configures a server to be managed by a specific:
- A . Admin
- B . Project
- C . AD server
- D . AD Service Account
Is Advanced Server Access Server Agent supported on Microsoft Active Directory DC?
- A . No, it’s not supported there
- B . It is supported
- C . Advanced Server Access server agent is only supported on Linux kernel related distributions