Salesforce-Platform-Identity-and-Access-Management-Architect Exam Questions With Explanations
The best Salesforce-Platform-Identity-and-Access-Management-Architect practice exam questions with research based explanations of each question will help you Prepare & Pass the exam!
Over 15K Students have given a five star review to SalesforceKing
Why choose our Practice Test
By familiarizing yourself with the Salesforce-Platform-Identity-and-Access-Management-Architect exam format and question types, you can reduce test-day anxiety and improve your overall performance.
Up-to-date Content
Ensure you're studying with the latest exam objectives and content.
Unlimited Retakes
We offer unlimited retakes, ensuring you'll prepare each questions properly.
Realistic Exam Questions
Experience exam-like questions designed to mirror the actual Salesforce-Platform-Identity-and-Access-Management-Architect test.
Targeted Learning
Detailed explanations help you understand the reasoning behind correct and incorrect answers.
Increased Confidence
The more you practice, the more confident you will become in your knowledge to pass the exam.
Study whenever you want, from any place in the world.
Start practicing today and take the fast track to becoming Salesforce Salesforce-Platform-Identity-and-Access-Management-Architect certified.
21084 already prepared
Salesforce 2026 Release 108 Questions 4.9/5.0
Salesforce User Authentication
Northern Trail Outfitters (NTO) is using Experience Cloud as an Identity Provider for its application on
Heroku. The application on Heroku should be able to handle two brands,
Northern Trail Shoes and Northern Trail Shirts.
A user should select either of the two brands in Heroku before logging into the community. The app then
performs Authorization using OAuth2.0 with the Salesforce Experience Cloud site.
NTO wants to make sure it renders login page images dynamically based on the user ' s brand
preference selected in Heroku before Authorization.
What should an identity architect do to fulfill the above requirements?
A. Create multiple login screens using Experience Builders and use Login Flows at runtime to route to
different login screens.
B. Authorize third-party service by sending authorizations requests to the community. Authorizes/search?
authorize?node=value.
C. For each brand create different communities and redirect users to the appropriate community using a
custom Login controller written in Ages.
D. Authorize third-party service by sending authorizations requests to the community. Authorizes/search?
authorize?coside_value.
A. Create multiple login screens using Experience Builders and use Login Flows at runtime to route to
different login screens.
Explanation:
This question tests dynamic branding in an OAuth 2.0 flow where Heroku acts as the client and Experience Cloud as the IdP. The user selects a brand in Heroku before authorization. The IdP must render a login page with brand-specific images dynamically. Login Flows allow runtime decisions based on incoming parameters.
✔️ Correct Option:
✔️ A. Create multiple login screens using Experience Builders and use Login Flows at runtime to route to different login screens.
Login Flows evaluate the brand preference passed from Heroku (e.g., via display or custom parameter). Based on that value, the flow redirects the user to a brand-specific login screen built in Experience Builder. This enables dynamic image rendering before credentials are entered, meeting the requirement without multiple communities.
❌ Incorrect options:
❌ B. Authorize third-party service by sending authorization requests to the community. Authorizes/search? authorize?node=value.
This option contains malformed and non‑standard OAuth syntax. More critically, it does not address dynamic login screen rendering based on brand preference. Authorization parameters alone cannot change the login page UI at runtime.
❌ C. For each brand create different communities and redirect users to the appropriate community using a custom Login controller written in Apex.
Creating separate communities for each brand is over‑engineered and costly. While technically possible, Salesforce recommends Login Flows for dynamic branding within a single community. Custom Apex controllers add unnecessary maintenance complexity for this use case.
❌ D. Authorize third-party service by sending authorization requests to the community. Authorizes/search? authorize?coside_value.
This option contains a typo ("coside_value") and invalid OAuth syntax. Like option B, it only describes authorization request formatting and provides no mechanism to dynamically render brand‑specific login page images before authentication.
🔧 Reference:
→ Salesforce Help: Customize Login Experiences with Login Flows
Confirms that Login Flows can route users to different login pages, communities, or experience sites based on runtime criteria such as URL parameters, enabling dynamic branding.
Universal Containers is implementing a new Experience Cloud site and the identity architect wants to use dynamic branding features as part of the login process.
Which two options should the identity architect recommend to support dynamic branding for the site? Choose 2 answers
A. To use dynamic branding, the community must be built with the Audience + Salesforce Tabs template.
B. Do use dynamic branding, the community must be built with the Customer Account Portal template.
C. An external content management system (CMS) must be used for dynamic branding on Experience Cloud sites.
D. An experience ID (expid) or placeholder parameter must be used in the URL to represent the brand.
Explanation:
Dynamic branding in Experience Cloud allows different brands or sub-brands to display unique logos, colors, and content based on a URL parameter, without creating separate sites. This is useful when multiple partner or customer entities access the same Experience Cloud site but require distinct visual identities during and after login.
Correct Options:
B. To use dynamic branding, the community must be built with the Customer Account Portal template.
The Customer Account Portal template is specifically designed to support dynamic branding features. This template includes the necessary components and architecture to switch branding assets based on the account or URL parameter. Other templates like Partner Central or Tabs + Salesforce Tabs do not offer this capability natively.
D. An experience ID (expid) or placeholder parameter must be used in the URL to represent the brand.
Dynamic branding is triggered by adding an expid (experience ID) parameter or a custom placeholder in the Experience Cloud URL. This value maps to a specific brand configuration, enabling different logos, themes, and navigation menus. Without this parameter, the system cannot determine which brand to display.
Incorrect Options:
A. To use dynamic branding, the community must be built with the Audience + Salesforce Tabs template.
This template is designed for audience targeting and role-based content, not for dynamic branding. It does not support the expid parameter or brand switching. Dynamic branding is a feature of the Customer Account Portal template only, not the Audience template.
C. An external content management system (CMS) must be used for dynamic branding on Experience Cloud sites.
An external CMS is not required. Dynamic branding is handled natively within Experience Cloud using brand sets, themes, and the expid parameter. While an external CMS could theoretically be integrated, it is not a requirement and adds unnecessary complexity.
Reference:
Salesforce Help Article: "Add Dynamic Branding to Your Experience Cloud Site"
Trailhead: "Build Branded Experiences with Experience Cloud" – Unit on "Dynamic Branding"
An identity architect has built a native mobile application and plans to integrate it with a Salesforce Identity
solution. The following are the requirements for the solution:
1. Users should not have to login every time they use the app.
2. The app should be able to make calls to the Salesforce REST API.
3. End users should NOT see the OAuth approval page.
How should the identity architect configure the Salesforce connected app to meet the requirements?
A. Enable the API Scope and Offline Access Scope on the connected app, and then set the Connected App
access settings to " User may self authorize " .
B. Enable the Full Access Scope and then set the connected app access settings to " Admin Pre-Approved
" .
C. Enable the API Scope and Offline Access Scope on the connected app, and then set the connected app
to access settings to " Admin Pre-Approved " .
D. Enable the API Scope and Offline Access Scope, upload a certificate so JWT Bearer Flow can be used
and then set the connected app access settings to " Admin Pre-Approved " .
C. Enable the API Scope and Offline Access Scope on the connected app, and then set the connected app
to access settings to " Admin Pre-Approved " .
Explanation:
Let’s map each requirement to the configuration options:
Requirement 1: Users should not have to log in every time they use the app
This requires Offline Access scope (refresh_token). The refresh token allows the app to obtain new access tokens without the user reauthenticating.
Requirement 2: The app should be able to make calls to the Salesforce REST API
This requires the API scope (api). This grants the app permission to access Salesforce REST APIs on the user's behalf.
Requirement 3: End users should NOT see the OAuth approval page
This requires "Admin Pre-Approved" permitted users setting. When an admin pre-approves users for the connected app, the OAuth consent/approval screen is skipped entirely. Users simply authenticate and the app is authorized without any additional prompt.
Now let’s analyze each option:
Option A (Incorrect)
"User may self-authorize" — This setting does the opposite of Requirement 3. When set, users are shown the OAuth approval/consent page asking them to allow the app to access their data. This violates the requirement that users should NOT see the approval page.
Option B (Incorrect)
"Full Access Scope" — There is no standard OAuth scope called "Full Access" in Salesforce. This is a fabricated term. The correct scopes are api, refresh_token, openid, etc. Using an invalid scope would not work.
Option C (Correct)
This configuration perfectly meets all three requirements:
API Scope → Enables REST API access
Offline Access Scope → Provides refresh tokens so users don't need to re-login
Admin Pre-Approved → Suppresses the OAuth approval prompt
Option D (Incorrect)
While JWT Bearer Flow can also achieve these requirements (it's a server-side flow that doesn't typically show a consent screen), the option adds an unnecessary requirement to "upload a certificate so JWT Bearer Flow can be used." The question asks for a native mobile app integration, and JWT Bearer Flow is not recommended for mobile apps because the signing certificate must be stored on the device, which is a security risk. The User-Agent flow or Web Server flow with refresh tokens is more appropriate for mobile apps.
Reference
Salesforce Help: Connected App OAuth Scopes — "API scope allows access to the current, logged-in user's account using REST APIs. Offline Access scope issues a refresh token so the app can interact with the user's data while the user is offline or not actively using the app."
Northern Trail Outfitters (NTO) would like to use a portal built on Salesforce Experience Cloud for customer self-service. Guests of the portal should be able to self-register, but be unable to automatically be assigned to a contact record until verified. External Identity licenses have been purchased for the project.
After registered guests complete an onboarding process, a flow will create the appropriate account and contact records for the user.
Which three steps should an identity architect follow to implement the outlined requirements?
Choose 3 answers
A. Customize the self-registration Apps handler to create only the user record.
B. Select the “Configurable Self-Reg Page” option under Login & Registration.
C. Set up an external login page and call Salesforce APIs for user creation.
D. Select new customers and partners to self-register.
E. Customize the self-registration Apps handler to temporarily associate the user to a shared single contact record.
Explanation:
NTO requires guests to self-register without being automatically assigned to a contact record until verification is complete. An external identity license allows user-only creation. The solution must use a customizable registration handler and the configurable self-registration page, while selecting the appropriate registration type for new customers.
Correct Options:
A. Customize the self-registration Apps handler to create only the user record.
The standard registration handler creates both a user and a contact. To prevent automatic contact assignment until verification, the architect must customize the registration handler (Auth.RegistrationHandler) to create only the user record initially. The external identity license supports user-only records without associated contacts.
B. Select the “Configurable Self-Reg Page” option under Login & Registration.
This setting enables the use of a custom self-registration page with Apex handlers. Without selecting this option, the standard registration flow forces immediate contact creation. Configurable Self-Reg Page allows the architect to plug in the customized handler that creates only the user record.
D. Select new customers and partners to self-register.
Under Login & Registration settings, the registration type must be set to allow "New customers and partners to self-register." This enables the self-registration link on the login page and permits external users to initiate the registration process. The other option ("No users can register") would block the flow.
Incorrect Options:
C. Set up an external login page and call Salesforce APIs for user creation.
This option is unnecessarily complex and incorrect. Experience Cloud provides native self-registration pages. Building an external login page with API calls bypasses built-in security, validation rules, and standard flows. The requirement can be met entirely within Experience Cloud using a custom handler.
E. Customize the self-registration Apps handler to temporarily associate the user to a shared single contact record.
This violates the requirement that guests should not be assigned to a contact record until after verification. Assigning a shared contact is still assignment. The requirement explicitly states "be unable to automatically be assigned to a contact record until verified." Only creating the user (without any contact) satisfies this.
Reference:
Salesforce Help Article: "Customize Self-Registration with Apex"
Trailhead: "Identity for External Users" – Unit on "Registration Handlers"
Salesforce Developer Guide: "Auth.RegistrationHandler Interface – Creating Users Without Contacts"
A global company is using the Salesforce Platform as an Identity Provider and needs to integrate a third-party
application with its Experience Cloud customer portal.
Which two features should be utilized to provide users with login and identity services for the third-party
application?
Choose 2 answers
A. Use the App Launcher with single sign-on (SSO).
B. Use Delegated Authentication.
C. Use a connected app.
D. External a Data source with Named Principal identity type.
A. Use the App Launcher with single sign-on (SSO). C. Use a connected app.
Explanation:
This question explores the necessary features to extend Salesforce’s Identity Provider (IdP) capabilities to external, third-party applications integrated within a customer portal.
✅ Option A: Use the App Launcher with single sign-on (SSO).
The App Launcher serves as a centralized "portal within a portal" where users can view and launch authorized applications. By enabling the App Launcher for Experience Cloud users and configuring SSO, an architect provides a seamless user experience. When a customer clicks a third-party app tile in the App Launcher, Salesforce handles the SAML or OAuth handshake in the background, allowing the user to access the external service without re-entering credentials.
✅ Option C: Use a connected app.
A Connected App is the technical anchor required for any integration where Salesforce acts as the Identity Provider. It stores the metadata of the third-party application (such as the Entity ID, ACS URL, or OAuth Callback URL). By creating a Connected App, the architect defines the security policies, permitted profiles, and scopes that dictate how the third-party application communicates with Salesforce and what user data it can access.
❌ Option B: Use Delegated Authentication.
Delegated Authentication is used when you want Salesforce to "outsource" its own password verification to an external SOAP service. In this scenario, Salesforce is the Identity Provider for a third-party app, so delegating authentication away from Salesforce would be contradictory to the requirement of using Salesforce as the source of identity.
❌ Option D: External Data source with Named Principal identity type.
This feature is used for "Salesforce Connect," which allows Salesforce to display data from an external system as if it were stored in local objects. While "Named Principal" allows multiple users to share a single credential to access that data, it is a data integration feature rather than a user-facing identity/SSO service for authenticating into an external application.
🔧 Reference:
→ Salesforce Help: Connected App
This documentation confirms that connected apps are the fundamental way to integrate third-party applications with Salesforce identity services.
Prep Smart, Pass Easy Your Success Starts Here!
Transform Your Test Prep with Realistic Salesforce-Platform-Identity-and-Access-Management-Architect Exam Questions That Build Confidence and Drive Success!