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 03,2025.
- Exam Code: Okta Certified Consultant
- Exam Name: Okta Certified Consultant
- Certification Provider: Okta
- Latest update: Apr 03,2025
You are faced with the error: "Failed to connect to the specified LDAP server displays.".
What is worth to consider checking first?
- A . That the ‘username’ attribute’s format contains the exact ’email’ attribute’s address value
- B . To make sure you enabled LDAPS
- C . To run a query and see if it returns the right port for LDAP (always non-SSL)
- D . Email should be in a UPN format, this needs to get checked
What is a Relative Distinguished Name (RDN)? (for example in an LDAP context)
- A . The leftmost portion of the user Distinguished Name
- B . The email address value without the "@domain.xxx" part
- C . The rightmost portion of the user Distinguished Name
The LDAP Incremental import relies on the ‘modifyTimestamp’ attribute to determine whether an LDAP entry has been imported. But, there are times when some on-prem LDAP servers’s system clock could go backward / be delayed – hence Okta missing some updates on an LDAP import. Okta has an option to deal with these issues, called:
- A . Incremental Imports
- B . Maximum clock skew
- C . This statement is false in its entirety as such option does not exist. All clock work very well, according to the NTP (Network Time Protocol)
- D . LDAP clock measurements
- E . LDAP clock delay timeframe
Okta serves pages on your custom domain over HTTPS. To set up this feature, you need to provide:
- A . A token in form of a cookie to the browser to locally (client-side) store session information to your custom domain
- B . A valid Service Account to Okta for setup
- C . An SSL certificate that is valid for your domain
- D . An API key from your custom domain, to authorize Okta to serve pages over HTTPS
After I’ve setup a custom domain for my organization, will the default Okta domain for my org still work?
- A . Yes
- B . No
- C . You will be redirected from the custom domain towards the default one then
Can I add more than one domain?
- A . Yes, you can have multiple custom domains set up for your organization
- B . No, you can only have one custom domain set up for your organization
- C . You are limited to three custom domains per org
In a SAML Trace, you can see that on an [Okta (IDP) App SAML request towards an App (SP side)] where you’ve already configured some regex-matching custom SAML attributes (not set in Mappings, but directly in the SAML App’s config) to be passed over, these (which are named in the App’s config as ‘User attributes’ or ‘Group attributes’) are send:
- A . As an API header
- B . Encrypted
- C . Unencrypted
- D . Back to Okta
The Okta RADIUS Server agent:
- 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
You should use Okta RADIUS Server agent for authentication, when authentication is being performed by:
- 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
You don’t have the same possibility you have for an On-Prem MFA Agent or AD Agent, to increase the logging level, in the case of an Okta Radius server.
- A . Statement is True
- B . Statement is False
- C . Statement is False and you even have 4 modes that you can simply enable via GUI: INFO, DEBUG,
WARN, ERROR