Authentic Salesforce Certification Exam Identity-and-Access-Management-Architect Questions Answers

Just-in-Time provisioning is designed for exactly this onboarding pattern: a user authenticates through an external identity provider, and Salesforce creates the user automatically on first successful login. That avoids preloading every external user into Salesforce before they ever visit the site. Middleware and custom web services can do similar work, but JIT is the native, lower-complexity mechanism built into Salesforce federation. Login flows by themselves do not create the user record during the authentication handshake. The architectural value of JIT is that it keeps the source of identity external while letting Salesforce create and update the user only when the person actually needs access. It is efficient, standard, and commonly used with Experience Cloud. This is why option B is the best answer in Salesforce terms.

When an organization operates many brands, duplicating communities or orgs just to achieve branded login becomes expensive to build and maintain. Salesforce’s scalable answer is to use the Experience ID so the login journey can render the correct branding dynamically for each sub-brand. This preserves a centralized identity service while allowing multiple brand experiences across the same platform. Audiences are useful for content targeting after authentication, but they are not the core mechanism for routing a multi-brand login experience. The architecture principle is to separate identity infrastructure from visual brand presentation. Experience ID lets the organization keep one identity backbone and many branded entry experiences, which is exactly the type of scalability the requirement calls for. This is why option B is the best answer in Salesforce terms.

If Salesforce is brokering identity from an enterprise SSO platform to downstream applications, then in its relationship with the enterprise SSO system Salesforce is acting as a service provider. It is consuming authentication from the enterprise identity source and then using that result to participate in further federation to third-party apps. That distinction matters because the same platform can be an SP upstream and an IdP downstream in the same overall architecture. Resource server and client-application labels do not describe the identity role Salesforce is playing in that specific trust relationship. The key point is directional trust: Salesforce receives the authentication from the enterprise SSO provider, so it is the service provider in that connection. This is why option A is the best answer in Salesforce terms.