IDENTITY-AND-ACCESS-MANAGEMENT-ARCHITECT practice question 29 of 30
Universal Containers is creating a mobile application that will be secured by Salesforce Identity using the OAuth 2.0 user-agent flow (this flow uses the OAuth 2.0 implicit grant type). Which three OAuth concepts apply to this flow? Choose 3 answers
Full set: 248 questionsThe OAuth 2.0 user-agent flow, also known as the implicit grant type, is designed for client-side applications like mobile or single-page web apps.
1. Client ID (A): This is a public identifier for the client application. It is a mandatory parameter (clientid) in the authorization request to identify the application to the Salesforce authorization server.
2. Scopes (E): Scopes are used to specify the level of access the application is requesting. The user must consent to these permissions. The scope parameter is a mandatory part of the authorization request. While the provided answer key suggests 'B' (Refresh Token), this is incorrect for the standard user-agent (implicit) flow. The implicit grant is considered less secure because the access token is exposed in the user-agent. For this reason, Salesforce documentation and the OAuth 2.0 specification (RFC 6749) explicitly state that a refresh token is not issued in this flow to limit the duration of potential exposure. A new access token requires the user to re-authenticate.
B. Refresh Token: The standard user-agent (implicit) flow does not issue refresh tokens due to the security risk of exposing a long-lived credential to the user-agent.
C. Authorization Code: This is a temporary code used in the OAuth 2.0 web server flow (Authorization Code Grant). The implicit flow bypasses this step entirely.
D. Verification Code: This term is not a standard component of the OAuth 2.0 user-agent flow. It is more commonly associated with device authorization flows or multi-factor authentication. Examiner's Note: While Salesforce offers a specialized "Hybrid App Token Flow" that is a variation of the user-agent flow and can issue a refresh token, the question specifically references the "OAuth 2.0 user-agent flow (this flow uses the OAuth 2.0 implicit grant type)". The standard implicit grant type, by definition, does not include a refresh token. Therefore, based on a strict interpretation of the official specifications, only Client ID and Scopes are correct concepts from the list. The question is likely flawed as it asks for three answers.
1. Salesforce Help & Training
OAuth 2.0 User-Agent Flow for Desktop or Mobile App Integration: "The user-agent flow is used by applications that can’t keep the connected app secret confidential... Because the access token is passed in the redirect URL
it can be exposed... Salesforce doesn’t issue a refresh token in this flow." This document confirms that Client ID (clientid) and Scopes (scope) are required parameters
but a refresh token is not issued.
2. IETF
RFC 6749
The OAuth 2.0 Authorization Framework
Section 4.2.2
"Access Token Response": This specification for the Implicit Grant flow details the parameters returned in a successful response. The parameters include accesstoken
tokentype
expiresin
and scope. It makes no provision for a refreshtoken.
3. Salesforce Help & Training
OAuth Scopes: This document lists all available scopes
including refreshtoken
which must be explicitly requested in flows that support it (like the web server flow). This confirms 'Scopes' is a core concept.
4. Salesforce Help & Training
OAuth Terminology: Defines the "Consumer Key" as the clientid
which uniquely identifies a connected app. This confirms 'Client ID' is a core concept.
Keep practicing
Take the free IDENTITY-AND-ACCESS-MANAGEMENT-ARCHITECT practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other IDENTITY-AND-ACCESS-MANAGEMENT-ARCHITECT practice questions
- Question 2Universal Containers (UC) is planning to deploy a custom mobile app that will allow users…
- Question 3Universal containers (UC) is setting up Delegated Authentication to allow employees to lo…
- Question 4Universal Containers (UC) wants to use Salesforce for sales orders and a legacy of system…
- Question 5Universal containers (UC) is successfully using Delegated Authentication for their salesf…
- Question 6Universal Containers (UC) plans to use a SAML-based third-party IdP serving both of the S…
- Question 7Universal Containers (UC) would like its community users to be able to register and log i…
