Okta-Certified-Developer 無料問題集「Okta Certified Developer」

（A）Limits the nr. of elements returned by the API call that uses it

（B）Limits the timeout of the specific API call that uses it

（C）Limits the nr. of APIs per minute (Rate Limit) of the specific endpoint that uses it

（D）Limits the nr. of Pages in the Pagination schema of the API call that uses it

（A）Provide the hook itself with an API token generated by an API-Only-Admin in Okta via using the Inline Hooks Management API

（B）Register your external service endpoint with Okta by using the Inline Hooks Management API

（C）Register Okta into your external app, which will auto-generate hooks section by using the Inline Hooks Management API

（A）/api/v1/authorizationServers/${authServerld}/poIicies/${policyld}

（B）/api/v1/authorizationServers/$(authServerld}/poIicies

（C）/api/v1/ authorizationServers/$( authServerld}/poIicies${scopeId}

（D）/api/v1/authorizationServers/policies/${authServerld}

（E）/api/vl /authorizationServers/credentiaIs/lifecycle/keyRotate

（A）Statement can,t be true as you have to encode the claim name within the command, specifically, this replaces ,N, with and ,/, with QI,

（B）Statement is false

（C）Statement is true

（A）SHA-512

（B）SHA-I

（C）SHA-256

（D）VIDS

（E）All of these

（F）BCRYPT

（A）Prevent CSRF (Cross-site Request Forgery) attacks

（B）Prevent MITM (Man-in-the-middle) attacks

（C）Prevent XSS (Cross Site Scripting) attacks

（D）Statement is False in its entirety as Okta does not have a requirement for that

（A）Okta Integration Network and Just-in-Time Provisioning

（B）OpenID Network and Just-in-Time Provisioning

（C）Okta Integration Network and Just-integrating-Trust Provisioning

（D）Okta Intelligence Network and Just-in-Time Provisioning

（A）Set to 60 minutes

（B）Set to 1 minute

（C）Configurable between 5 minutes and 1 year

（A）Statement is True, but for the Access Token part, as the Refresh Token is the one exchanged, which then creates Access Tokens

（B）Statement is False

（C）Statement is True

（A）"Server Authorization flow,

（B）Yes, it is

（C）The only Oauth flows that exist are: "Client Authorization flow", "Authorization Code flow", "Authorization Code flow with PKCE",

（D）No, SAML 2.0 Assertion flow is an entirely different protocol