Salesforce Certified Platform Identity and Access Management Architect Practice Test 9
Question 80
An integration architect receives this requirement: A support team manually creates Salesforce accounts for 15 contractor specialists with irregular engagement. A technical discovery also finds: The population is small, has no reliable automated directory feed and needs individualized approval. Which response most directly addresses the present constraint?
- Include lifecycle-driven deactivation, session cleanup and periodic reconciliation beyond JIT creation.
- Define allowed JIT update attributes and stable Federation IDs, and retest existing-user matches.
- Use supported external-user registration and provisioning with identity matching and approved license checks.
- Use controlled manual account creation with explicit owners, role approval and expiry review.
Explanation
Correct Answer
D:Best. The most direct action is to use controlled manual account creation with explicit owners, role approval and expiry review. It is supported by the specific finding that the population is small, has no reliable automated directory feed and needs individualized approval. The expected acceptance evidence is: Contractors receive appropriately scoped accounts with documented sponsorship and removal dates.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An HR offboarding process disables a departing worker in the corporate directory, but Salesforce stays active. Its relevant condition is: The federation setup creates users at login but lacks an event or batch process for deprovisioning. The present case instead turns on: The population is small, has no reliable automated directory feed and needs individualized approval. The direct answer here is: Use controlled manual account creation with explicit owners, role approval and expiry review.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external identity provider changes a person's surname and department shortly before a Salesforce SSO login. Its relevant condition is: The org's provisioning design never specifies whether authoritative attributes may be updated at login. The present case instead turns on: The population is small, has no reliable automated directory feed and needs individualized approval. The direct answer here is: Use controlled manual account creation with explicit owners, role approval and expiry review.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A public membership site expects tens of thousands of new identity records each month. Its relevant condition is: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. The present case instead turns on: The population is small, has no reliable automated directory feed and needs individualized approval. The direct answer here is: Use controlled manual account creation with explicit owners, role approval and expiry review.
Question 81
Consider the following hypothetical Salesforce initiative: A support team manually creates Salesforce accounts for 15 contractor specialists with irregular engagement. Which evidence would most strongly explain the current integration weakness?
- The partners may not have Salesforce user records before they initially authenticate.
- The federation setup creates users at login but lacks an event or batch process for deprovisioning.
- The population is small, has no reliable automated directory feed and needs individualized approval.
- Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts.
Explanation
Correct Answer
C:Best. The decisive observation is: The population is small, has no reliable automated directory feed and needs individualized approval. This is why the design response should be: Use controlled manual account creation with explicit owners, role approval and expiry review.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A limited partner population signs into Salesforce for the first time through a trusted SAML IdP. Its relevant condition is: The partners may not have Salesforce user records before they initially authenticate. The present case instead turns on: The population is small, has no reliable automated directory feed and needs individualized approval. The direct answer here is: The population is small, has no reliable automated directory feed and needs individualized approval.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An HR offboarding process disables a departing worker in the corporate directory, but Salesforce stays active. Its relevant condition is: The federation setup creates users at login but lacks an event or batch process for deprovisioning. The present case instead turns on: The population is small, has no reliable automated directory feed and needs individualized approval. The direct answer here is: The population is small, has no reliable automated directory feed and needs individualized approval.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A public membership site expects tens of thousands of new identity records each month. Its relevant condition is: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. The present case instead turns on: The population is small, has no reliable automated directory feed and needs individualized approval. The direct answer here is: The population is small, has no reliable automated directory feed and needs individualized approval.
Question 82
Review this change: Use controlled manual account creation with explicit owners, role approval and expiry review. It addresses a project where A support team manually creates Salesforce accounts for 15 contractor specialists with irregular engagement. Which result should appear in integration acceptance evidence?
- A correctly signed initial assertion creates a scoped user who can access the permitted site.
- New registrants receive one appropriately linked user record, with duplicates rejected or reconciled.
- Contractors receive appropriately scoped accounts with documented sponsorship and removal dates.
- The same Salesforce user is updated without creating a duplicate account when non-key attributes change.
Explanation
Correct Answer
C:Best. The verification target is: Contractors receive appropriately scoped accounts with documented sponsorship and removal dates. It tests whether the chosen approach—Use controlled manual account creation with explicit owners, role approval and expiry review.—actually resolves the specific finding: The population is small, has no reliable automated directory feed and needs individualized approval.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A limited partner population signs into Salesforce for the first time through a trusted SAML IdP. Its relevant condition is: The partners may not have Salesforce user records before they initially authenticate. The present case instead turns on: The population is small, has no reliable automated directory feed and needs individualized approval. The direct answer here is: Contractors receive appropriately scoped accounts with documented sponsorship and removal dates.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A public membership site expects tens of thousands of new identity records each month. Its relevant condition is: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. The present case instead turns on: The population is small, has no reliable automated directory feed and needs individualized approval. The direct answer here is: Contractors receive appropriately scoped accounts with documented sponsorship and removal dates.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external identity provider changes a person's surname and department shortly before a Salesforce SSO login. Its relevant condition is: The org's provisioning design never specifies whether authoritative attributes may be updated at login. The present case instead turns on: The population is small, has no reliable automated directory feed and needs individualized approval. The direct answer here is: Contractors receive appropriately scoped accounts with documented sponsorship and removal dates.
Question 83
Suppose the integration design proceeds without correcting this issue: The population is small, has no reliable automated directory feed and needs individualized approval. In the environment A support team manually creates Salesforce accounts for 15 contractor specialists with irregular engagement. What should the risk register emphasize?
- Missing mandatory JIT fields cause login failures or unintended profile assignment.
- Automating against an unreliable source creates unsponsored or long-lived identities.
- A display-name change generates a second Salesforce identity with conflicting access.
- An account remains active indefinitely because the employee never attempts another login.
Explanation
Correct Answer
B:Best. The most direct failure is: Automating against an unreliable source creates unsponsored or long-lived identities. It is a consequence of the documented condition: The population is small, has no reliable automated directory feed and needs individualized approval. A mitigation is: Use controlled manual account creation with explicit owners, role approval and expiry review.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A limited partner population signs into Salesforce for the first time through a trusted SAML IdP. Its relevant condition is: The partners may not have Salesforce user records before they initially authenticate. The present case instead turns on: The population is small, has no reliable automated directory feed and needs individualized approval. The direct answer here is: Automating against an unreliable source creates unsponsored or long-lived identities.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external identity provider changes a person's surname and department shortly before a Salesforce SSO login. Its relevant condition is: The org's provisioning design never specifies whether authoritative attributes may be updated at login. The present case instead turns on: The population is small, has no reliable automated directory feed and needs individualized approval. The direct answer here is: Automating against an unreliable source creates unsponsored or long-lived identities.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An HR offboarding process disables a departing worker in the corporate directory, but Salesforce stays active. Its relevant condition is: The federation setup creates users at login but lacks an event or batch process for deprovisioning. The present case instead turns on: The population is small, has no reliable automated directory feed and needs individualized approval. The direct answer here is: Automating against an unreliable source creates unsponsored or long-lived identities.
Question 84
In this fictional project, An external identity provider changes a person's surname and department shortly before a Salesforce SSO login. The project team has uncovered that The org's provisioning design never specifies whether authoritative attributes may be updated at login. Which action is best supported by those facts?
- Configure Salesforce as SAML service provider and have the trusted corporate IdP authenticate users.
- Define allowed JIT update attributes and stable Federation IDs, and retest existing-user matches.
- Use governed preprovisioning or supported identity lifecycle integration tied to HR state changes.
- Use supported external-user registration and provisioning with identity matching and approved license checks.
Explanation
Correct Answer
B:Best. The most direct action is to define allowed JIT update attributes and stable Federation IDs, and retest existing-user matches. It is supported by the specific finding that the org's provisioning design never specifies whether authoritative attributes may be updated at login. The expected acceptance evidence is: The same Salesforce user is updated without creating a duplicate account when non-key attributes change.
Incorrect Answers
A:Not best for this scenario. This option is associated with another type of requirement: A global manufacturer wants its workforce to access Salesforce and several SaaS applications after one corporate sign-in. Its relevant condition is: The existing workforce IdP can issue signed SAML assertions, while Salesforce must consume the authentication. The present case instead turns on: The org's provisioning design never specifies whether authoritative attributes may be updated at login. The direct answer here is: Define allowed JIT update attributes and stable Federation IDs, and retest existing-user matches.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A company provisions 20,000 employees nightly from its HR-driven identity directory to Salesforce. Its relevant condition is: Users need roles prepared before first access and timely removal when employment ends. The present case instead turns on: The org's provisioning design never specifies whether authoritative attributes may be updated at login. The direct answer here is: Define allowed JIT update attributes and stable Federation IDs, and retest existing-user matches.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A public membership site expects tens of thousands of new identity records each month. Its relevant condition is: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. The present case instead turns on: The org's provisioning design never specifies whether authoritative attributes may be updated at login. The direct answer here is: Define allowed JIT update attributes and stable Federation IDs, and retest existing-user matches.
Question 85
An enterprise review begins with this business situation: An external identity provider changes a person's surname and department shortly before a Salesforce SSO login. Which technical or process signal best identifies the obstacle?
- The partners may not have Salesforce user records before they initially authenticate.
- The org's provisioning design never specifies whether authoritative attributes may be updated at login.
- Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts.
- Users need roles prepared before first access and timely removal when employment ends.
Explanation
Correct Answer
B:Best. The decisive observation is: The org's provisioning design never specifies whether authoritative attributes may be updated at login. This is why the design response should be: Define allowed JIT update attributes and stable Federation IDs, and retest existing-user matches.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A limited partner population signs into Salesforce for the first time through a trusted SAML IdP. Its relevant condition is: The partners may not have Salesforce user records before they initially authenticate. The present case instead turns on: The org's provisioning design never specifies whether authoritative attributes may be updated at login. The direct answer here is: The org's provisioning design never specifies whether authoritative attributes may be updated at login.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A public membership site expects tens of thousands of new identity records each month. Its relevant condition is: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. The present case instead turns on: The org's provisioning design never specifies whether authoritative attributes may be updated at login. The direct answer here is: The org's provisioning design never specifies whether authoritative attributes may be updated at login.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A company provisions 20,000 employees nightly from its HR-driven identity directory to Salesforce. Its relevant condition is: Users need roles prepared before first access and timely removal when employment ends. The present case instead turns on: The org's provisioning design never specifies whether authoritative attributes may be updated at login. The direct answer here is: The org's provisioning design never specifies whether authoritative attributes may be updated at login.
Question 86
The team adopts this approach: Define allowed JIT update attributes and stable Federation IDs, and retest existing-user matches. The original project scenario is: An external identity provider changes a person's surname and department shortly before a Salesforce SSO login. Which verification outcome best demonstrates that it worked?
- Accounts, entitlement assignments and deactivation reconcile before employees attempt login.
- The same Salesforce user is updated without creating a duplicate account when non-key attributes change.
- New registrants receive one appropriately linked user record, with duplicates rejected or reconciled.
- Departed workers cannot use existing sessions, API tokens or stale Salesforce access.
Explanation
Correct Answer
B:Best. The verification target is: The same Salesforce user is updated without creating a duplicate account when non-key attributes change. It tests whether the chosen approach—Define allowed JIT update attributes and stable Federation IDs, and retest existing-user matches.—actually resolves the specific finding: The org's provisioning design never specifies whether authoritative attributes may be updated at login.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A company provisions 20,000 employees nightly from its HR-driven identity directory to Salesforce. Its relevant condition is: Users need roles prepared before first access and timely removal when employment ends. The present case instead turns on: The org's provisioning design never specifies whether authoritative attributes may be updated at login. The direct answer here is: The same Salesforce user is updated without creating a duplicate account when non-key attributes change.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A public membership site expects tens of thousands of new identity records each month. Its relevant condition is: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. The present case instead turns on: The org's provisioning design never specifies whether authoritative attributes may be updated at login. The direct answer here is: The same Salesforce user is updated without creating a duplicate account when non-key attributes change.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An HR offboarding process disables a departing worker in the corporate directory, but Salesforce stays active. Its relevant condition is: The federation setup creates users at login but lacks an event or batch process for deprovisioning. The present case instead turns on: The org's provisioning design never specifies whether authoritative attributes may be updated at login. The direct answer here is: The same Salesforce user is updated without creating a duplicate account when non-key attributes change.
Question 87
A project manager declines to address this finding: The org's provisioning design never specifies whether authoritative attributes may be updated at login. The related project is: An external identity provider changes a person's surname and department shortly before a Salesforce SSO login. Which consequence most directly follows?
- Relying only on first-login creation leaves new employees without timely role assignments.
- Automating against an unreliable source creates unsponsored or long-lived identities.
- An account remains active indefinitely because the employee never attempts another login.
- A display-name change generates a second Salesforce identity with conflicting access.
Explanation
Correct Answer
D:Best. The most direct failure is: A display-name change generates a second Salesforce identity with conflicting access. It is a consequence of the documented condition: The org's provisioning design never specifies whether authoritative attributes may be updated at login. A mitigation is: Define allowed JIT update attributes and stable Federation IDs, and retest existing-user matches.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A company provisions 20,000 employees nightly from its HR-driven identity directory to Salesforce. Its relevant condition is: Users need roles prepared before first access and timely removal when employment ends. The present case instead turns on: The org's provisioning design never specifies whether authoritative attributes may be updated at login. The direct answer here is: A display-name change generates a second Salesforce identity with conflicting access.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A support team manually creates Salesforce accounts for 15 contractor specialists with irregular engagement. Its relevant condition is: The population is small, has no reliable automated directory feed and needs individualized approval. The present case instead turns on: The org's provisioning design never specifies whether authoritative attributes may be updated at login. The direct answer here is: A display-name change generates a second Salesforce identity with conflicting access.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An HR offboarding process disables a departing worker in the corporate directory, but Salesforce stays active. Its relevant condition is: The federation setup creates users at login but lacks an event or batch process for deprovisioning. The present case instead turns on: The org's provisioning design never specifies whether authoritative attributes may be updated at login. The direct answer here is: A display-name change generates a second Salesforce identity with conflicting access.
Question 88
In this fictional project, A public membership site expects tens of thousands of new identity records each month. The project team has uncovered that Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. Which action is best supported by those facts?
- Include lifecycle-driven deactivation, session cleanup and periodic reconciliation beyond JIT creation.
- Define allowed JIT update attributes and stable Federation IDs, and retest existing-user matches.
- Use supported external-user registration and provisioning with identity matching and approved license checks.
- Evaluate SAML just-in-time provisioning with required attributes, federation identifiers and controlled defaults.
Explanation
Correct Answer
C:Best. The most direct action is to use supported external-user registration and provisioning with identity matching and approved license checks. It is supported by the specific finding that Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. The expected acceptance evidence is: New registrants receive one appropriately linked user record, with duplicates rejected or reconciled.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An HR offboarding process disables a departing worker in the corporate directory, but Salesforce stays active. Its relevant condition is: The federation setup creates users at login but lacks an event or batch process for deprovisioning. The present case instead turns on: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. The direct answer here is: Use supported external-user registration and provisioning with identity matching and approved license checks.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external identity provider changes a person's surname and department shortly before a Salesforce SSO login. Its relevant condition is: The org's provisioning design never specifies whether authoritative attributes may be updated at login. The present case instead turns on: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. The direct answer here is: Use supported external-user registration and provisioning with identity matching and approved license checks.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A limited partner population signs into Salesforce for the first time through a trusted SAML IdP. Its relevant condition is: The partners may not have Salesforce user records before they initially authenticate. The present case instead turns on: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. The direct answer here is: Use supported external-user registration and provisioning with identity matching and approved license checks.
Question 89
An enterprise review begins with this business situation: A public membership site expects tens of thousands of new identity records each month. Which technical or process signal best identifies the obstacle?
- Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts.
- The org's provisioning design never specifies whether authoritative attributes may be updated at login.
- The population is small, has no reliable automated directory feed and needs individualized approval.
- The partners may not have Salesforce user records before they initially authenticate.
Explanation
Correct Answer
A:Best. The decisive observation is: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. This is why the design response should be: Use supported external-user registration and provisioning with identity matching and approved license checks.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external identity provider changes a person's surname and department shortly before a Salesforce SSO login. Its relevant condition is: The org's provisioning design never specifies whether authoritative attributes may be updated at login. The present case instead turns on: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. The direct answer here is: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A support team manually creates Salesforce accounts for 15 contractor specialists with irregular engagement. Its relevant condition is: The population is small, has no reliable automated directory feed and needs individualized approval. The present case instead turns on: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. The direct answer here is: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A limited partner population signs into Salesforce for the first time through a trusted SAML IdP. Its relevant condition is: The partners may not have Salesforce user records before they initially authenticate. The present case instead turns on: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. The direct answer here is: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts.
Question 90
The team adopts this approach: Use supported external-user registration and provisioning with identity matching and approved license checks. The original project scenario is: A public membership site expects tens of thousands of new identity records each month. Which verification outcome best demonstrates that it worked?
- New registrants receive one appropriately linked user record, with duplicates rejected or reconciled.
- Accounts, entitlement assignments and deactivation reconcile before employees attempt login.
- Contractors receive appropriately scoped accounts with documented sponsorship and removal dates.
- The same Salesforce user is updated without creating a duplicate account when non-key attributes change.
Explanation
Correct Answer
A:Best. The verification target is: New registrants receive one appropriately linked user record, with duplicates rejected or reconciled. It tests whether the chosen approach—Use supported external-user registration and provisioning with identity matching and approved license checks.—actually resolves the specific finding: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A company provisions 20,000 employees nightly from its HR-driven identity directory to Salesforce. Its relevant condition is: Users need roles prepared before first access and timely removal when employment ends. The present case instead turns on: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. The direct answer here is: New registrants receive one appropriately linked user record, with duplicates rejected or reconciled.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A support team manually creates Salesforce accounts for 15 contractor specialists with irregular engagement. Its relevant condition is: The population is small, has no reliable automated directory feed and needs individualized approval. The present case instead turns on: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. The direct answer here is: New registrants receive one appropriately linked user record, with duplicates rejected or reconciled.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external identity provider changes a person's surname and department shortly before a Salesforce SSO login. Its relevant condition is: The org's provisioning design never specifies whether authoritative attributes may be updated at login. The present case instead turns on: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. The direct answer here is: New registrants receive one appropriately linked user record, with duplicates rejected or reconciled.