Salesforce Certified Platform Identity and Access Management Architect Practice Test 10
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.
Question 91
A project manager declines to address this finding: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. The related project is: A public membership site expects tens of thousands of new identity records each month. Which consequence most directly follows?
- Uncontrolled automatic registration creates redundant user records and inconsistent contact ownership.
- An account remains active indefinitely because the employee never attempts another login.
- Relying only on first-login creation leaves new employees without timely role assignments.
- Automating against an unreliable source creates unsponsored or long-lived identities.
Explanation
Correct Answer
A:Best. The most direct failure is: Uncontrolled automatic registration creates redundant user records and inconsistent contact ownership. It is a consequence of the documented condition: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. A mitigation is: 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 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: Uncontrolled automatic registration creates redundant user records and inconsistent contact ownership.
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: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. The direct answer here is: Uncontrolled automatic registration creates redundant user records and inconsistent contact ownership.
D: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: Uncontrolled automatic registration creates redundant user records and inconsistent contact ownership.
Question 92
In this fictional project, An HR offboarding process disables a departing worker in the corporate directory, but Salesforce stays active. The project team has uncovered that The federation setup creates users at login but lacks an event or batch process for deprovisioning. Which action is best supported by those facts?
- Use controlled manual account creation with explicit owners, role approval and expiry review.
- Evaluate SAML just-in-time provisioning with required attributes, federation identifiers and controlled defaults.
- Use supported external-user registration and provisioning with identity matching and approved license checks.
- Include lifecycle-driven deactivation, session cleanup and periodic reconciliation beyond JIT creation.
Explanation
Correct Answer
D:Best. The most direct action is to include lifecycle-driven deactivation, session cleanup and periodic reconciliation beyond JIT creation. It is supported by the specific finding that the federation setup creates users at login but lacks an event or batch process for deprovisioning. The expected acceptance evidence is: Departed workers cannot use existing sessions, API tokens or stale Salesforce access.
Incorrect Answers
A: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 federation setup creates users at login but lacks an event or batch process for deprovisioning. The direct answer here is: Include lifecycle-driven deactivation, session cleanup and periodic reconciliation beyond JIT creation.
B: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 federation setup creates users at login but lacks an event or batch process for deprovisioning. The direct answer here is: Include lifecycle-driven deactivation, session cleanup and periodic reconciliation beyond JIT creation.
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 federation setup creates users at login but lacks an event or batch process for deprovisioning. The direct answer here is: Include lifecycle-driven deactivation, session cleanup and periodic reconciliation beyond JIT creation.
Question 93
An enterprise review begins with this business situation: An HR offboarding process disables a departing worker in the corporate directory, but Salesforce stays active. Which technical or process signal best identifies the obstacle?
- Users need roles prepared before first access and timely removal when employment ends.
- The federation setup creates users at login but lacks an event or batch process for deprovisioning.
- 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.
Explanation
Correct Answer
B:Best. The decisive observation is: The federation setup creates users at login but lacks an event or batch process for deprovisioning. This is why the design response should be: Include lifecycle-driven deactivation, session cleanup and periodic reconciliation beyond JIT creation.
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 federation setup creates users at login but lacks an event or batch process for deprovisioning. The direct answer here is: The federation setup creates users at login but lacks an event or batch process for deprovisioning.
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 federation setup creates users at login but lacks an event or batch process for deprovisioning. The direct answer here is: The federation setup creates users at login but lacks an event or batch process for deprovisioning.
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 federation setup creates users at login but lacks an event or batch process for deprovisioning. The direct answer here is: The federation setup creates users at login but lacks an event or batch process for deprovisioning.
Question 94
The team adopts this approach: Include lifecycle-driven deactivation, session cleanup and periodic reconciliation beyond JIT creation. The original project scenario is: An HR offboarding process disables a departing worker in the corporate directory, but Salesforce stays active. Which verification outcome best demonstrates that it worked?
- New registrants receive one appropriately linked user record, with duplicates rejected or reconciled.
- A correctly signed initial assertion creates a scoped user who can access the permitted site.
- Departed workers cannot use existing sessions, API tokens or stale Salesforce access.
- Contractors receive appropriately scoped accounts with documented sponsorship and removal dates.
Explanation
Correct Answer
C:Best. The verification target is: Departed workers cannot use existing sessions, API tokens or stale Salesforce access. It tests whether the chosen approach—Include lifecycle-driven deactivation, session cleanup and periodic reconciliation beyond JIT creation.—actually resolves the specific finding: The federation setup creates users at login but lacks an event or batch process for deprovisioning.
Incorrect Answers
A: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 federation setup creates users at login but lacks an event or batch process for deprovisioning. The direct answer here is: Departed workers cannot use existing sessions, API tokens or stale Salesforce access.
B: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 federation setup creates users at login but lacks an event or batch process for deprovisioning. The direct answer here is: Departed workers cannot use existing sessions, API tokens or stale Salesforce access.
D: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 federation setup creates users at login but lacks an event or batch process for deprovisioning. The direct answer here is: Departed workers cannot use existing sessions, API tokens or stale Salesforce access.
Question 95
A project manager declines to address this finding: The federation setup creates users at login but lacks an event or batch process for deprovisioning. The related project is: An HR offboarding process disables a departing worker in the corporate directory, but Salesforce stays active. 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 outdated certificate configuration causes broad federation downtime.
- An account remains active indefinitely because the employee never attempts another login.
Explanation
Correct Answer
D:Best. The most direct failure is: An account remains active indefinitely because the employee never attempts another login. It is a consequence of the documented condition: The federation setup creates users at login but lacks an event or batch process for deprovisioning. A mitigation is: Include lifecycle-driven deactivation, session cleanup and periodic reconciliation beyond JIT creation.
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 federation setup creates users at login but lacks an event or batch process for deprovisioning. The direct answer here is: An account remains active indefinitely because the employee never attempts another login.
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 federation setup creates users at login but lacks an event or batch process for deprovisioning. The direct answer here is: An account remains active indefinitely because the employee never attempts another login.
C:Not best for this scenario. This option is associated with another type of requirement: A group of employees receives intermittent SAML signature failures after an identity-provider certificate rollover. Its relevant condition is: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The present case instead turns on: The federation setup creates users at login but lacks an event or batch process for deprovisioning. The direct answer here is: An account remains active indefinitely because the employee never attempts another login.
Question 96
In this fictional project, Salesforce rejects a newly deployed SAML integration with an invalid assertion audience error. The project team has uncovered that The IdP uses a destination string copied from a sandbox while the user is signing into production. Which action is best supported by those facts?
- Compare both initiation paths, relay destination and SAML login history before changing access policies.
- Compare the active signature certificate with trusted metadata, then rotate without weakening signature checks.
- Inspect the SAML assertion and Salesforce SSO configuration; correct entity IDs and audience mapping.
- Inspect NameID or federation identifier and user matching, then align immutable account identifiers.
Explanation
Correct Answer
C:Best. The most direct action is to inspect the SAML assertion and Salesforce SSO configuration; correct entity IDs and audience mapping. It is supported by the specific finding that the IdP uses a destination string copied from a sandbox while the user is signing into production. The expected acceptance evidence is: An assertion targeted at the production service provider is accepted after proper validation.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner reports sporadic SSO failures only when opening Salesforce from a bookmarked application link. Its relevant condition is: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The present case instead turns on: The IdP uses a destination string copied from a sandbox while the user is signing into production. The direct answer here is: Inspect the SAML assertion and Salesforce SSO configuration; correct entity IDs and audience mapping.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A group of employees receives intermittent SAML signature failures after an identity-provider certificate rollover. Its relevant condition is: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The present case instead turns on: The IdP uses a destination string copied from a sandbox while the user is signing into production. The direct answer here is: Inspect the SAML assertion and Salesforce SSO configuration; correct entity IDs and audience mapping.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A browser SSO login returns a valid assertion but Salesforce cannot find the intended existing user. Its relevant condition is: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The present case instead turns on: The IdP uses a destination string copied from a sandbox while the user is signing into production. The direct answer here is: Inspect the SAML assertion and Salesforce SSO configuration; correct entity IDs and audience mapping.
Question 97
An enterprise review begins with this business situation: Salesforce rejects a newly deployed SAML integration with an invalid assertion audience error. Which technical or process signal best identifies the obstacle?
- The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org.
- The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs.
- The IdP uses a destination string copied from a sandbox while the user is signing into production.
- The callback URL in the authorization request does not match the registered app redirect configuration.
Explanation
Correct Answer
C:Best. The decisive observation is: The IdP uses a destination string copied from a sandbox while the user is signing into production. This is why the design response should be: Inspect the SAML assertion and Salesforce SSO configuration; correct entity IDs and audience mapping.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A server-to-server integration fails with invalid_grant after a JWT-based OAuth rollout. Its relevant condition is: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. The present case instead turns on: The IdP uses a destination string copied from a sandbox while the user is signing into production. The direct answer here is: The IdP uses a destination string copied from a sandbox while the user is signing into production.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A group of employees receives intermittent SAML signature failures after an identity-provider certificate rollover. Its relevant condition is: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The present case instead turns on: The IdP uses a destination string copied from a sandbox while the user is signing into production. The direct answer here is: The IdP uses a destination string copied from a sandbox while the user is signing into production.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An OAuth client receives invalid_redirect_uri after its administrator migrates from test to production. Its relevant condition is: The callback URL in the authorization request does not match the registered app redirect configuration. The present case instead turns on: The IdP uses a destination string copied from a sandbox while the user is signing into production. The direct answer here is: The IdP uses a destination string copied from a sandbox while the user is signing into production.
Question 98
The team adopts this approach: Inspect the SAML assertion and Salesforce SSO configuration; correct entity IDs and audience mapping. The original project scenario is: Salesforce rejects a newly deployed SAML integration with an invalid assertion audience error. Which verification outcome best demonstrates that it worked?
- An assertion targeted at the production service provider is accepted after proper validation.
- A correctly signed and scoped assertion receives an access token without password storage.
- Approved entry points direct the user to the expected Salesforce page with valid authentication.
- The assertion maps to the correct existing Salesforce account without accidental user duplication.
Explanation
Correct Answer
A:Best. The verification target is: An assertion targeted at the production service provider is accepted after proper validation. It tests whether the chosen approach—Inspect the SAML assertion and Salesforce SSO configuration; correct entity IDs and audience mapping.—actually resolves the specific finding: The IdP uses a destination string copied from a sandbox while the user is signing into production.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A server-to-server integration fails with invalid_grant after a JWT-based OAuth rollout. Its relevant condition is: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. The present case instead turns on: The IdP uses a destination string copied from a sandbox while the user is signing into production. The direct answer here is: An assertion targeted at the production service provider is accepted after proper validation.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner reports sporadic SSO failures only when opening Salesforce from a bookmarked application link. Its relevant condition is: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The present case instead turns on: The IdP uses a destination string copied from a sandbox while the user is signing into production. The direct answer here is: An assertion targeted at the production service provider is accepted after proper validation.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A browser SSO login returns a valid assertion but Salesforce cannot find the intended existing user. Its relevant condition is: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The present case instead turns on: The IdP uses a destination string copied from a sandbox while the user is signing into production. The direct answer here is: An assertion targeted at the production service provider is accepted after proper validation.
Question 99
A project manager declines to address this finding: The IdP uses a destination string copied from a sandbox while the user is signing into production. The related project is: Salesforce rejects a newly deployed SAML integration with an invalid assertion audience error. Which consequence most directly follows?
- Admins disable assertion validation instead of correcting the environment mismatch.
- Allowing arbitrary redirect URIs exposes the authorization result to attacker-controlled endpoints.
- An outdated certificate configuration causes broad federation downtime.
- A valid employee is repeatedly rejected or provisioned as another identity.
Explanation
Correct Answer
A:Best. The most direct failure is: Admins disable assertion validation instead of correcting the environment mismatch. It is a consequence of the documented condition: The IdP uses a destination string copied from a sandbox while the user is signing into production. A mitigation is: Inspect the SAML assertion and Salesforce SSO configuration; correct entity IDs and audience mapping.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An OAuth client receives invalid_redirect_uri after its administrator migrates from test to production. Its relevant condition is: The callback URL in the authorization request does not match the registered app redirect configuration. The present case instead turns on: The IdP uses a destination string copied from a sandbox while the user is signing into production. The direct answer here is: Admins disable assertion validation instead of correcting the environment mismatch.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A group of employees receives intermittent SAML signature failures after an identity-provider certificate rollover. Its relevant condition is: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The present case instead turns on: The IdP uses a destination string copied from a sandbox while the user is signing into production. The direct answer here is: Admins disable assertion validation instead of correcting the environment mismatch.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A browser SSO login returns a valid assertion but Salesforce cannot find the intended existing user. Its relevant condition is: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The present case instead turns on: The IdP uses a destination string copied from a sandbox while the user is signing into production. The direct answer here is: Admins disable assertion validation instead of correcting the environment mismatch.
Question 100
An architecture board reviews a proposed Salesforce integration. Context: A group of employees receives intermittent SAML signature failures after an identity-provider certificate rollover. Finding: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. Which decision best resolves the concern?
- Compare the active signature certificate with trusted metadata, then rotate without weakening signature checks.
- Compare both initiation paths, relay destination and SAML login history before changing access policies.
- Validate ID-token signature and issuer, client audience, freshness and nonce against Salesforce configuration.
- Inspect the SAML assertion and Salesforce SSO configuration; correct entity IDs and audience mapping.
Explanation
Correct Answer
A:Best. The most direct action is to compare the active signature certificate with trusted metadata, then rotate without weakening signature checks. It is supported by the specific finding that the IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The expected acceptance evidence is: Login succeeds across affected orgs with the intended trusted signing certificate.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner reports sporadic SSO failures only when opening Salesforce from a bookmarked application link. Its relevant condition is: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The present case instead turns on: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The direct answer here is: Compare the active signature certificate with trusted metadata, then rotate without weakening signature checks.
C:Not best for this scenario. This option is associated with another type of requirement: A partner SaaS app signs in users using Salesforce as its OpenID Connect identity provider. Its relevant condition is: The app checks the user email claim but ignores the token signature, issuer and nonce. The present case instead turns on: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The direct answer here is: Compare the active signature certificate with trusted metadata, then rotate without weakening signature checks.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Salesforce rejects a newly deployed SAML integration with an invalid assertion audience error. Its relevant condition is: The IdP uses a destination string copied from a sandbox while the user is signing into production. The present case instead turns on: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The direct answer here is: Compare the active signature certificate with trusted metadata, then rotate without weakening signature checks.