Salesforce Certified Platform Identity and Access Management Architect (Plat-Arch-203) Exam Topics and Questions
These Salesforce Certified Platform Identity and Access Management Architect (Plat-Arch-203) exam topics are organized according to official exam domains to help candidates quickly verify coverage and focus on assessment rather than theory. Each domain is paired with topic-wise Salesforce Certified Platform Identity and Access Management Architect (Plat-Arch-203) sample questions that reflect how objectives are tested in the actual exam. This structure enables efficient review, targeted self-assessment, and rapid identification of weak areas when preparing for the Salesforce Certified Platform Identity and Access Management Architect certification exam.
Let's Practice Free Salesforce Certified Platform Identity and Access Management Architect (Plat-Arch-203) Questions Aligned with Official Exam Topics
This topic sets the foundation everything else depends on. The exam tests whether you can reason about authentication and authorization decisions in context, not whether you can recite definitions. Where candidates lose ground here is in the distinctions: confusing how trust is established between systems, or picking the wrong provisioning method for a given scenario. Seventeen percent of the exam lives here, so gaps in these fundamentals compound across every later topic. β Authentication patterns and trust The exam expects...
This topic sets the foundation everything else depends on. The exam tests whether you can reason about authentication and authorization decisions in context, not whether you can recite definitions. Where candidates lose ground here is in the distinctions: confusing how trust is established between systems, or picking the wrong provisioning method for a given scenario. Seventeen percent of the exam lives here, so gaps in these fundamentals compound across every later topic.
β Authentication patterns and trust
The exam expects you to tell authentication mechanisms apart in the way that changes a real architectural decision. Knowing that SAML and OAuth exist is not enough; you need to know when each one fits and where the boundary between them sits. Trust between two systems is a specific technical relationship, and the exam will give you a scenario where you must identify how that trust is established, whether through certificates, metadata exchange, or token validation. The non-obvious angle is directionality: trust is not always mutual, and the exam probes whether you understand which party is asserting identity and which is consuming it. Authentication patterns such as SP-initiated versus IdP-initiated SSO carry different failure modes, and confusing them in a scenario question costs you the mark.
β Building blocks, provisioning, and troubleshooting
Authentication, authorization, and accountability are the three pillars the exam maps Salesforce features against. For each one, you need to know which platform capability delivers it, not just what the concept means in the abstract. Provisioning is where many candidates underestimate the detail required: just-in-time provisioning, manual creation, and API-driven approaches each have conditions that make them appropriate, and the exam gives you those conditions in the scenario. Read them carefully before choosing. Troubleshooting single sign-on failures is a practical sub-skill the exam tests directly. Common SAML failure points include certificate mismatches, clock skew, and incorrect entity IDs. OAuth failures often trace to redirect URI mismatches or scope misconfiguration. Knowing the symptom-to-cause mapping is what earns marks in these items, not a general familiarity with the protocols.
How Identity Management Concepts: is tested
At 17%, this topic produces a meaningful share of your exam. Items are almost always scenario-driven: you are given a business situation or a technical symptom and asked to choose the right pattern, method, or diagnosis. Straightforward recall items are rare. The demand is that you translate a described situation into a specific Salesforce capability or protocol decision. Candidates lose marks in two predictable places. First, they treat authentication and authorization as interchangeable, which causes them to pick the wrong building block for a given requirement. Second, they approach troubleshooting items by eliminating obviously wrong options rather than by reasoning from the symptom. The exam rewards candidates who can trace a failure back to its root cause, such as identifying that a SAML assertion is being rejected because the SP and IdP clocks are out of sync, without needing to be told what category of problem to look for. Read every scenario detail before committing to an answer.
The ITExamsTopics practice test covers all five sub-areas of this topic. Running through a full bank of scenario items lets you spot exactly which authentication pattern or provisioning method you keep second-guessing, before that uncertainty costs you on exam day. A free demo is available in both PDF and practice test formats.
The question below tests your ability to apply one of the core distinctions from this topic to a realistic scenario.
An architect needs to set up a Facebook Authentication provider as login option for a salesforce customer Community. What portion of the authentication provider setup associates a Facebook user with a salesforce user?
Building on the foundational patterns from the previous topic, this area shifts the lens to Salesforce acting as the consumer of identity rather than the producer. At 21%, it is the single heaviest topic on the exam. The practical consequence is that you cannot afford to be vague here. You need to know when Salesforce is a Service Provider, how users get provisioned from external directories in both employee and customer scenarios, and how to audit what happens after login....
Building on the foundational patterns from the previous topic, this area shifts the lens to Salesforce acting as the consumer of identity rather than the producer. At 21%, it is the single heaviest topic on the exam. The practical consequence is that you cannot afford to be vague here. You need to know when Salesforce is a Service Provider, how users get provisioned from external directories in both employee and customer scenarios, and how to audit what happens after login.
β Service Provider role and authentication mechanisms
When Salesforce is the Service Provider, it is trusting an external Identity Provider to assert who the user is. The exam tests whether you can identify this configuration from a scenario description and then recommend the right authentication mechanism to support it. Enterprise directories, social identity providers, and community or partner portals each carry different integration patterns. The mechanism you recommend must match the identity store type and the user population. For B2E scenarios, SAML with an enterprise IdP such as Active Directory Federation Services is the typical path. For B2C scenarios, social authentication or a customer identity platform introduces different token flows. Mixing up the appropriate mechanism for the population is a common source of lost marks. The exam will describe the use case in enough detail to distinguish them, so the skill is reading that detail and matching it to the right option.
β User provisioning strategies
Provisioning is tested in both B2E and B2C contexts, and the right answer changes depending on the scenario. Just-in-time provisioning suits scenarios where users are authenticated through SAML and you want accounts created automatically on first login. API-based provisioning fits situations where you need to create accounts in advance or sync them from an external system on a schedule. Manual provisioning is rarely the right answer for a large user population, but the exam may present it as a distractor in scenarios where scale is mentioned. The question to ask yourself is: what does the scenario say about when users need access and where the authoritative source of user data lives? That combination drives the provisioning choice. Candidates who pick a provisioning method before reading the full scenario tend to choose the one they are most familiar with rather than the one the scenario requires.
β Auditing, monitoring, and IdP diagnostics
The exam expects you to know which Salesforce tools surface login activity, identity verification events, and authentication anomalies. Login History, Event Monitoring, and the Identity Provider Event Log each serve a different diagnostic purpose, and the exam distinguishes between them in scenario items. A question might describe a situation where an IdP is intermittently rejecting assertions and ask which tool gives you the data you need to diagnose it. The answer depends on what kind of data the tool exposes: raw login attempts, SAML assertion details, or OAuth token activity. Auditing is also framed around accountability, the third building block from the previous topic. Knowing which log to consult for which type of event is the specific skill being tested, not a general awareness that logging exists on the platform.
How Accepting Third-Party Identity in Salesforce: is tested
With the highest weight on the exam, this topic will appear frequently enough that your comfort level with it directly shapes your final score. Items are consistently scenario-based and require you to make a recommendation, not just identify a feature. The exam rewards candidates who can read a described identity architecture and immediately recognize which role Salesforce is playing and which mechanism fits. Provisioning items are a particular trap: the scenario will include details about user volume, the source identity store, and the timing of access needs, and each detail is there to steer you toward or away from a specific method. Candidates who ignore one of those details tend to pick the provisioning approach that sounds most sophisticated rather than the one the scenario actually calls for. Auditing items reward knowing which specific tool matches which specific diagnostic need. Familiarity with the platform at a general level is not enough; the exam tests the distinctions between tools, not awareness that the tools exist.
Because this topic carries the most weight, it is worth checking your coverage across all five sub-areas before exam day. Working through the ITExamsTopics question bank under timed conditions shows you whether your speed and accuracy hold up on provisioning and auditing items, not just the authentication ones. PDF and practice test formats are included on one purchase.
The question below places you in one of the scenario types this topic tests most frequently.
Universal Containers (UC) wants to build a custom mobile app for their field reps to create orders in salesforce. After the first time the users log in, they must be able to access salesforce upon opening the mobile app without being prompted to log in again. What Oauth flows should be considered to support this requirement?
The previous topic covered Salesforce consuming external identity. This one reverses the direction: Salesforce is now the authority asserting who the user is to other systems. The practical shift is significant. You move from configuring inbound trust to configuring outbound token issuance, OAuth flows, and Connected App settings. At 17%, the exam expects architectural-level decisions here, particularly around which OAuth flow to use and how to configure the Connected App to support it correctly. β OAuth flows and when each...
The previous topic covered Salesforce consuming external identity. This one reverses the direction: Salesforce is now the authority asserting who the user is to other systems. The practical shift is significant. You move from configuring inbound trust to configuring outbound token issuance, OAuth flows, and Connected App settings. At 17%, the exam expects architectural-level decisions here, particularly around which OAuth flow to use and how to configure the Connected App to support it correctly.
β OAuth flows and when each one applies
The exam does not ask you to recite what each OAuth flow does. It gives you a scenario and expects you to select the right one. The Web Server flow suits server-side applications where a client secret can be stored securely. The User-Agent flow is for client-side apps where a secret cannot be kept safe. The JWT Bearer flow removes the user interaction step and suits machine-to-machine integrations where a service account needs to act on behalf of users. The Device Authentication flow fits input-constrained devices that cannot open a browser. The key is matching the flow to the constraints described in the scenario: who is initiating the request, whether a browser is available, whether a secret can be protected, and whether a human user is in the loop. Candidates who memorize flow names without understanding the selection criteria pick the wrong one when the scenario adds a constraint they did not anticipate.
β OAuth implementation details and Connected App configuration
Scopes, tokens, refresh tokens, token expiration, and revocation are all individually testable. The exam is interested in the decisions these concepts drive. Scope defines what the token permits, and the exam may describe a use case where a narrow scope is required for security reasons, then ask which scope setting achieves it. Token expiration and refresh token behavior determine how long a session stays alive and what happens when it ends, both of which matter in scenarios involving long-running integrations or offline access. Revocation is the mechanism for ending access immediately, which appears in scenarios about deprovisioning or compromised credentials. Connected App configuration is the practical container for all of these settings. The exam tests which configuration options control which behaviors, including callback URLs, IP relaxation, and permitted user policies. Getting the Connected App settings wrong in a scenario means the OAuth flow cannot complete, and the exam knows this.
β Technologies for providing identity to third-party systems
Canvas, Connected Apps, and App Launcher each serve a different purpose when Salesforce is acting as the IdP for an external system. Canvas allows Salesforce to embed an external application and pass identity context to it using a signed request. Connected Apps define the OAuth or SAML trust relationship with the external system. App Launcher surfaces those Connected Apps to users in a consistent way. The exam tests whether you can match the technology to the requirement. A scenario describing an external web app that needs to display inside Salesforce and receive user context points toward Canvas. A scenario describing a standalone external system that needs Salesforce to assert user identity via SAML points toward a Connected App with SAML enabled. The distinction matters because each technology imposes different configuration requirements and different constraints.
How Salesforce as an Identity Provider: is tested
At 17%, this topic matches the weight of the first, and the item style is similarly scenario-driven. The highest-value skill here is OAuth flow selection. Items in this area describe a system integration scenario with specific constraints, and the exam rewards picking the flow that fits all of those constraints, not just most of them. A single unconsidered detail, such as whether the application can store a client secret, changes the answer. Connected App configuration items test whether you know which setting controls which behavior. The trap is treating Connected App options as interchangeable or assuming that a more permissive setting is always safer to choose. Scope and token items reward candidates who understand the security implication of each option, not just its function. The technology-selection sub-topic rewards knowing the difference between Canvas, Connected Apps, and App Launcher at the level of what each one actually does in an integration, not just that all three exist as Salesforce features.
Seeing how OAuth flow selection and Connected App configuration are framed as exam items is more useful than re-reading documentation. The ITExamsTopics practice test gives you a bank of scenario items across this topic so you can check whether your flow-selection reasoning holds up before the real exam. The free demo lets you try it first.
The question below presents a scenario that turns on one of the OAuth flow selection criteria covered in this topic.
Where the previous topics focused on how identity moves between systems, this one focuses on what happens once a user is inside Salesforce. The exam tests whether you can control access precisely: choosing the right MFA method, assigning roles and permissions correctly during and after SSO, auditing what users do, and configuring Connected Apps to enforce the right policies. At 15%, this topic rewards candidates who know Salesforce access controls at the configuration level, not just the concept level. β...
Where the previous topics focused on how identity moves between systems, this one focuses on what happens once a user is inside Salesforce. The exam tests whether you can control access precisely: choosing the right MFA method, assigning roles and permissions correctly during and after SSO, auditing what users do, and configuring Connected Apps to enforce the right policies. At 15%, this topic rewards candidates who know Salesforce access controls at the configuration level, not just the concept level.
β Multi-factor authentication and session management
MFA method selection is not a single answer that applies everywhere. The exam gives you a requirement set and expects you to match it to the appropriate MFA type: Salesforce Authenticator, TOTP apps, hardware security keys, or built-in authenticators. Each has different usability and security trade-offs that appear in scenario constraints. The session type that MFA yields is equally important. A high-assurance session is required for certain sensitive operations, and the exam tests whether you know which session level results from which authentication method. Candidates who treat all MFA methods as equivalent, assuming any one will satisfy any requirement, lose marks on items where the session type is the deciding factor. Read the requirement for session assurance level before selecting an MFA method, because the method and the session are both part of the answer.
β Roles, profiles, permission sets, and post-SSO assignment
Assigning access rights during the SSO process is a specific capability the exam tests in detail. Just-in-time provisioning can carry attribute mappings that assign a profile or permission set at the moment the user is created. The exam asks you to design this correctly for a given scenario, including how to keep those assignments current as the user's role in the external directory changes. The question of freshness matters: if a user's department changes in the IdP, how does that change propagate to their Salesforce permissions? The answer depends on which provisioning mechanism is in use and how attribute mapping is configured. Candidates who know how to set up initial assignment but have not thought through ongoing synchronization tend to pick answers that solve the day-one problem but leave a maintenance gap.
β Auditing, verification, and Connected App settings
Login Forensics, Transaction Security policies, and Event Monitoring each serve a distinct audit purpose, and the exam distinguishes between them. A scenario describing a need to detect anomalous login behavior points toward one tool; a scenario describing a need to enforce a policy in real time during a session points toward another. Connected App configuration in this topic is framed around access control rather than OAuth mechanics. IP ranges, permitted user policies, and OAuth policy settings on the Connected App determine who can use it and under what conditions. The exam may describe a security requirement and ask which Connected App setting enforces it. Knowing the setting name is less important than knowing what behavior it controls and what it does not control, because the exam often includes a distractor that sounds similar but applies to a different layer of access.
How Access Management Best Practices: is tested
At 15%, this topic produces a steady stream of items that test configuration decisions rather than conceptual knowledge. The exam rewards candidates who can read a security or compliance requirement and map it directly to a Salesforce control. MFA items are a reliable place to pick up marks if you know the session-assurance implications of each method, and a reliable place to lose them if you do not. Permission assignment items reward end-to-end thinking: initial provisioning and ongoing synchronization are both part of the scenario, and an answer that only addresses one of them is incomplete. Audit and monitoring items are framed as diagnostic or policy-design problems. The exam is testing whether you can select the right tool for the described need, not whether you are aware that auditing tools exist. Connected App items in this topic tend to focus on the security policy settings rather than the OAuth flow settings covered in the previous topic, so the framing shifts even though the feature is the same.
If you want to check a specific weak area in this topic without re-reading an entire study guide, the ITExamsTopics question bank lets you work through access management items in isolation. Both the PDF and the practice test are included, and a free demo is available to assess the format before you commit.
The question below focuses on one of the configuration decisions this topic tests most directly.
After four topics that cover protocols, flows, and configuration settings, this one zooms out to product selection. The exam tests whether you can identify the right Salesforce Identity product or license type for a given requirement, including Identity Connect for directory integration and Customer 360 Identity for customer-facing scenarios. At 12%, the weighting is the lightest on the exam, but the items here are easy to get wrong if you have not thought carefully about when each product fits and...
After four topics that cover protocols, flows, and configuration settings, this one zooms out to product selection. The exam tests whether you can identify the right Salesforce Identity product or license type for a given requirement, including Identity Connect for directory integration and Customer 360 Identity for customer-facing scenarios. At 12%, the weighting is the lightest on the exam, but the items here are easy to get wrong if you have not thought carefully about when each product fits and when it does not.
How Salesforce Identity: is tested
Items in this topic are requirement-matching problems. You are given a described implementation need and asked to identify which product or license type satisfies it. Identity Connect items test whether you understand its specific role in a Salesforce Identity architecture: it synchronizes users from Active Directory to Salesforce and can drive SSO, but it is not a general-purpose identity platform. The exam will include scenarios where Identity Connect is a plausible but incorrect choice, usually because the scenario involves a non-AD directory or a customer-facing population rather than an employee one. Customer 360 Identity items test whether you can recognize when a fully developed Customer 360 solution actually requires it versus when existing platform features are sufficient. License type items reward knowing the practical differences between license categories, particularly which license grants access to which identity features. The trap across all three sub-areas is picking the most feature-rich option when the scenario only requires a targeted one.
At 12%, this topic is narrow enough that a small number of missed items can shift your score noticeably. Running through the ITExamsTopics question bank for this topic shows you quickly whether your product and license knowledge is solid or whether one of the three sub-areas needs more attention before exam day.
The question below tests the kind of product-selection reasoning this topic requires.
This topic brings together identity, access, and user experience in the context of Experience Cloud communities. At 18%, it is the second-heaviest topic on the exam. The distinctive challenge here is that the user population is external: partners, customers, and self-registering members rather than internal employees. The authentication options, provisioning models, and license constraints are all different from the internal Salesforce user scenarios covered earlier, and the exam tests those differences directly. β Experience Cloud customization and authentication options Branding...
This topic brings together identity, access, and user experience in the context of Experience Cloud communities. At 18%, it is the second-heaviest topic on the exam. The distinctive challenge here is that the user population is external: partners, customers, and self-registering members rather than internal employees. The authentication options, provisioning models, and license constraints are all different from the internal Salesforce user scenarios covered earlier, and the exam tests those differences directly.
β Experience Cloud customization and authentication options
Branding and user experience customization in Experience Cloud is more than a cosmetic concern. The exam tests whether you know which authentication options are available to community users and how to configure them. Self-registration, identity verification, and password reset flows each have configuration settings that affect the user experience and the security posture of the community. The exam may describe a branding or communication requirement and ask which platform capability delivers it, or describe a security requirement and ask which authentication option enforces it. The distinction between what can be customized through standard configuration and what requires custom development is a practical boundary the exam probes. Candidates who treat all customization options as equivalent tend to pick answers that would require development work when a configuration option exists, or vice versa.
β External identity providers and user/contact models
Supporting external identity providers in communities means connecting social logins, enterprise IdPs, or customer identity platforms to Experience Cloud, and then mapping the authenticated user to the right Salesforce contact or user record. The contact and user model for community users is different from the internal user model, and the exam tests whether you understand that difference. A customer community user is associated with a Contact, which is in turn associated with an Account. The exam may give you a scenario where the wrong model is chosen and ask you to identify the problem, or give you a requirement and ask which model supports it. External IdP scenarios in communities also raise questions about attribute mapping: which fields from the external assertion map to which Salesforce user fields, and what happens when those fields are missing or mismatched.
β External Identity licenses and embedded login
External Identity licenses have specific capabilities and specific limitations, and the exam tests both. Knowing what the license permits is as important as knowing what it does not permit, because the exam frequently presents a scenario where a requirement cannot be met with an External Identity license and asks you to recognize that limitation. Embedded login is a specific feature that allows Salesforce authentication flows to appear within an external web page rather than redirecting the user to a Salesforce-hosted login page. The exam tests when embedded login is the right choice: it fits scenarios where you want to keep the user on an external site while still authenticating them through Salesforce. The wrong-choice scenario is typically one where the external site has constraints that embedded login cannot accommodate, or where a simpler redirect flow would satisfy the requirement without the added configuration complexity.
How Community (Partner and Customer): is tested
At 18%, this topic demands the same level of preparation as the heaviest topic on the exam. Items are scenario-driven and frequently combine two concerns at once: an authentication requirement and a user model requirement, or a customization requirement and a license constraint. The exam rewards candidates who can hold both constraints in mind and find the option that satisfies both. Embedded login items are a reliable differentiator between candidates who have studied this feature specifically and those who have only a general awareness of it. The exam describes a situation and asks whether embedded login is appropriate, which means you need to know both when it fits and when it does not. License limitation items reward knowing the specific boundaries of External Identity licenses, not just that they exist as a lower-cost option. The user and contact model questions reward understanding the structural relationship between community users, contacts, and accounts, because getting that relationship wrong leads to picking an answer that would cause a data model problem in practice.
The ITExamsTopics practice test includes items across all four sub-areas of this topic, covering the full range of community authentication, user model, and license scenarios you will face. Seeing the item style in advance, in both PDF and practice test formats, is the most direct way to verify your coverage before the exam.
The question below presents a community scenario that draws on more than one of this topic's sub-areas.
Ready to Start Practicing?
Access all questions and start your exam preparation journey
Upgrade to Full Salesforce Certified Platform Identity and Access Management Architect (Plat-Arch-203) Exam Questions π