Free Salesforce Platform Identity and Access Management Architect Practice Test Questions
108 questionsUpdated 18-Nov-20266 topics
TopicIdentity Management Concepts
Question 21Choose 3
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
Correct answer:
A. Scopes
B. Client ID
E. Refresh Token
Explanation:
This question explores the fundamental components of the OAuth 2.0 User-Agent Flow, which is typically utilized by mobile and desktop applications. It tests the architect's ability to identify which parameters are required to define permissions and establish long-term access in a browser-based redirection model.
✅ Option A: Scopes:
Scopes are essential in the User-Agent flow as they define the specific permissions the mobile application is requesting, such as api, web, or refresh_token. During the flow, these scopes are presented to the user on the authorization screen, allowing them to explicitly grant or deny the application access to specific parts of their Salesforce data.
✅ Option B: Client ID:
The Client ID (known as the Consumer Key in Salesforce) is a unique identifier for the Connected App. In the User-Agent flow, the mobile app must provide this ID in the initial authorization request so Salesforce can identify which application is requesting access and apply the correct security policies and redirect URIs configured for that specific app.
✅ Option E: Refresh Token:
While the standard OAuth 2.0 Implicit Grant does not typically support refresh tokens, the Salesforce User-Agent flow does allow an application to request a refresh_token scope. If granted, Salesforce returns a refresh token alongside the access token, enabling the mobile app to maintain long-term access without requiring the user to re-authenticate every time the short-lived access token expires.
❌ Option C: Authorization Code:
The Authorization Code is a concept exclusive to the OAuth 2.0 Web Server Flow, where a temporary code is exchanged for an access token on a secure backend server. In the User-Agent flow (Implicit Grant), no intermediate code is used; the access token is returned directly in the URL fragment after the user authenticates.
❌ Option D: Verification Code:
A "Verification Code" is generally used in the Device Flow (for devices with no browser) or during Multi-Factor Authentication (MFA) challenges. It is not a core architectural component of the standard OAuth 2.0 User-Agent flow used to establish the identity and permission handshake between a mobile client and Salesforce.
🔧 Reference:
→ Salesforce Help: OAuth 2.0 User-Agent Flow
This documentation confirms that Client ID, Scopes, and Refresh Tokens are integral parts of the User-Agent flow used to secure mobile and desktop apps.
Question 22Choose 3
Northern Trail Outfitters (NTO) has an existing business-to-consumer (B2C) website that does NOT support
single sign-on standards, such as Security Assertion Markup Language (SAML) or OAuth. NTO wants to use
Salesforce Identity to register and authenticate new customers on the website.
Which three Salesforce features should an Identity architect use in order to provide social sign-in capabilities
for the website?
Choose 3 answers
Correct answer:
A. Connected Apps
B. Authentication Providers
D. Embedded Login
Explanation:
This scenario is about enabling social sign-in for a B2C website that does not support SAML or OAuth natively. Salesforce Identity must provide external authentication, user registration, and seamless login integration.
You need features that support:
Social identity federation
External app trust
Embedded customer login experience
🟢 Correct Options:
A. Connected Apps
Connected Apps establish the trust framework between Salesforce and external applications. They are required to configure authentication flows, define access policies, and enable secure integration for external websites using Salesforce Identity services.
B. Authentication Providers
Authentication Providers enable social login and external identity federation (Google, Facebook, etc.). They allow users to authenticate using third-party identity systems and map external identities into Salesforce customer records. This is the core feature for social sign-in.
D. Embedded Login
Embedded Login allows Salesforce authentication and registration UI to be embedded directly into a B2C website. It is essential when the external system does not support SAML or OAuth, providing seamless login without requiring protocol implementation on the website.
🔴 Incorrect Options:
C. Delegated Authentication
Delegated Authentication forwards password validation to an external system. It is not designed for social login or identity federation and does not support modern customer authentication experiences.
E. Identity Connect
Identity Connect is used for syncing enterprise users between Active Directory and Salesforce. It is intended for internal workforce identity management, not B2C social sign-in or customer authentication.
🔧 Reference:
→ Salesforce Identity – Authentication Providers and Social Sign-On
This document explains how Salesforce uses Authentication Providers, Connected Apps, and Embedded Login to enable social sign-in and external customer authentication for B2C websites.
TopicSSO and Federation Integration
Question 23Choose 1
Universal Containers (UC) is building a custom employee hub application on Amazon Web Services (AWS)
and would like to store their users ' credentials there. Users will also need access to Salesforce for internal
operations. UC has tasked an identity architect with evaluating different solutions for authentication and
authorization between AWS and Salesforce.
How should an identity architect configure AWS to authenticate and authorize Salesforce users?
Correct answer:
D. Configure AWS as an OpenID Connect Provider.
Explanation:
In this scenario, UC wants to:
Store user credentials in AWS (so AWS is the identity source).
Allow users to access Salesforce for internal operations using those AWS-stored credentials.
This means AWS will act as the Identity Provider (IdP), and Salesforce will be the Service Provider (SP) that trusts AWS to authenticate users. To integrate an external IdP (AWS) with Salesforce for user authentication and authorization, you configure the external IdP as an OpenID Connect (OIDC) Provider in Salesforce. This allows Salesforce to accept OIDC tokens from AWS and map them to Salesforce users for Single Sign-On (SSO).
Analysis of Other Options Create a custom external authentication provider: This is a misdirection. While you do create an Authentication Provider in Salesforce, it is not "custom" in the sense of building a new authentication system. Instead, you configure a standard OpenID Connect Authentication Provider in Salesforce and point it to AWS Cognito or another OIDC-compliant service.
Develop a custom Auth server in AWS: This approach is unnecessary and overly complex. AWS already provides managed identity services such as Amazon Cognito, which fully supports OpenID Connect. There is no need to build a custom authorization server when a standards-based solution already exists.
Configure the custom employee app as a connected app: A Connected App in Salesforce is used when Salesforce acts as the Identity Provider or when external applications need API access. In this case, AWS is the Identity Provider, so the employee app does not need to be configured as a Connected App for authentication into Salesforce. Instead, Salesforce must be configured to trust AWS.
Conclusion
The correct approach is to configure AWS (using Cognito User Pools) as an OpenID Connect Provider in Salesforce Authentication Provider settings. This establishes AWS as the identity source and allows users stored in AWS to authenticate seamlessly into Salesforce using Single Sign-On.
Reference
Salesforce Help: Set Up an OpenID Connect Authentication Provider
Salesforce Identity Implementation Guide: Authentication Providers for inbound SSO
Question 24Choose 1
Universal Containers wants to secure its Salesforce APIs by using an existing Security Assertion Markup
Language (SAML) configuration that supports the company ' s single signon process to Salesforce.
Which Salesforce OAuth authorization flow should be used?
Correct answer:
B. OAuth 2.0 SAML Bearer Assertion Flow
Explanation:
Let’s analyze the requirement and each option:
Requirement: UC wants to secure Salesforce APIs while leveraging an existing SAML configuration that already supports their single sign-on (SSO) process to Salesforce.
Option B - OAuth 2.0 SAML Bearer Assertion Flow (Correct)
This flow allows a client application to obtain an OAuth access token by presenting a valid, signed SAML assertion that was issued by the company's existing SAML Identity Provider (IdP). Since UC already has a SAML configuration for SSO, this flow reuses that same IdP and trust relationship. The app gets a SAML assertion from the existing IdP, sends it to Salesforce's OAuth token endpoint, and receives an OAuth access token to call APIs. This perfectly fulfills the requirement of securing APIs using the existing SAML infrastructure.
Option A - OAuth 2.0 JWT Bearer Flow (Incorrect)
This flow uses a JSON Web Token (JWT) signed with a certificate, not a SAML assertion. While it is a valid OAuth flow for server-to-server integration, it does not leverage an existing SAML configuration. It requires separate certificate management and does not reuse the SAML SSO IdP.
Option C - OAuth 2.0 User-Agent Flow (Incorrect)
This flow is designed for client-side applications (like JavaScript SPAs or mobile apps) where the OAuth process runs entirely in the user agent (browser). It does not involve SAML at all and does not leverage an existing SAML configuration. It's typically used for browser-based apps that can't securely store a client secret.
Option D - SAML Assertion Flow (Incorrect)
"SAML Assertion Flow" is not a standard OAuth 2.0 authorization grant type defined in the Salesforce OAuth specification. The official name is OAuth 2.0 SAML Bearer Assertion Flow (sometimes called SAML 2.0 Bearer Assertion Flow for OAuth 2.0). This option appears to be a distractor that sounds similar but is not the precise technical term.
Summary
The OAuth 2.0 SAML Bearer Assertion Flow is purpose-built exactly for this scenario: it bridges SAML and OAuth, allowing an organization to reuse its existing SAML IdP investment to secure API access via OAuth tokens.
Reference
Salesforce Help: OAuth 2.0 SAML Bearer Assertion Flow — "Use this flow to get an access token using a SAML assertion when you already have a SAML single sign-on configuration."
Salesforce Developer Documentation: OAuth 2.0 SAML Bearer Assertion Flow — "This flow allows use of a SAML 2.0 identity provider to authorize API access to Salesforce."
TopicAccess Management and Security Controls
Question 25Choose 1
A company ' s external application is protected by Salesforce through OAuth. The identity architect for the project needs to limit the level of access to the data of the protected resource in a flexible way.
What should be done to improve security?
Correct answer:
B. Create custom scopes and assign to the connected app.
Explanation:
When an external application accesses Salesforce via OAuth, the level of data access is governed by OAuth scopes. Predefined scopes (e.g., api, refresh_token) offer coarse control. To flexibly limit access, custom OAuth scopes can be created, allowing fine-grained permissions tailored to specific resources or operations, improving security by following least privilege.
Correct Option:
B. Create custom scopes and assign to the connected app.
Custom OAuth scopes allow architects to define granular permissions (e.g., read_orders, update_inventory) that map to specific Apex classes or API resources. By assigning these custom scopes to the connected app, the external application receives only the permissions it needs. This follows the principle of least privilege and provides flexible access control beyond Salesforce's standard scopes.
Incorrect Option:
A. Select "Admin approved users are pre-authorized" and assign specific profiles.
This setting controls the OAuth approval flow (whether users must approve access), but it does not limit data access scope. Assigning profiles controls user permissions within Salesforce, not the access level of the external application via OAuth. This option confuses user authorization with OAuth scoping.
C. Leverage external objects and data classification policies.
External objects represent data outside Salesforce, and data classification policies label sensitivity (e.g., PII). Neither directly limits OAuth access from an external application to protected resources. These are unrelated to OAuth scope configuration.
D. Define a permission set that grants access to the app and assign to authorized users.
Permission sets grant permissions (object, field, page) to users inside Salesforce. They are not used to restrict OAuth scopes for external applications. The external app's access is defined by the connected app's OAuth scopes, independent of user permission sets (though user permissions still apply as a second factor).
Salesforce Help Article: "Create Custom OAuth Scopes for Connected Apps"
Trailhead: "OAuth 2.0 for API Integration" – Unit on "Scopes and Permissions"
TopicMonitoring, Auditing and Lifecycle Management
Question 26Choose 1
A company with 15,000 employees is using Salesforce and would like to take the necessary steps to highlight or curb fraudulent activity.
Which tool should be used to track login data, such as the average number of logins, who logged in more than the average number of times and who logged in during non-business hours?
Correct answer:
B. Login Forensics
Explanation:
To detect fraudulent activity like unusual login frequency or off-hours access, Salesforce provides Event Monitoring which includes LoginForensics (part of Login Analytics). LoginForensics analyzes login patterns, calculates averages, and surfaces anomalous behavior such as users exceeding average login counts or logging in outside business hours.
Correct Option:
B. Login Forensics
Login Forensics is a feature within Salesforce Event Monitoring (Login Analytics). It uses machine learning and statistical analysis to identify anomalies in login behavior. It can show average logins per user, flag users logging in during non-business hours, and highlight users who exceed the average. This is specifically designed for security monitoring and fraud detection.
Incorrect Options:
A. Login Inspector
There is no standard Salesforce feature called "Login Inspector." This may be confused with Login Forensics or a third-party tool. It is not a valid native tool for tracking average logins or off-hours activity.
C. Login Report
Standard login reports (from Login History) can show raw login events but cannot calculate averages, compare users against averages, or automatically highlight anomalies. Login reports require manual analysis and do not provide the behavioral analytics needed for fraud detection.
D. Login History
Login History is a standard setup audit trail showing raw login events (timestamp, user, IP, status). It does not compute averages, flag off-hours logins automatically, or identify anomalous patterns. While useful for basic auditing, it lacks the advanced analytics required for this use case.
Reference:
Salesforce Help Article: "Monitor Login Activity with Event Monitoring – Login Forensics"
Trailhead: "Event Monitoring for Security" – Unit on "Login Forensics"
Our timed 2026 Salesforce Platform Identity and Access Management Architect practice test mirrors the format, number of questions and time limit of the official exam.
The #1 challenge isn't just knowing the material, it's managing the clock. The simulation builds your speed and stamina, so you walk in knowing exactly what to expect.
Build exam stamina: stay focused and accurate for the entire duration.
Master time management: learn to pace yourself so you never have to rush.
A new test every time: a randomised set from the Salesforce Platform Identity and Access Management Architect - Plat-Arch-203 question pool on every attempt.
Unlimited attempts: practice until you're 100% confident, not just once.