A. Project
B. AD Service Account
C. AD server
D. Admin
A. A list of enrolled servers. Only if the server was successfully enrolled it will appear in the list
B. A list of logs (chronologically ordered) for events happening across the list of servers
C. A list of projects and their date for enrollment into the server farm
A. Create, Read, Upload, Delete
B. Create, Read, Update, Deprovision
C. Create, Read, Upload, Deprovision
D. Create, Read, Update, Deliver
E. Create, Read, Update, Delete
A. ,windowsUserName, and respectively ,UnixUserName,
B. ,osUserName, and respectively ,LinuxUserName,
C. Only users have usernames, not servers, it,s obvious
D. ,winUserName, and respectively ,UserName,
A. Cross-Origin Restricted Source
B. Mechanism that allows JavaScript hosted on your website to make XMLHttpRequests to Okta API via session cookie authorization
C. Cross-Origin Resource Sharing
D. Mechanism that allows another domain to request specific restricted resources on a web page with the condition that the domain requesting it is not a subdomain in this case, but a total different one apart from the first one where the resources are hosted on
A. 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
B. No, Okta randomly selects an AD Agent, location is not a factor in this equation
C. Yes, this way there will surely be less hops on a traceroute for the requests
A. Statement is True
B. Statement is False, as the ,security image, is mandatory to have a value assigned
C. Statement is False, as both aforementioned attributes would need to have a value assigned
D. Statement is False, as the ,secondary email address, is mandatory to have a value assigned
A. ,access_token,
B. ,refresh_token,
C. ,oidc_token,
D. ,id_token,
A. Push by SSO standard
B. Push by rule
C. Push by name
D. Push by Entity Id
A. hasWorkdayUser()
B. findDirectoryUser()
C. hasDirectoryUser()