Salesforce Certified Platform Identity and Access Management Architect Practice Test 17
Question 160
Consider the following hypothetical Salesforce initiative: A consulting partner's Salesforce access should end immediately when its contract closes. Which evidence would most strongly explain the current integration weakness?
- Most consultants lack Salesforce users until their first approved SSO session.
- The partner's external IdP controls authentication but Salesforce user records persist after contract end.
- Some temporary workers are scheduled in the future while others have already left the assignment.
- A new email should not create an unrelated Salesforce user or orphan the existing Contact association.
Explanation
Correct Answer
B:Best. The decisive observation is: The partner's external IdP controls authentication but Salesforce user records persist after contract end. This is why the design response should be: Combine federation with lifecycle-driven user deactivation and periodic contact/account entitlement reconciliation.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A small professional network has external consultants who use a federation relationship a few times per year. Its relevant condition is: Most consultants lack Salesforce users until their first approved SSO session. The present case instead turns on: The partner's external IdP controls authentication but Salesforce user records persist after contract end. The direct answer here is: The partner's external IdP controls authentication but Salesforce user records persist after contract end.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A B2E organization imports temporary workers from an external identity directory each week. Its relevant condition is: Some temporary workers are scheduled in the future while others have already left the assignment. The present case instead turns on: The partner's external IdP controls authentication but Salesforce user records persist after contract end. The direct answer here is: The partner's external IdP controls authentication but Salesforce user records persist after contract end.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An ecommerce platform allows a customer to update an email address after account creation. Its relevant condition is: A new email should not create an unrelated Salesforce user or orphan the existing Contact association. The present case instead turns on: The partner's external IdP controls authentication but Salesforce user records persist after contract end. The direct answer here is: The partner's external IdP controls authentication but Salesforce user records persist after contract end.
Question 161
Review this change: Combine federation with lifecycle-driven user deactivation and periodic contact/account entitlement reconciliation. It addresses a project where A consulting partner's Salesforce access should end immediately when its contract closes. Which result should appear in integration acceptance evidence?
- Only currently sponsored workers have Salesforce login access, with future accounts staged safely.
- Expired partner users lose access despite any prior successful login or stale external credential.
- Accounts and entitlements reconcile before start dates and promptly close on termination.
- The returning consumer signs into the same authorized site user after an email change.
Explanation
Correct Answer
B:Best. The verification target is: Expired partner users lose access despite any prior successful login or stale external credential. It tests whether the chosen approach—Combine federation with lifecycle-driven user deactivation and periodic contact/account entitlement reconciliation.—actually resolves the specific finding: The partner's external IdP controls authentication but Salesforce user records persist after contract end.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A B2E organization imports temporary workers from an external identity directory each week. Its relevant condition is: Some temporary workers are scheduled in the future while others have already left the assignment. The present case instead turns on: The partner's external IdP controls authentication but Salesforce user records persist after contract end. The direct answer here is: Expired partner users lose access despite any prior successful login or stale external credential.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A global manufacturer adds 3,000 internal employees to Salesforce through a central directory. Its relevant condition is: People must be present before their first shift and later removed promptly after HR offboarding. The present case instead turns on: The partner's external IdP controls authentication but Salesforce user records persist after contract end. The direct answer here is: Expired partner users lose access despite any prior successful login or stale external credential.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An ecommerce platform allows a customer to update an email address after account creation. Its relevant condition is: A new email should not create an unrelated Salesforce user or orphan the existing Contact association. The present case instead turns on: The partner's external IdP controls authentication but Salesforce user records persist after contract end. The direct answer here is: Expired partner users lose access despite any prior successful login or stale external credential.
Question 162
Suppose the integration design proceeds without correcting this issue: The partner's external IdP controls authentication but Salesforce user records persist after contract end. In the environment A consulting partner's Salesforce access should end immediately when its contract closes. What should the risk register emphasize?
- Bulk directory import inadvertently activates expired workers and dormant identities.
- A missing JIT attribute silently assigns an unintended user profile or causes a login loop.
- Federation alone is mistaken for a full user offboarding mechanism.
- One broad replicated role grants users privileges in an org where they have no business need.
Explanation
Correct Answer
C:Best. The most direct failure is: Federation alone is mistaken for a full user offboarding mechanism. It is a consequence of the documented condition: The partner's external IdP controls authentication but Salesforce user records persist after contract end. A mitigation is: Combine federation with lifecycle-driven user deactivation and periodic contact/account entitlement reconciliation.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A B2E organization imports temporary workers from an external identity directory each week. Its relevant condition is: Some temporary workers are scheduled in the future while others have already left the assignment. The present case instead turns on: The partner's external IdP controls authentication but Salesforce user records persist after contract end. The direct answer here is: Federation alone is mistaken for a full user offboarding mechanism.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A small professional network has external consultants who use a federation relationship a few times per year. Its relevant condition is: Most consultants lack Salesforce users until their first approved SSO session. The present case instead turns on: The partner's external IdP controls authentication but Salesforce user records persist after contract end. The direct answer here is: Federation alone is mistaken for a full user offboarding mechanism.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise must onboard business users across several Salesforce orgs from one source directory. Its relevant condition is: The team proposes logging into each org manually to create the same employees and roles. The present case instead turns on: The partner's external IdP controls authentication but Salesforce user records persist after contract end. The direct answer here is: Federation alone is mistaken for a full user offboarding mechanism.
Question 163
In this fictional project, An enterprise must onboard business users across several Salesforce orgs from one source directory. The project team has uncovered that The team proposes logging into each org manually to create the same employees and roles. Which action is best supported by those facts?
- Provision approved Experience Cloud partner users through the account/contact model with licensed access checks.
- Combine federation with lifecycle-driven user deactivation and periodic contact/account entitlement reconciliation.
- Adopt a governed org-by-org provisioning sync with distinct entitlements and common stable user IDs.
- Use lifecycle state and effective dates rather than assuming every imported record must be active.
Explanation
Correct Answer
C:Best. The most direct action is to adopt a governed org-by-org provisioning sync with distinct entitlements and common stable user IDs. It is supported by the specific finding that the team proposes logging into each org manually to create the same employees and roles. The expected acceptance evidence is: All target orgs receive their authorized accounts while permission assignments remain org-specific.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A regional franchise grants outside partners access to their own order records within an Experience Cloud site. Its relevant condition is: The partner users must have a suitable external-user identity and be associated with the right business account. The present case instead turns on: The team proposes logging into each org manually to create the same employees and roles. The direct answer here is: Adopt a governed org-by-org provisioning sync with distinct entitlements and common stable user IDs.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A consulting partner's Salesforce access should end immediately when its contract closes. Its relevant condition is: The partner's external IdP controls authentication but Salesforce user records persist after contract end. The present case instead turns on: The team proposes logging into each org manually to create the same employees and roles. The direct answer here is: Adopt a governed org-by-org provisioning sync with distinct entitlements and common stable user IDs.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A B2E organization imports temporary workers from an external identity directory each week. Its relevant condition is: Some temporary workers are scheduled in the future while others have already left the assignment. The present case instead turns on: The team proposes logging into each org manually to create the same employees and roles. The direct answer here is: Adopt a governed org-by-org provisioning sync with distinct entitlements and common stable user IDs.
Question 164
An enterprise review begins with this business situation: An enterprise must onboard business users across several Salesforce orgs from one source directory. Which technical or process signal best identifies the obstacle?
- Members are customers linked to contacts rather than employees managed by the HR identity system.
- Some temporary workers are scheduled in the future while others have already left the assignment.
- A new email should not create an unrelated Salesforce user or orphan the existing Contact association.
- The team proposes logging into each org manually to create the same employees and roles.
Explanation
Correct Answer
D:Best. The decisive observation is: The team proposes logging into each org manually to create the same employees and roles. This is why the design response should be: Adopt a governed org-by-org provisioning sync with distinct entitlements and common stable user IDs.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A large consumer loyalty website expects many external member registrations daily. Its relevant condition is: Members are customers linked to contacts rather than employees managed by the HR identity system. The present case instead turns on: The team proposes logging into each org manually to create the same employees and roles. The direct answer here is: The team proposes logging into each org manually to create the same employees and roles.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A B2E organization imports temporary workers from an external identity directory each week. Its relevant condition is: Some temporary workers are scheduled in the future while others have already left the assignment. The present case instead turns on: The team proposes logging into each org manually to create the same employees and roles. The direct answer here is: The team proposes logging into each org manually to create the same employees and roles.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An ecommerce platform allows a customer to update an email address after account creation. Its relevant condition is: A new email should not create an unrelated Salesforce user or orphan the existing Contact association. The present case instead turns on: The team proposes logging into each org manually to create the same employees and roles. The direct answer here is: The team proposes logging into each org manually to create the same employees and roles.
Question 165
The team adopts this approach: Adopt a governed org-by-org provisioning sync with distinct entitlements and common stable user IDs. The original project scenario is: An enterprise must onboard business users across several Salesforce orgs from one source directory. Which verification outcome best demonstrates that it worked?
- An approved first login establishes a scoped Salesforce account without mass manual preparation.
- All target orgs receive their authorized accounts while permission assignments remain org-specific.
- The returning consumer signs into the same authorized site user after an email change.
- Only currently sponsored workers have Salesforce login access, with future accounts staged safely.
Explanation
Correct Answer
B:Best. The verification target is: All target orgs receive their authorized accounts while permission assignments remain org-specific. It tests whether the chosen approach—Adopt a governed org-by-org provisioning sync with distinct entitlements and common stable user IDs.—actually resolves the specific finding: The team proposes logging into each org manually to create the same employees and roles.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A small professional network has external consultants who use a federation relationship a few times per year. Its relevant condition is: Most consultants lack Salesforce users until their first approved SSO session. The present case instead turns on: The team proposes logging into each org manually to create the same employees and roles. The direct answer here is: All target orgs receive their authorized accounts while permission assignments remain org-specific.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An ecommerce platform allows a customer to update an email address after account creation. Its relevant condition is: A new email should not create an unrelated Salesforce user or orphan the existing Contact association. The present case instead turns on: The team proposes logging into each org manually to create the same employees and roles. The direct answer here is: All target orgs receive their authorized accounts while permission assignments remain org-specific.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A B2E organization imports temporary workers from an external identity directory each week. Its relevant condition is: Some temporary workers are scheduled in the future while others have already left the assignment. The present case instead turns on: The team proposes logging into each org manually to create the same employees and roles. The direct answer here is: All target orgs receive their authorized accounts while permission assignments remain org-specific.
Question 166
A project manager declines to address this finding: The team proposes logging into each org manually to create the same employees and roles. The related project is: An enterprise must onboard business users across several Salesforce orgs from one source directory. Which consequence most directly follows?
- One broad replicated role grants users privileges in an org where they have no business need.
- A missing JIT attribute silently assigns an unintended user profile or causes a login loop.
- Only relying on first-login JIT leaves new staff missing access and departing users still active.
- Incorrect contact-to-account linking lets one franchise view another franchise's orders.
Explanation
Correct Answer
A:Best. The most direct failure is: One broad replicated role grants users privileges in an org where they have no business need. It is a consequence of the documented condition: The team proposes logging into each org manually to create the same employees and roles. A mitigation is: Adopt a governed org-by-org provisioning sync with distinct entitlements and common stable user IDs.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A small professional network has external consultants who use a federation relationship a few times per year. Its relevant condition is: Most consultants lack Salesforce users until their first approved SSO session. The present case instead turns on: The team proposes logging into each org manually to create the same employees and roles. The direct answer here is: One broad replicated role grants users privileges in an org where they have no business need.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A global manufacturer adds 3,000 internal employees to Salesforce through a central directory. Its relevant condition is: People must be present before their first shift and later removed promptly after HR offboarding. The present case instead turns on: The team proposes logging into each org manually to create the same employees and roles. The direct answer here is: One broad replicated role grants users privileges in an org where they have no business need.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A regional franchise grants outside partners access to their own order records within an Experience Cloud site. Its relevant condition is: The partner users must have a suitable external-user identity and be associated with the right business account. The present case instead turns on: The team proposes logging into each org manually to create the same employees and roles. The direct answer here is: One broad replicated role grants users privileges in an org where they have no business need.
Question 167
Salesforce and its partners face the following situation: An ecommerce platform allows a customer to update an email address after account creation. The integration review notes: A new email should not create an unrelated Salesforce user or orphan the existing Contact association. Which architectural step should take priority?
- Adopt a governed org-by-org provisioning sync with distinct entitlements and common stable user IDs.
- Use supported B2C registration or automated provisioning mapped to the customer contact/account model.
- Match on a stable external identity key and update the approved customer contact record.
- Select automated B2E preprovisioning and deprovisioning driven by authoritative workforce identity changes.
Explanation
Correct Answer
C:Best. The most direct action is to match on a stable external identity key and update the approved customer contact record. It is supported by the specific finding that A new email should not create an unrelated Salesforce user or orphan the existing Contact association. The expected acceptance evidence is: The returning consumer signs into the same authorized site user after an email change.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise must onboard business users across several Salesforce orgs from one source directory. Its relevant condition is: The team proposes logging into each org manually to create the same employees and roles. The present case instead turns on: A new email should not create an unrelated Salesforce user or orphan the existing Contact association. The direct answer here is: Match on a stable external identity key and update the approved customer contact record.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A large consumer loyalty website expects many external member registrations daily. Its relevant condition is: Members are customers linked to contacts rather than employees managed by the HR identity system. The present case instead turns on: A new email should not create an unrelated Salesforce user or orphan the existing Contact association. The direct answer here is: Match on a stable external identity key and update the approved customer contact record.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A global manufacturer adds 3,000 internal employees to Salesforce through a central directory. Its relevant condition is: People must be present before their first shift and later removed promptly after HR offboarding. The present case instead turns on: A new email should not create an unrelated Salesforce user or orphan the existing Contact association. The direct answer here is: Match on a stable external identity key and update the approved customer contact record.
Question 168
An implementation team investigates this scenario: An ecommerce platform allows a customer to update an email address after account creation. Which finding would most directly justify a change to the integration architecture?
- People must be present before their first shift and later removed promptly after HR offboarding.
- A new email should not create an unrelated Salesforce user or orphan the existing Contact association.
- The team proposes logging into each org manually to create the same employees and roles.
- The partner users must have a suitable external-user identity and be associated with the right business account.
Explanation
Correct Answer
B:Best. The decisive observation is: A new email should not create an unrelated Salesforce user or orphan the existing Contact association. This is why the design response should be: Match on a stable external identity key and update the approved customer contact record.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A global manufacturer adds 3,000 internal employees to Salesforce through a central directory. Its relevant condition is: People must be present before their first shift and later removed promptly after HR offboarding. The present case instead turns on: A new email should not create an unrelated Salesforce user or orphan the existing Contact association. The direct answer here is: A new email should not create an unrelated Salesforce user or orphan the existing Contact association.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise must onboard business users across several Salesforce orgs from one source directory. Its relevant condition is: The team proposes logging into each org manually to create the same employees and roles. The present case instead turns on: A new email should not create an unrelated Salesforce user or orphan the existing Contact association. The direct answer here is: A new email should not create an unrelated Salesforce user or orphan the existing Contact association.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A regional franchise grants outside partners access to their own order records within an Experience Cloud site. Its relevant condition is: The partner users must have a suitable external-user identity and be associated with the right business account. The present case instead turns on: A new email should not create an unrelated Salesforce user or orphan the existing Contact association. The direct answer here is: A new email should not create an unrelated Salesforce user or orphan the existing Contact association.
Question 169
A solution review asks whether this control is effective: Match on a stable external identity key and update the approved customer contact record. The business setting is: An ecommerce platform allows a customer to update an email address after account creation. What should a demonstrable successful outcome be?
- Expired partner users lose access despite any prior successful login or stale external credential.
- An approved first login establishes a scoped Salesforce account without mass manual preparation.
- Only currently sponsored workers have Salesforce login access, with future accounts staged safely.
- The returning consumer signs into the same authorized site user after an email change.
Explanation
Correct Answer
D:Best. The verification target is: The returning consumer signs into the same authorized site user after an email change. It tests whether the chosen approach—Match on a stable external identity key and update the approved customer contact record.—actually resolves the specific finding: A new email should not create an unrelated Salesforce user or orphan the existing Contact association.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A consulting partner's Salesforce access should end immediately when its contract closes. Its relevant condition is: The partner's external IdP controls authentication but Salesforce user records persist after contract end. The present case instead turns on: A new email should not create an unrelated Salesforce user or orphan the existing Contact association. The direct answer here is: The returning consumer signs into the same authorized site user after an email change.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A small professional network has external consultants who use a federation relationship a few times per year. Its relevant condition is: Most consultants lack Salesforce users until their first approved SSO session. The present case instead turns on: A new email should not create an unrelated Salesforce user or orphan the existing Contact association. The direct answer here is: The returning consumer signs into the same authorized site user after an email change.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A B2E organization imports temporary workers from an external identity directory each week. Its relevant condition is: Some temporary workers are scheduled in the future while others have already left the assignment. The present case instead turns on: A new email should not create an unrelated Salesforce user or orphan the existing Contact association. The direct answer here is: The returning consumer signs into the same authorized site user after an email change.
Question 170
A Salesforce integration initiative faces this situation: An ecommerce platform allows a customer to update an email address after account creation. The critical observation is: A new email should not create an unrelated Salesforce user or orphan the existing Contact association. What failure is most likely if it is ignored?
- A missing JIT attribute silently assigns an unintended user profile or causes a login loop.
- Email-only matching fragments a customer's history into duplicate users and contacts.
- Treating consumer registrations as full internal user licenses creates an expensive inappropriate identity model.
- Incorrect contact-to-account linking lets one franchise view another franchise's orders.
Explanation
Correct Answer
B:Best. The most direct failure is: Email-only matching fragments a customer's history into duplicate users and contacts. It is a consequence of the documented condition: A new email should not create an unrelated Salesforce user or orphan the existing Contact association. A mitigation is: Match on a stable external identity key and update the approved customer contact record.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A small professional network has external consultants who use a federation relationship a few times per year. Its relevant condition is: Most consultants lack Salesforce users until their first approved SSO session. The present case instead turns on: A new email should not create an unrelated Salesforce user or orphan the existing Contact association. The direct answer here is: Email-only matching fragments a customer's history into duplicate users and contacts.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A large consumer loyalty website expects many external member registrations daily. Its relevant condition is: Members are customers linked to contacts rather than employees managed by the HR identity system. The present case instead turns on: A new email should not create an unrelated Salesforce user or orphan the existing Contact association. The direct answer here is: Email-only matching fragments a customer's history into duplicate users and contacts.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A regional franchise grants outside partners access to their own order records within an Experience Cloud site. Its relevant condition is: The partner users must have a suitable external-user identity and be associated with the right business account. The present case instead turns on: A new email should not create an unrelated Salesforce user or orphan the existing Contact association. The direct answer here is: Email-only matching fragments a customer's history into duplicate users and contacts.