Salesforce Certified Platform Identity and Access Management Architect Practice Test 61
Question 600
A Salesforce integration initiative faces this situation: A B2B supplier portal must let users start on a specific purchase-order detail page. The critical observation is: After SSO, users always land on a generic homepage rather than the requested permitted record. What failure is most likely if it is ignored?
- Locale selection accidentally grants access to confidential regional records rather than changing presentation.
- A branded design breaks basic accessibility and traps users in repeated authentication attempts.
- A confusing redirect loop causes users to abandon registration or bypass the intended provider.
- An unvalidated return URL redirects an authenticated user to an attacker-controlled site.
Explanation
Correct Answer
D:Best. The most direct failure is: An unvalidated return URL redirects an authenticated user to an attacker-controlled site. It is a consequence of the documented condition: After SSO, users always land on a generic homepage rather than the requested permitted record. A mitigation is: Use secure routing and approved start or return URLs while validating authorization on the target page.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A manufacturer runs an Experience Cloud partner portal in multiple languages. Its relevant condition is: Partners can authenticate but the post-login page uses a single language and hides regional support content. The present case instead turns on: After SSO, users always land on a generic homepage rather than the requested permitted record. The direct answer here is: An unvalidated return URL redirects an authenticated user to an attacker-controlled site.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A public service portal needs a simple accessibility-friendly login and password recovery process. Its relevant condition is: A bespoke theme removes labels and clear feedback from the authentication interface. The present case instead turns on: After SSO, users always land on a generic homepage rather than the requested permitted record. The direct answer here is: An unvalidated return URL redirects an authenticated user to an attacker-controlled site.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A nonprofit customer portal offers both passwordless and federated sign-in choices. Its relevant condition is: The user interface does not distinguish login methods and repeatedly redirects customers between providers. The present case instead turns on: After SSO, users always land on a generic homepage rather than the requested permitted record. The direct answer here is: An unvalidated return URL redirects an authenticated user to an attacker-controlled site.
Question 601
An architecture board reviews a proposed Salesforce integration. Context: A public service portal needs a simple accessibility-friendly login and password recovery process. Finding: A bespoke theme removes labels and clear feedback from the authentication interface. Which decision best resolves the concern?
- Configure approved Experience Cloud branding, login components and appropriate navigation without weakening identity checks.
- Use supported accessible Experience Cloud login components and understandable recovery status messages.
- Customize supported site localization and user experience based on properly scoped audience attributes.
- Separate public content visibility from authenticated case pages and apply record authorization.
Explanation
Correct Answer
B:Best. The most direct action is to use supported accessible Experience Cloud login components and understandable recovery status messages. It is supported by the specific finding that A bespoke theme removes labels and clear feedback from the authentication interface. The expected acceptance evidence is: Keyboard and screen-reader users can finish authentication and account recovery without confusing states.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A retailer wants its Experience Cloud customers to see a branded sign-in page and self-service order history. Its relevant condition is: The standard login page lacks company branding and does not explain the site's supported authentication choices. The present case instead turns on: A bespoke theme removes labels and clear feedback from the authentication interface. The direct answer here is: Use supported accessible Experience Cloud login components and understandable recovery status messages.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A manufacturer runs an Experience Cloud partner portal in multiple languages. Its relevant condition is: Partners can authenticate but the post-login page uses a single language and hides regional support content. The present case instead turns on: A bespoke theme removes labels and clear feedback from the authentication interface. The direct answer here is: Use supported accessible Experience Cloud login components and understandable recovery status messages.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A public customer support site wants anonymous FAQ access and authenticated case history. Its relevant condition is: The new theme uses the same page permissions for guests and signed-in users. The present case instead turns on: A bespoke theme removes labels and clear feedback from the authentication interface. The direct answer here is: Use supported accessible Experience Cloud login components and understandable recovery status messages.
Question 602
A design workshop describes this environment: A public service portal needs a simple accessibility-friendly login and password recovery process. Which concrete observation should be documented as the most decisive issue?
- A bespoke theme removes labels and clear feedback from the authentication interface.
- The user interface does not distinguish login methods and repeatedly redirects customers between providers.
- Partners can authenticate but the post-login page uses a single language and hides regional support content.
- The developer proposes replacing all authentication with a custom agreement screen and checkbox.
Explanation
Correct Answer
A:Best. The decisive observation is: A bespoke theme removes labels and clear feedback from the authentication interface. This is why the design response should be: Use supported accessible Experience Cloud login components and understandable recovery status messages.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A nonprofit customer portal offers both passwordless and federated sign-in choices. Its relevant condition is: The user interface does not distinguish login methods and repeatedly redirects customers between providers. The present case instead turns on: A bespoke theme removes labels and clear feedback from the authentication interface. The direct answer here is: A bespoke theme removes labels and clear feedback from the authentication interface.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A manufacturer runs an Experience Cloud partner portal in multiple languages. Its relevant condition is: Partners can authenticate but the post-login page uses a single language and hides regional support content. The present case instead turns on: A bespoke theme removes labels and clear feedback from the authentication interface. The direct answer here is: A bespoke theme removes labels and clear feedback from the authentication interface.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An insurer wants additional terms acceptance before members use sensitive claim features. Its relevant condition is: The developer proposes replacing all authentication with a custom agreement screen and checkbox. The present case instead turns on: A bespoke theme removes labels and clear feedback from the authentication interface. The direct answer here is: A bespoke theme removes labels and clear feedback from the authentication interface.
Question 603
An architect must create an acceptance test after choosing: Use supported accessible Experience Cloud login components and understandable recovery status messages. For the situation A public service portal needs a simple accessibility-friendly login and password recovery process. Which result most directly proves success?
- Students can register with required fields, and unnecessary personal data is not collected.
- Keyboard and screen-reader users can finish authentication and account recovery without confusing states.
- Users return to the intended purchase order only when their external account can access it.
- Customers recognize the company and reach their permitted orders through the intended sign-in path.
Explanation
Correct Answer
B:Best. The verification target is: Keyboard and screen-reader users can finish authentication and account recovery without confusing states. It tests whether the chosen approach—Use supported accessible Experience Cloud login components and understandable recovery status messages.—actually resolves the specific finding: A bespoke theme removes labels and clear feedback from the authentication interface.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An education provider wants a registration page that collects only essential student contact fields. Its relevant condition is: The first proposed experience includes social security numbers and unrelated employment details for every registration. The present case instead turns on: A bespoke theme removes labels and clear feedback from the authentication interface. The direct answer here is: Keyboard and screen-reader users can finish authentication and account recovery without confusing states.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A B2B supplier portal must let users start on a specific purchase-order detail page. Its relevant condition is: After SSO, users always land on a generic homepage rather than the requested permitted record. The present case instead turns on: A bespoke theme removes labels and clear feedback from the authentication interface. The direct answer here is: Keyboard and screen-reader users can finish authentication and account recovery without confusing states.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A retailer wants its Experience Cloud customers to see a branded sign-in page and self-service order history. Its relevant condition is: The standard login page lacks company branding and does not explain the site's supported authentication choices. The present case instead turns on: A bespoke theme removes labels and clear feedback from the authentication interface. The direct answer here is: Keyboard and screen-reader users can finish authentication and account recovery without confusing states.
Question 604
An incident scenario concerns this architecture: A public service portal needs a simple accessibility-friendly login and password recovery process. The team has discovered: A bespoke theme removes labels and clear feedback from the authentication interface. Which project risk requires explicit mitigation?
- Locale selection accidentally grants access to confidential regional records rather than changing presentation.
- An unvalidated return URL redirects an authenticated user to an attacker-controlled site.
- A guest-access setting leaks individual customers' support case histories.
- A branded design breaks basic accessibility and traps users in repeated authentication attempts.
Explanation
Correct Answer
D:Best. The most direct failure is: A branded design breaks basic accessibility and traps users in repeated authentication attempts. It is a consequence of the documented condition: A bespoke theme removes labels and clear feedback from the authentication interface. A mitigation is: Use supported accessible Experience Cloud login components and understandable recovery status messages.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A manufacturer runs an Experience Cloud partner portal in multiple languages. Its relevant condition is: Partners can authenticate but the post-login page uses a single language and hides regional support content. The present case instead turns on: A bespoke theme removes labels and clear feedback from the authentication interface. The direct answer here is: A branded design breaks basic accessibility and traps users in repeated authentication attempts.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A B2B supplier portal must let users start on a specific purchase-order detail page. Its relevant condition is: After SSO, users always land on a generic homepage rather than the requested permitted record. The present case instead turns on: A bespoke theme removes labels and clear feedback from the authentication interface. The direct answer here is: A branded design breaks basic accessibility and traps users in repeated authentication attempts.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A public customer support site wants anonymous FAQ access and authenticated case history. Its relevant condition is: The new theme uses the same page permissions for guests and signed-in users. The present case instead turns on: A bespoke theme removes labels and clear feedback from the authentication interface. The direct answer here is: A branded design breaks basic accessibility and traps users in repeated authentication attempts.
Question 605
In this fictional project, A public customer support site wants anonymous FAQ access and authenticated case history. The project team has uncovered that The new theme uses the same page permissions for guests and signed-in users. Which action is best supported by those facts?
- Keep the terms acknowledgement in a supported login flow or site experience after proper authentication.
- Configure approved Experience Cloud branding, login components and appropriate navigation without weakening identity checks.
- Design a clear supported login experience with an appropriate provider selection and consistent return URL.
- Separate public content visibility from authenticated case pages and apply record authorization.
Explanation
Correct Answer
D:Best. The most direct action is to separate public content visibility from authenticated case pages and apply record authorization. It is supported by the specific finding that the new theme uses the same page permissions for guests and signed-in users. The expected acceptance evidence is: Guests can read general help while personal case details remain restricted to permitted users.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An insurer wants additional terms acceptance before members use sensitive claim features. Its relevant condition is: The developer proposes replacing all authentication with a custom agreement screen and checkbox. The present case instead turns on: The new theme uses the same page permissions for guests and signed-in users. The direct answer here is: Separate public content visibility from authenticated case pages and apply record authorization.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A retailer wants its Experience Cloud customers to see a branded sign-in page and self-service order history. Its relevant condition is: The standard login page lacks company branding and does not explain the site's supported authentication choices. The present case instead turns on: The new theme uses the same page permissions for guests and signed-in users. The direct answer here is: Separate public content visibility from authenticated case pages and apply record authorization.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A nonprofit customer portal offers both passwordless and federated sign-in choices. Its relevant condition is: The user interface does not distinguish login methods and repeatedly redirects customers between providers. The present case instead turns on: The new theme uses the same page permissions for guests and signed-in users. The direct answer here is: Separate public content visibility from authenticated case pages and apply record authorization.
Question 606
An enterprise review begins with this business situation: A public customer support site wants anonymous FAQ access and authenticated case history. Which technical or process signal best identifies the obstacle?
- The user interface does not distinguish login methods and repeatedly redirects customers between providers.
- Partners can authenticate but the post-login page uses a single language and hides regional support content.
- The first proposed experience includes social security numbers and unrelated employment details for every registration.
- The new theme uses the same page permissions for guests and signed-in users.
Explanation
Correct Answer
D:Best. The decisive observation is: The new theme uses the same page permissions for guests and signed-in users. This is why the design response should be: Separate public content visibility from authenticated case pages and apply record authorization.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A nonprofit customer portal offers both passwordless and federated sign-in choices. Its relevant condition is: The user interface does not distinguish login methods and repeatedly redirects customers between providers. The present case instead turns on: The new theme uses the same page permissions for guests and signed-in users. The direct answer here is: The new theme uses the same page permissions for guests and signed-in users.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A manufacturer runs an Experience Cloud partner portal in multiple languages. Its relevant condition is: Partners can authenticate but the post-login page uses a single language and hides regional support content. The present case instead turns on: The new theme uses the same page permissions for guests and signed-in users. The direct answer here is: The new theme uses the same page permissions for guests and signed-in users.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An education provider wants a registration page that collects only essential student contact fields. Its relevant condition is: The first proposed experience includes social security numbers and unrelated employment details for every registration. The present case instead turns on: The new theme uses the same page permissions for guests and signed-in users. The direct answer here is: The new theme uses the same page permissions for guests and signed-in users.
Question 607
The team adopts this approach: Separate public content visibility from authenticated case pages and apply record authorization. The original project scenario is: A public customer support site wants anonymous FAQ access and authenticated case history. Which verification outcome best demonstrates that it worked?
- Users return to the intended purchase order only when their external account can access it.
- Keyboard and screen-reader users can finish authentication and account recovery without confusing states.
- Guests can read general help while personal case details remain restricted to permitted users.
- Customers recognize the company and reach their permitted orders through the intended sign-in path.
Explanation
Correct Answer
C:Best. The verification target is: Guests can read general help while personal case details remain restricted to permitted users. It tests whether the chosen approach—Separate public content visibility from authenticated case pages and apply record authorization.—actually resolves the specific finding: The new theme uses the same page permissions for guests and signed-in users.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A B2B supplier portal must let users start on a specific purchase-order detail page. Its relevant condition is: After SSO, users always land on a generic homepage rather than the requested permitted record. The present case instead turns on: The new theme uses the same page permissions for guests and signed-in users. The direct answer here is: Guests can read general help while personal case details remain restricted to permitted users.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A public service portal needs a simple accessibility-friendly login and password recovery process. Its relevant condition is: A bespoke theme removes labels and clear feedback from the authentication interface. The present case instead turns on: The new theme uses the same page permissions for guests and signed-in users. The direct answer here is: Guests can read general help while personal case details remain restricted to permitted users.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A retailer wants its Experience Cloud customers to see a branded sign-in page and self-service order history. Its relevant condition is: The standard login page lacks company branding and does not explain the site's supported authentication choices. The present case instead turns on: The new theme uses the same page permissions for guests and signed-in users. The direct answer here is: Guests can read general help while personal case details remain restricted to permitted users.
Question 608
A project manager declines to address this finding: The new theme uses the same page permissions for guests and signed-in users. The related project is: A public customer support site wants anonymous FAQ access and authenticated case history. Which consequence most directly follows?
- An improvised custom login form captures passwords outside the supported identity provider flow.
- A guest-access setting leaks individual customers' support case histories.
- A convenient generic form creates a long-lived store of sensitive information without purpose.
- A branded design breaks basic accessibility and traps users in repeated authentication attempts.
Explanation
Correct Answer
B:Best. The most direct failure is: A guest-access setting leaks individual customers' support case histories. It is a consequence of the documented condition: The new theme uses the same page permissions for guests and signed-in users. A mitigation is: Separate public content visibility from authenticated case pages and apply record authorization.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A retailer wants its Experience Cloud customers to see a branded sign-in page and self-service order history. Its relevant condition is: The standard login page lacks company branding and does not explain the site's supported authentication choices. The present case instead turns on: The new theme uses the same page permissions for guests and signed-in users. The direct answer here is: A guest-access setting leaks individual customers' support case histories.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An education provider wants a registration page that collects only essential student contact fields. Its relevant condition is: The first proposed experience includes social security numbers and unrelated employment details for every registration. The present case instead turns on: The new theme uses the same page permissions for guests and signed-in users. The direct answer here is: A guest-access setting leaks individual customers' support case histories.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A public service portal needs a simple accessibility-friendly login and password recovery process. Its relevant condition is: A bespoke theme removes labels and clear feedback from the authentication interface. The present case instead turns on: The new theme uses the same page permissions for guests and signed-in users. The direct answer here is: A guest-access setting leaks individual customers' support case histories.
Question 609
An architecture board reviews a proposed Salesforce integration. Context: A regional distributor wants partners to authenticate through their employer's corporate SAML IdP. Finding: Each partner user must be associated with a Contact and a permitted Salesforce partner account. Which decision best resolves the concern?
- Use a stable verified federation identifier and controlled identity-to-Contact association.
- Use an approved account-linking process with proof of identity and stable mapping between providers.
- Implement supported provider discovery and country-specific federation settings with consistent validation.
- Configure external SAML SSO and verify contact-account, federation ID, license and sharing mappings.
Explanation
Correct Answer
D:Best. The most direct action is to configure external SAML SSO and verify contact-account, federation ID, license and sharing mappings. It is supported by the specific finding that Each partner user must be associated with a Contact and a permitted Salesforce partner account. The expected acceptance evidence is: The partner enters via its IdP and sees only records tied to its authorized reseller account.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A government agency allows its constituent services to federate from a trusted national IdP. Its relevant condition is: The IdP issues a stable subject claim, but the site currently keys users by mutable display names. The present case instead turns on: Each partner user must be associated with a Contact and a permitted Salesforce partner account. The direct answer here is: Configure external SAML SSO and verify contact-account, federation ID, license and sharing mappings.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A customer already has an Experience Cloud user and signs in through a newly added OIDC provider. Its relevant condition is: The new provider returns a different subject value but the person must retain the original account. The present case instead turns on: Each partner user must be associated with a Contact and a permitted Salesforce partner account. The direct answer here is: Configure external SAML SSO and verify contact-account, federation ID, license and sharing mappings.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A B2C portal supports customers from several countries through different approved IdPs. Its relevant condition is: The configuration sends all users to one provider and assumes each national identity source has the same format. The present case instead turns on: Each partner user must be associated with a Contact and a permitted Salesforce partner account. The direct answer here is: Configure external SAML SSO and verify contact-account, federation ID, license and sharing mappings.
Question 610
A design workshop describes this environment: A regional distributor wants partners to authenticate through their employer's corporate SAML IdP. Which concrete observation should be documented as the most decisive issue?
- The existing site lacks a safe registration handler to match first-time identity claims to Contacts.
- The SAML JIT attributes omit required Contact or Account information for an external user.
- The IdP issues a stable subject claim, but the site currently keys users by mutable display names.
- Each partner user must be associated with a Contact and a permitted Salesforce partner account.
Explanation
Correct Answer
D:Best. The decisive observation is: Each partner user must be associated with a Contact and a permitted Salesforce partner account. This is why the design response should be: Configure external SAML SSO and verify contact-account, federation ID, license and sharing mappings.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An online retailer lets customers sign in using a supported OpenID Connect social provider. Its relevant condition is: The existing site lacks a safe registration handler to match first-time identity claims to Contacts. The present case instead turns on: Each partner user must be associated with a Contact and a permitted Salesforce partner account. The direct answer here is: Each partner user must be associated with a Contact and a permitted Salesforce partner account.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A supplier partner SAML login validates the signature but Salesforce rejects user creation. Its relevant condition is: The SAML JIT attributes omit required Contact or Account information for an external user. The present case instead turns on: Each partner user must be associated with a Contact and a permitted Salesforce partner account. The direct answer here is: Each partner user must be associated with a Contact and a permitted Salesforce partner account.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A government agency allows its constituent services to federate from a trusted national IdP. Its relevant condition is: The IdP issues a stable subject claim, but the site currently keys users by mutable display names. The present case instead turns on: Each partner user must be associated with a Contact and a permitted Salesforce partner account. The direct answer here is: Each partner user must be associated with a Contact and a permitted Salesforce partner account.