Salesforce Certified Platform Identity and Access Management Architect Practice Test 53
Question 520
An implementation team investigates this scenario: A retailer wants a unified customer profile across ecommerce and Salesforce but already has an enterprise IdP. Which finding would most directly justify a change to the integration architecture?
- Existing systems already perform strong authentication, but customer attributes are fragmented between many records.
- The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration.
- The portal and app authenticate at different providers but must link to an approved CRM contact.
- Marketing assumes that a unified profile permits every application to reuse all customer data for any purpose.
Explanation
Correct Answer
B:Best. The decisive observation is: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. This is why the design response should be: Assess Customer 360 identity needs separately from federation and customer-data unification components.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A financial services architecture board evaluates whether Salesforce identity capabilities fit a mature customer data platform. Its relevant condition is: Existing systems already perform strong authentication, but customer attributes are fragmented between many records. The present case instead turns on: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The direct answer here is: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A customer registers in an Experience Cloud portal and later uses a mobile loyalty app. Its relevant condition is: The portal and app authenticate at different providers but must link to an approved CRM contact. The present case instead turns on: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The direct answer here is: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise wants to centralize customer consent alongside Salesforce Customer 360 use cases. Its relevant condition is: Marketing assumes that a unified profile permits every application to reuse all customer data for any purpose. The present case instead turns on: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The direct answer here is: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration.
Question 521
A solution review asks whether this control is effective: Assess Customer 360 identity needs separately from federation and customer-data unification components. The business setting is: A retailer wants a unified customer profile across ecommerce and Salesforce but already has an enterprise IdP. What should a demonstrable successful outcome be?
- Applications receive only customer attributes permitted for their approved business purpose.
- The solution clearly assigns responsibility for login, matching, consent and profile data.
- The architecture adds only the identity capabilities needed without replacing a successful enterprise IdP.
- Changing contact details does not create inconsistent cross-channel profile linkage.
Explanation
Correct Answer
B:Best. The verification target is: The solution clearly assigns responsibility for login, matching, consent and profile data. It tests whether the chosen approach—Assess Customer 360 identity needs separately from federation and customer-data unification components.—actually resolves the specific finding: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise wants to centralize customer consent alongside Salesforce Customer 360 use cases. Its relevant condition is: Marketing assumes that a unified profile permits every application to reuse all customer data for any purpose. The present case instead turns on: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The direct answer here is: The solution clearly assigns responsibility for login, matching, consent and profile data.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A financial services architecture board evaluates whether Salesforce identity capabilities fit a mature customer data platform. Its relevant condition is: Existing systems already perform strong authentication, but customer attributes are fragmented between many records. The present case instead turns on: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The direct answer here is: The solution clearly assigns responsibility for login, matching, consent and profile data.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A public membership platform has customer records shared between commerce, support and loyalty services. Its relevant condition is: A user can have two email addresses but should retain one governed customer identity association. The present case instead turns on: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The direct answer here is: The solution clearly assigns responsibility for login, matching, consent and profile data.
Question 522
A Salesforce integration initiative faces this situation: A retailer wants a unified customer profile across ecommerce and Salesforce but already has an enterprise IdP. The critical observation is: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. What failure is most likely if it is ignored?
- The company buys a duplicate authentication system while leaving customer matching problems unsolved.
- Email-only identity stitching merges unrelated customers or splits one person's entitlements.
- An SSO login provider is expected to merge duplicate customer records automatically.
- A matching email address alone allows an unrelated person to claim an existing loyalty account.
Explanation
Correct Answer
C:Best. The most direct failure is: An SSO login provider is expected to merge duplicate customer records automatically. It is a consequence of the documented condition: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. A mitigation is: Assess Customer 360 identity needs separately from federation and customer-data unification components.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A financial services architecture board evaluates whether Salesforce identity capabilities fit a mature customer data platform. Its relevant condition is: Existing systems already perform strong authentication, but customer attributes are fragmented between many records. The present case instead turns on: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The direct answer here is: An SSO login provider is expected to merge duplicate customer records automatically.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A public membership platform has customer records shared between commerce, support and loyalty services. Its relevant condition is: A user can have two email addresses but should retain one governed customer identity association. The present case instead turns on: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The direct answer here is: An SSO login provider is expected to merge duplicate customer records automatically.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A customer registers in an Experience Cloud portal and later uses a mobile loyalty app. Its relevant condition is: The portal and app authenticate at different providers but must link to an approved CRM contact. The present case instead turns on: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The direct answer here is: An SSO login provider is expected to merge duplicate customer records automatically.
Question 523
In this fictional project, A telecom provider wants customers to use one login across several branded service portals. The project team has uncovered that Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. Which action is best supported by those facts?
- Separate customer identity resolution from partner authentication, delegated authorization and legal data sharing.
- Assess Customer 360 identity needs separately from federation and customer-data unification components.
- Model purpose, consent, data access and retention distinctly from identity matching and sign-in.
- Define customer authentication and identity-linking requirements independently of profile unification.
Explanation
Correct Answer
D:Best. The most direct action is to define customer authentication and identity-linking requirements independently of profile unification. It is supported by the specific finding that its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. The expected acceptance evidence is: Customers sign in consistently while each portal enforces its own access and data visibility.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An insurance company wants to connect customer identity between service applications and external partners. Its relevant condition is: The diagram has one global customer record but no documented trust or permissions at partner boundaries. The present case instead turns on: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. The direct answer here is: Define customer authentication and identity-linking requirements independently of profile unification.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A retailer wants a unified customer profile across ecommerce and Salesforce but already has an enterprise IdP. Its relevant condition is: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The present case instead turns on: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. The direct answer here is: Define customer authentication and identity-linking requirements independently of profile unification.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise wants to centralize customer consent alongside Salesforce Customer 360 use cases. Its relevant condition is: Marketing assumes that a unified profile permits every application to reuse all customer data for any purpose. The present case instead turns on: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. The direct answer here is: Define customer authentication and identity-linking requirements independently of profile unification.
Question 524
An enterprise review begins with this business situation: A telecom provider wants customers to use one login across several branded service portals. Which technical or process signal best identifies the obstacle?
- Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy.
- Marketing assumes that a unified profile permits every application to reuse all customer data for any purpose.
- The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration.
- A user can have two email addresses but should retain one governed customer identity association.
Explanation
Correct Answer
A:Best. The decisive observation is: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. This is why the design response should be: Define customer authentication and identity-linking requirements independently of profile unification.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise wants to centralize customer consent alongside Salesforce Customer 360 use cases. Its relevant condition is: Marketing assumes that a unified profile permits every application to reuse all customer data for any purpose. The present case instead turns on: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. The direct answer here is: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A retailer wants a unified customer profile across ecommerce and Salesforce but already has an enterprise IdP. Its relevant condition is: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The present case instead turns on: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. The direct answer here is: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A public membership platform has customer records shared between commerce, support and loyalty services. Its relevant condition is: A user can have two email addresses but should retain one governed customer identity association. The present case instead turns on: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. The direct answer here is: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy.
Question 525
The team adopts this approach: Define customer authentication and identity-linking requirements independently of profile unification. The original project scenario is: A telecom provider wants customers to use one login across several branded service portals. Which verification outcome best demonstrates that it worked?
- Customers sign in consistently while each portal enforces its own access and data visibility.
- Both channels associate the verified customer to a single appropriate Salesforce profile.
- Applications receive only customer attributes permitted for their approved business purpose.
- Partners can access permitted customer context without inheriting broad platform privileges.
Explanation
Correct Answer
A:Best. The verification target is: Customers sign in consistently while each portal enforces its own access and data visibility. It tests whether the chosen approach—Define customer authentication and identity-linking requirements independently of profile unification.—actually resolves the specific finding: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A customer registers in an Experience Cloud portal and later uses a mobile loyalty app. Its relevant condition is: The portal and app authenticate at different providers but must link to an approved CRM contact. The present case instead turns on: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. The direct answer here is: Customers sign in consistently while each portal enforces its own access and data visibility.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise wants to centralize customer consent alongside Salesforce Customer 360 use cases. Its relevant condition is: Marketing assumes that a unified profile permits every application to reuse all customer data for any purpose. The present case instead turns on: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. The direct answer here is: Customers sign in consistently while each portal enforces its own access and data visibility.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An insurance company wants to connect customer identity between service applications and external partners. Its relevant condition is: The diagram has one global customer record but no documented trust or permissions at partner boundaries. The present case instead turns on: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. The direct answer here is: Customers sign in consistently while each portal enforces its own access and data visibility.
Question 526
A project manager declines to address this finding: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. The related project is: A telecom provider wants customers to use one login across several branded service portals. Which consequence most directly follows?
- The company buys a duplicate authentication system while leaving customer matching problems unsolved.
- A unified identity record is misused as permission to expose every customer's information.
- An SSO login provider is expected to merge duplicate customer records automatically.
- A single CRM customer identifier is mistaken for an authenticated login credential.
Explanation
Correct Answer
D:Best. The most direct failure is: A single CRM customer identifier is mistaken for an authenticated login credential. It is a consequence of the documented condition: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. A mitigation is: Define customer authentication and identity-linking requirements independently of profile unification.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A financial services architecture board evaluates whether Salesforce identity capabilities fit a mature customer data platform. Its relevant condition is: Existing systems already perform strong authentication, but customer attributes are fragmented between many records. The present case instead turns on: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. The direct answer here is: A single CRM customer identifier is mistaken for an authenticated login credential.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An insurance company wants to connect customer identity between service applications and external partners. Its relevant condition is: The diagram has one global customer record but no documented trust or permissions at partner boundaries. The present case instead turns on: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. The direct answer here is: A single CRM customer identifier is mistaken for an authenticated login credential.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A retailer wants a unified customer profile across ecommerce and Salesforce but already has an enterprise IdP. Its relevant condition is: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The present case instead turns on: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. The direct answer here is: A single CRM customer identifier is mistaken for an authenticated login credential.
Question 527
An architecture board reviews a proposed Salesforce integration. Context: A public membership platform has customer records shared between commerce, support and loyalty services. Finding: A user can have two email addresses but should retain one governed customer identity association. Which decision best resolves the concern?
- Separate customer identity resolution from partner authentication, delegated authorization and legal data sharing.
- Assess gaps in customer identity linking, authorization boundaries and data stewardship before choosing products.
- Evaluate durable customer identifiers and supported identity resolution aligned to authentication policy.
- Assess Customer 360 identity needs separately from federation and customer-data unification components.
Explanation
Correct Answer
C:Best. The most direct action is to evaluate durable customer identifiers and supported identity resolution aligned to authentication policy. It is supported by the specific finding that A user can have two email addresses but should retain one governed customer identity association. The expected acceptance evidence is: Changing contact details does not create inconsistent cross-channel profile linkage.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An insurance company wants to connect customer identity between service applications and external partners. Its relevant condition is: The diagram has one global customer record but no documented trust or permissions at partner boundaries. The present case instead turns on: A user can have two email addresses but should retain one governed customer identity association. The direct answer here is: Evaluate durable customer identifiers and supported identity resolution aligned to authentication policy.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A financial services architecture board evaluates whether Salesforce identity capabilities fit a mature customer data platform. Its relevant condition is: Existing systems already perform strong authentication, but customer attributes are fragmented between many records. The present case instead turns on: A user can have two email addresses but should retain one governed customer identity association. The direct answer here is: Evaluate durable customer identifiers and supported identity resolution aligned to authentication policy.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A retailer wants a unified customer profile across ecommerce and Salesforce but already has an enterprise IdP. Its relevant condition is: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The present case instead turns on: A user can have two email addresses but should retain one governed customer identity association. The direct answer here is: Evaluate durable customer identifiers and supported identity resolution aligned to authentication policy.
Question 528
A design workshop describes this environment: A public membership platform has customer records shared between commerce, support and loyalty services. Which concrete observation should be documented as the most decisive issue?
- A user can have two email addresses but should retain one governed customer identity association.
- The portal and app authenticate at different providers but must link to an approved CRM contact.
- The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration.
- Existing systems already perform strong authentication, but customer attributes are fragmented between many records.
Explanation
Correct Answer
A:Best. The decisive observation is: A user can have two email addresses but should retain one governed customer identity association. This is why the design response should be: Evaluate durable customer identifiers and supported identity resolution aligned to authentication policy.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A customer registers in an Experience Cloud portal and later uses a mobile loyalty app. Its relevant condition is: The portal and app authenticate at different providers but must link to an approved CRM contact. The present case instead turns on: A user can have two email addresses but should retain one governed customer identity association. The direct answer here is: A user can have two email addresses but should retain one governed customer identity association.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A retailer wants a unified customer profile across ecommerce and Salesforce but already has an enterprise IdP. Its relevant condition is: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The present case instead turns on: A user can have two email addresses but should retain one governed customer identity association. The direct answer here is: A user can have two email addresses but should retain one governed customer identity association.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A financial services architecture board evaluates whether Salesforce identity capabilities fit a mature customer data platform. Its relevant condition is: Existing systems already perform strong authentication, but customer attributes are fragmented between many records. The present case instead turns on: A user can have two email addresses but should retain one governed customer identity association. The direct answer here is: A user can have two email addresses but should retain one governed customer identity association.
Question 529
An architect must create an acceptance test after choosing: Evaluate durable customer identifiers and supported identity resolution aligned to authentication policy. For the situation A public membership platform has customer records shared between commerce, support and loyalty services. Which result most directly proves success?
- Applications receive only customer attributes permitted for their approved business purpose.
- The architecture adds only the identity capabilities needed without replacing a successful enterprise IdP.
- Changing contact details does not create inconsistent cross-channel profile linkage.
- Customers sign in consistently while each portal enforces its own access and data visibility.
Explanation
Correct Answer
C:Best. The verification target is: Changing contact details does not create inconsistent cross-channel profile linkage. It tests whether the chosen approach—Evaluate durable customer identifiers and supported identity resolution aligned to authentication policy.—actually resolves the specific finding: A user can have two email addresses but should retain one governed customer identity association.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise wants to centralize customer consent alongside Salesforce Customer 360 use cases. Its relevant condition is: Marketing assumes that a unified profile permits every application to reuse all customer data for any purpose. The present case instead turns on: A user can have two email addresses but should retain one governed customer identity association. The direct answer here is: Changing contact details does not create inconsistent cross-channel profile linkage.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A financial services architecture board evaluates whether Salesforce identity capabilities fit a mature customer data platform. Its relevant condition is: Existing systems already perform strong authentication, but customer attributes are fragmented between many records. The present case instead turns on: A user can have two email addresses but should retain one governed customer identity association. The direct answer here is: Changing contact details does not create inconsistent cross-channel profile linkage.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A telecom provider wants customers to use one login across several branded service portals. Its relevant condition is: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. The present case instead turns on: A user can have two email addresses but should retain one governed customer identity association. The direct answer here is: Changing contact details does not create inconsistent cross-channel profile linkage.
Question 530
An incident scenario concerns this architecture: A public membership platform has customer records shared between commerce, support and loyalty services. The team has discovered: A user can have two email addresses but should retain one governed customer identity association. Which project risk requires explicit mitigation?
- A matching email address alone allows an unrelated person to claim an existing loyalty account.
- Email-only identity stitching merges unrelated customers or splits one person's entitlements.
- A single CRM customer identifier is mistaken for an authenticated login credential.
- The company buys a duplicate authentication system while leaving customer matching problems unsolved.
Explanation
Correct Answer
B:Best. The most direct failure is: Email-only identity stitching merges unrelated customers or splits one person's entitlements. It is a consequence of the documented condition: A user can have two email addresses but should retain one governed customer identity association. A mitigation is: Evaluate durable customer identifiers and supported identity resolution aligned to authentication policy.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A customer registers in an Experience Cloud portal and later uses a mobile loyalty app. Its relevant condition is: The portal and app authenticate at different providers but must link to an approved CRM contact. The present case instead turns on: A user can have two email addresses but should retain one governed customer identity association. The direct answer here is: Email-only identity stitching merges unrelated customers or splits one person's entitlements.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A telecom provider wants customers to use one login across several branded service portals. Its relevant condition is: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. The present case instead turns on: A user can have two email addresses but should retain one governed customer identity association. The direct answer here is: Email-only identity stitching merges unrelated customers or splits one person's entitlements.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A financial services architecture board evaluates whether Salesforce identity capabilities fit a mature customer data platform. Its relevant condition is: Existing systems already perform strong authentication, but customer attributes are fragmented between many records. The present case instead turns on: A user can have two email addresses but should retain one governed customer identity association. The direct answer here is: Email-only identity stitching merges unrelated customers or splits one person's entitlements.