Salesforce Certified Platform Identity and Access Management Architect Practice Test 16
Question 150
A Salesforce integration initiative faces this situation: A global manufacturer adds 3,000 internal employees to Salesforce through a central directory. The critical observation is: People must be present before their first shift and later removed promptly after HR offboarding. What failure is most likely if it is ignored?
- Incorrect contact-to-account linking lets one franchise view another franchise's orders.
- One broad replicated role grants users privileges in an org where they have no business need.
- Only relying on first-login JIT leaves new staff missing access and departing users still active.
- Bulk directory import inadvertently activates expired workers and dormant identities.
Explanation
Correct Answer
C:Best. The most direct failure is: Only relying on first-login JIT leaves new staff missing access and departing users still active. It is a consequence of the documented condition: People must be present before their first shift and later removed promptly after HR offboarding. A mitigation is: Select automated B2E preprovisioning and deprovisioning driven by authoritative workforce identity changes.
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: People must be present before their first shift and later removed promptly after HR offboarding. The direct answer here is: Only relying on first-login JIT leaves new staff missing access and departing users still active.
B: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: People must be present before their first shift and later removed promptly after HR offboarding. The direct answer here is: Only relying on first-login JIT leaves new staff missing access and departing users still active.
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: People must be present before their first shift and later removed promptly after HR offboarding. The direct answer here is: Only relying on first-login JIT leaves new staff missing access and departing users still active.
Question 151
An integration architect receives this requirement: A small professional network has external consultants who use a federation relationship a few times per year. A technical discovery also finds: Most consultants lack Salesforce users until their first approved SSO session. Which response most directly addresses the present constraint?
- Select automated B2E preprovisioning and deprovisioning driven by authoritative workforce identity changes.
- Adopt a governed org-by-org provisioning sync with distinct entitlements and common stable user IDs.
- Provision approved Experience Cloud partner users through the account/contact model with licensed access checks.
- Consider controlled SAML JIT creation with required attributes and stable federation identifiers.
Explanation
Correct Answer
D:Best. The most direct action is to consider controlled SAML JIT creation with required attributes and stable federation identifiers. It is supported by the specific finding that Most consultants lack Salesforce users until their first approved SSO session. The expected acceptance evidence is: An approved first login establishes a scoped Salesforce account without mass manual preparation.
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: Most consultants lack Salesforce users until their first approved SSO session. The direct answer here is: Consider controlled SAML JIT creation with required attributes and stable federation identifiers.
B: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: Most consultants lack Salesforce users until their first approved SSO session. The direct answer here is: Consider controlled SAML JIT creation with required attributes and stable federation identifiers.
C: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: Most consultants lack Salesforce users until their first approved SSO session. The direct answer here is: Consider controlled SAML JIT creation with required attributes and stable federation identifiers.
Question 152
Consider the following hypothetical Salesforce initiative: A small professional network has external consultants who use a federation relationship a few times per year. Which evidence would most strongly explain the current integration weakness?
- Most consultants lack Salesforce users until their first approved SSO session.
- The team proposes logging into each org manually to create the same employees and roles.
- People must be present before their first shift and later removed promptly after HR offboarding.
- Members are customers linked to contacts rather than employees managed by the HR identity system.
Explanation
Correct Answer
A:Best. The decisive observation is: Most consultants lack Salesforce users until their first approved SSO session. This is why the design response should be: Consider controlled SAML JIT creation with required attributes and stable federation identifiers.
Incorrect Answers
B: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: Most consultants lack Salesforce users until their first approved SSO session. The direct answer here is: Most consultants lack Salesforce users until their first approved SSO session.
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: Most consultants lack Salesforce users until their first approved SSO session. The direct answer here is: Most consultants lack Salesforce users until their first approved SSO session.
D: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: Most consultants lack Salesforce users until their first approved SSO session. The direct answer here is: Most consultants lack Salesforce users until their first approved SSO session.
Question 153
Review this change: Consider controlled SAML JIT creation with required attributes and stable federation identifiers. It addresses a project where A small professional network has external consultants who use a federation relationship a few times per year. Which result should appear in integration acceptance evidence?
- An approved first login establishes a scoped Salesforce account without mass manual preparation.
- Each verified customer is linked to one approved external user and customer identity record.
- 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
A:Best. The verification target is: An approved first login establishes a scoped Salesforce account without mass manual preparation. It tests whether the chosen approach—Consider controlled SAML JIT creation with required attributes and stable federation identifiers.—actually resolves the specific finding: Most consultants lack Salesforce users until their first approved SSO session.
Incorrect Answers
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: Most consultants lack Salesforce users until their first approved SSO session. The direct answer here is: An approved first login establishes a scoped Salesforce account without mass manual preparation.
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: Most consultants lack Salesforce users until their first approved SSO session. The direct answer here is: An approved first login establishes a scoped Salesforce account without mass manual preparation.
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: Most consultants lack Salesforce users until their first approved SSO session. The direct answer here is: An approved first login establishes a scoped Salesforce account without mass manual preparation.
Question 154
Suppose the integration design proceeds without correcting this issue: Most consultants lack Salesforce users until their first approved SSO session. In the environment A small professional network has external consultants who use a federation relationship a few times per year. What should the risk register emphasize?
- Treating consumer registrations as full internal user licenses creates an expensive inappropriate identity model.
- 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.
- 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: A missing JIT attribute silently assigns an unintended user profile or causes a login loop. It is a consequence of the documented condition: Most consultants lack Salesforce users until their first approved SSO session. A mitigation is: Consider controlled SAML JIT creation with required attributes and stable federation identifiers.
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: Most consultants lack Salesforce users until their first approved SSO session. The direct answer here is: A missing JIT attribute silently assigns an unintended user profile or causes a login loop.
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: Most consultants lack Salesforce users until their first approved SSO session. The direct answer here is: A missing JIT attribute silently assigns an unintended user profile or causes a login loop.
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: Most consultants lack Salesforce users until their first approved SSO session. The direct answer here is: A missing JIT attribute silently assigns an unintended user profile or causes a login loop.
Question 155
Salesforce and its partners face the following situation: A large consumer loyalty website expects many external member registrations daily. The integration review notes: Members are customers linked to contacts rather than employees managed by the HR identity system. Which architectural step should take priority?
- Consider controlled SAML JIT creation with required attributes and stable federation identifiers.
- Use supported B2C registration or automated provisioning mapped to the customer contact/account model.
- Combine federation with lifecycle-driven user deactivation and periodic contact/account entitlement reconciliation.
- Provision approved Experience Cloud partner users through the account/contact model with licensed access checks.
Explanation
Correct Answer
B:Best. The most direct action is to use supported B2C registration or automated provisioning mapped to the customer contact/account model. It is supported by the specific finding that Members are customers linked to contacts rather than employees managed by the HR identity system. The expected acceptance evidence is: Each verified customer is linked to one approved external user and customer identity 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: Members are customers linked to contacts rather than employees managed by the HR identity system. The direct answer here is: Use supported B2C registration or automated provisioning mapped to the customer contact/account model.
C: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: Members are customers linked to contacts rather than employees managed by the HR identity system. The direct answer here is: Use supported B2C registration or automated provisioning mapped to the customer contact/account model.
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: Members are customers linked to contacts rather than employees managed by the HR identity system. The direct answer here is: Use supported B2C registration or automated provisioning mapped to the customer contact/account model.
Question 156
An implementation team investigates this scenario: A large consumer loyalty website expects many external member registrations daily. Which finding would most directly justify a change to the integration architecture?
- The team proposes logging into each org manually to create the same employees and roles.
- A new email should not create an unrelated Salesforce user or orphan the existing Contact association.
- Most consultants lack Salesforce users until their first approved SSO session.
- Members are customers linked to contacts rather than employees managed by the HR identity system.
Explanation
Correct Answer
D:Best. The decisive observation is: Members are customers linked to contacts rather than employees managed by the HR identity system. This is why the design response should be: Use supported B2C registration or automated provisioning mapped to the customer contact/account model.
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: Members are customers linked to contacts rather than employees managed by the HR identity system. The direct answer here is: Members are customers linked to contacts rather than employees managed by the HR identity system.
B: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: Members are customers linked to contacts rather than employees managed by the HR identity system. The direct answer here is: Members are customers linked to contacts rather than employees managed by the HR identity system.
C: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: Members are customers linked to contacts rather than employees managed by the HR identity system. The direct answer here is: Members are customers linked to contacts rather than employees managed by the HR identity system.
Question 157
A solution review asks whether this control is effective: Use supported B2C registration or automated provisioning mapped to the customer contact/account model. The business setting is: A large consumer loyalty website expects many external member registrations daily. What should a demonstrable successful outcome be?
- A partner accesses only their account's permitted orders after first SSO or registration.
- Each verified customer is linked to one approved external user and customer identity record.
- All target orgs receive their authorized accounts while permission assignments remain org-specific.
- Expired partner users lose access despite any prior successful login or stale external credential.
Explanation
Correct Answer
B:Best. The verification target is: Each verified customer is linked to one approved external user and customer identity record. It tests whether the chosen approach—Use supported B2C registration or automated provisioning mapped to the customer contact/account model.—actually resolves the specific finding: Members are customers linked to contacts rather than employees managed by the HR identity system.
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: Members are customers linked to contacts rather than employees managed by the HR identity system. The direct answer here is: Each verified customer is linked to one approved external user and customer identity record.
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: Members are customers linked to contacts rather than employees managed by the HR identity system. The direct answer here is: Each verified customer is linked to one approved external user and customer identity record.
D: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: Members are customers linked to contacts rather than employees managed by the HR identity system. The direct answer here is: Each verified customer is linked to one approved external user and customer identity record.
Question 158
A Salesforce integration initiative faces this situation: A large consumer loyalty website expects many external member registrations daily. The critical observation is: Members are customers linked to contacts rather than employees managed by the HR identity system. What failure is most likely if it is ignored?
- Incorrect contact-to-account linking lets one franchise view another franchise's orders.
- Treating consumer registrations as full internal user licenses creates an expensive inappropriate identity model.
- Only relying on first-login JIT leaves new staff missing access and departing users still active.
- One broad replicated role grants users privileges in an org where they have no business need.
Explanation
Correct Answer
B:Best. The most direct failure is: Treating consumer registrations as full internal user licenses creates an expensive inappropriate identity model. It is a consequence of the documented condition: Members are customers linked to contacts rather than employees managed by the HR identity system. A mitigation is: Use supported B2C registration or automated provisioning mapped to the customer contact/account model.
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: Members are customers linked to contacts rather than employees managed by the HR identity system. The direct answer here is: Treating consumer registrations as full internal user licenses creates an expensive inappropriate identity model.
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: Members are customers linked to contacts rather than employees managed by the HR identity system. The direct answer here is: Treating consumer registrations as full internal user licenses creates an expensive inappropriate identity model.
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: Members are customers linked to contacts rather than employees managed by the HR identity system. The direct answer here is: Treating consumer registrations as full internal user licenses creates an expensive inappropriate identity model.
Question 159
An integration architect receives this requirement: A consulting partner's Salesforce access should end immediately when its contract closes. A technical discovery also finds: The partner's external IdP controls authentication but Salesforce user records persist after contract end. Which response most directly addresses the present constraint?
- Combine federation with lifecycle-driven user deactivation and periodic contact/account entitlement reconciliation.
- Match on a stable external identity key and update the approved customer contact record.
- Use supported B2C registration or automated provisioning mapped to the customer contact/account model.
- Use lifecycle state and effective dates rather than assuming every imported record must be active.
Explanation
Correct Answer
A:Best. The most direct action is to combine federation with lifecycle-driven user deactivation and periodic contact/account entitlement reconciliation. It is supported by the specific finding that the partner's external IdP controls authentication but Salesforce user records persist after contract end. The expected acceptance evidence is: Expired partner users lose access despite any prior successful login or stale external credential.
Incorrect Answers
B: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: Combine federation with lifecycle-driven user deactivation and periodic contact/account entitlement reconciliation.
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: The partner's external IdP controls authentication but Salesforce user records persist after contract end. The direct answer here is: Combine federation with lifecycle-driven user deactivation and periodic contact/account entitlement reconciliation.
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 partner's external IdP controls authentication but Salesforce user records persist after contract end. The direct answer here is: Combine federation with lifecycle-driven user deactivation and periodic contact/account entitlement reconciliation.
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.