cert
cert-1
cert-2

Pass Salesforce Certified Platform Identity and Access Management Architect Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
Certified Platform Identity and Access Management Architect Exam - Verified By Experts
Certified Platform Identity and Access Management Architect Premium File

Certified Platform Identity and Access Management Architect Premium File

$69.99
$76.99
  • Premium File 58 Questions & Answers. Last Update: Nov 17, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$76.99
$69.99
accept 10 downloads in the last 7 days
block-screenshots
Salesforce Certified Platform Identity and Access Management Architect Practice Test 8

Question 70

An architect must create an acceptance test after choosing: Review and remove obsolete trusted IdP and certificate entries after migration and access testing. For the situation Security analysts discover an old Salesforce SAML configuration still trusts a retired partner certificate. Which result most directly proves success?

  1. Each relying party accepts assertions only for its own registered trust configuration.
  2. Only Salesforce-issued identity claims intended for this client establish user authentication.
  3. Retired federation relationships no longer provide a valid route to Salesforce authentication.
  4. Salesforce accepts only assertions addressed to its service and signed by the configured partner.

Explanation

Correct Answer

C:

Best. The verification target is: Retired federation relationships no longer provide a valid route to Salesforce authentication. It tests whether the chosen approach—Review and remove obsolete trusted IdP and certificate entries after migration and access testing.—actually resolves the specific finding: The partner relationship ended, but the IdP metadata and signing key remain active.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise adds two service providers that share one Salesforce identity provider. Its relevant condition is: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. The present case instead turns on: The partner relationship ended, but the IdP metadata and signing key remain active. The direct answer here is: Retired federation relationships no longer provide a valid route to Salesforce authentication.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: 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 partner relationship ended, but the IdP metadata and signing key remain active. The direct answer here is: Retired federation relationships no longer provide a valid route to Salesforce authentication.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A retail brand wants only its approved partner identity provider to authenticate users into Salesforce. Its relevant condition is: An incoming assertion names the right user but has an unexpected issuer and audience value. The present case instead turns on: The partner relationship ended, but the IdP metadata and signing key remain active. The direct answer here is: Retired federation relationships no longer provide a valid route to Salesforce authentication.

Question 71

An incident scenario concerns this architecture: Security analysts discover an old Salesforce SAML configuration still trusts a retired partner certificate. The team has discovered: The partner relationship ended, but the IdP metadata and signing key remain active. Which project risk requires explicit mitigation?

  1. A former partner uses stale trust metadata to keep signing accepted login assertions.
  2. The broker accidentally launders untrusted identity assertions from an unrelated IdP.
  3. A valid assertion intended for a different application is replayed to Salesforce.
  4. A captured assertion for one application opens an unrelated service.

Explanation

Correct Answer

A:

Best. The most direct failure is: A former partner uses stale trust metadata to keep signing accepted login assertions. It is a consequence of the documented condition: The partner relationship ended, but the IdP metadata and signing key remain active. A mitigation is: Review and remove obsolete trusted IdP and certificate entries after migration and access testing.

Incorrect Answers

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A distributed company adds an identity broker between an external IdP and Salesforce. Its relevant condition is: The proposed broker forwards assertions without documenting which component signs or verifies them. The present case instead turns on: The partner relationship ended, but the IdP metadata and signing key remain active. The direct answer here is: A former partner uses stale trust metadata to keep signing accepted login assertions.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A retail brand wants only its approved partner identity provider to authenticate users into Salesforce. Its relevant condition is: An incoming assertion names the right user but has an unexpected issuer and audience value. The present case instead turns on: The partner relationship ended, but the IdP metadata and signing key remain active. The direct answer here is: A former partner uses stale trust metadata to keep signing accepted login assertions.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise adds two service providers that share one Salesforce identity provider. Its relevant condition is: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. The present case instead turns on: The partner relationship ended, but the IdP metadata and signing key remain active. The direct answer here is: A former partner uses stale trust metadata to keep signing accepted login assertions.

Question 72

In this fictional project, A company provisions 20,000 employees nightly from its HR-driven identity directory to Salesforce. The project team has uncovered that Users need roles prepared before first access and timely removal when employment ends. Which action is best supported by those facts?

  1. Use governed preprovisioning or supported identity lifecycle integration tied to HR state changes.
  2. Use controlled manual account creation with explicit owners, role approval and expiry review.
  3. Define allowed JIT update attributes and stable Federation IDs, and retest existing-user matches.
  4. Use supported external-user registration and provisioning with identity matching and approved license checks.

Explanation

Correct Answer

A:

Best. The most direct action is to use governed preprovisioning or supported identity lifecycle integration tied to HR state changes. It is supported by the specific finding that Users need roles prepared before first access and timely removal when employment ends. The expected acceptance evidence is: Accounts, entitlement assignments and deactivation reconcile before employees attempt login.

Incorrect Answers

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: Users need roles prepared before first access and timely removal when employment ends. The direct answer here is: Use governed preprovisioning or supported identity lifecycle integration tied to HR state changes.

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: Users need roles prepared before first access and timely removal when employment ends. The direct answer here is: Use governed preprovisioning or supported identity lifecycle integration tied to HR state changes.

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: Users need roles prepared before first access and timely removal when employment ends. The direct answer here is: Use governed preprovisioning or supported identity lifecycle integration tied to HR state changes.

Question 73

An enterprise review begins with this business situation: A company provisions 20,000 employees nightly from its HR-driven identity directory to Salesforce. Which technical or process signal best identifies the obstacle?

  1. Users need roles prepared before first access and timely removal when employment ends.
  2. The population is small, has no reliable automated directory feed and needs individualized approval.
  3. The partners may not have Salesforce user records before they initially authenticate.
  4. The federation setup creates users at login but lacks an event or batch process for deprovisioning.

Explanation

Correct Answer

A:

Best. The decisive observation is: Users need roles prepared before first access and timely removal when employment ends. This is why the design response should be: Use governed preprovisioning or supported identity lifecycle integration tied to HR state changes.

Incorrect Answers

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: Users need roles prepared before first access and timely removal when employment ends. The direct answer here is: Users need roles prepared before first access and timely removal when employment ends.

C:

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: Users need roles prepared before first access and timely removal when employment ends. The direct answer here is: Users need roles prepared before first access and timely removal when employment ends.

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: Users need roles prepared before first access and timely removal when employment ends. The direct answer here is: Users need roles prepared before first access and timely removal when employment ends.

Question 74

The team adopts this approach: Use governed preprovisioning or supported identity lifecycle integration tied to HR state changes. The original project scenario is: A company provisions 20,000 employees nightly from its HR-driven identity directory to Salesforce. Which verification outcome best demonstrates that it worked?

  1. New registrants receive one appropriately linked user record, with duplicates rejected or reconciled.
  2. Contractors receive appropriately scoped accounts with documented sponsorship and removal dates.
  3. Departed workers cannot use existing sessions, API tokens or stale Salesforce access.
  4. Accounts, entitlement assignments and deactivation reconcile before employees attempt login.

Explanation

Correct Answer

D:

Best. The verification target is: Accounts, entitlement assignments and deactivation reconcile before employees attempt login. It tests whether the chosen approach—Use governed preprovisioning or supported identity lifecycle integration tied to HR state changes.—actually resolves the specific finding: Users need roles prepared before first access and timely removal when employment ends.

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: Users need roles prepared before first access and timely removal when employment ends. The direct answer here is: Accounts, entitlement assignments and deactivation reconcile before employees attempt 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: Users need roles prepared before first access and timely removal when employment ends. The direct answer here is: Accounts, entitlement assignments and deactivation reconcile before employees attempt login.

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: Users need roles prepared before first access and timely removal when employment ends. The direct answer here is: Accounts, entitlement assignments and deactivation reconcile before employees attempt login.

Question 75

A project manager declines to address this finding: Users need roles prepared before first access and timely removal when employment ends. The related project is: A company provisions 20,000 employees nightly from its HR-driven identity directory to Salesforce. Which consequence most directly follows?

  1. Relying only on first-login creation leaves new employees without timely role assignments.
  2. Missing mandatory JIT fields cause login failures or unintended profile assignment.
  3. A display-name change generates a second Salesforce identity with conflicting access.
  4. Automating against an unreliable source creates unsponsored or long-lived identities.

Explanation

Correct Answer

A:

Best. The most direct failure is: Relying only on first-login creation leaves new employees without timely role assignments. It is a consequence of the documented condition: Users need roles prepared before first access and timely removal when employment ends. A mitigation is: Use governed preprovisioning or supported identity lifecycle integration tied to HR state changes.

Incorrect Answers

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: Users need roles prepared before first access and timely removal when employment ends. The direct answer here is: Relying only on first-login creation leaves new employees without timely role assignments.

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: Users need roles prepared before first access and timely removal when employment ends. The direct answer here is: Relying only on first-login creation leaves new employees without timely role assignments.

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: Users need roles prepared before first access and timely removal when employment ends. The direct answer here is: Relying only on first-login creation leaves new employees without timely role assignments.

Question 76

Salesforce and its partners face the following situation: A limited partner population signs into Salesforce for the first time through a trusted SAML IdP. The integration review notes: The partners may not have Salesforce user records before they initially authenticate. Which architectural step should take priority?

  1. Evaluate SAML just-in-time provisioning with required attributes, federation identifiers and controlled defaults.
  2. Include lifecycle-driven deactivation, session cleanup and periodic reconciliation beyond JIT creation.
  3. Use governed preprovisioning or supported identity lifecycle integration tied to HR state changes.
  4. Define allowed JIT update attributes and stable Federation IDs, and retest existing-user matches.

Explanation

Correct Answer

A:

Best. The most direct action is to evaluate SAML just-in-time provisioning with required attributes, federation identifiers and controlled defaults. It is supported by the specific finding that the partners may not have Salesforce user records before they initially authenticate. The expected acceptance evidence is: A correctly signed initial assertion creates a scoped user who can access the permitted site.

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: The partners may not have Salesforce user records before they initially authenticate. The direct answer here is: Evaluate SAML just-in-time provisioning with required attributes, federation identifiers and controlled defaults.

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 partners may not have Salesforce user records before they initially authenticate. The direct answer here is: Evaluate SAML just-in-time provisioning with required attributes, federation identifiers and controlled defaults.

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 partners may not have Salesforce user records before they initially authenticate. The direct answer here is: Evaluate SAML just-in-time provisioning with required attributes, federation identifiers and controlled defaults.

Question 77

An implementation team investigates this scenario: A limited partner population signs into Salesforce for the first time through a trusted SAML IdP. Which finding would most directly justify a change to the integration architecture?

  1. The partners may not have Salesforce user records before they initially authenticate.
  2. Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts.
  3. The org's provisioning design never specifies whether authoritative attributes may be updated at login.
  4. The federation setup creates users at login but lacks an event or batch process for deprovisioning.

Explanation

Correct Answer

A:

Best. The decisive observation is: The partners may not have Salesforce user records before they initially authenticate. This is why the design response should be: Evaluate SAML just-in-time provisioning with required attributes, federation identifiers and controlled defaults.

Incorrect Answers

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 partners may not have Salesforce user records before they initially authenticate. The direct answer here is: The partners may not have Salesforce user records before they initially authenticate.

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 partners may not have Salesforce user records before they initially authenticate. The direct answer here is: The partners may not have Salesforce user records before they initially authenticate.

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 partners may not have Salesforce user records before they initially authenticate. The direct answer here is: The partners may not have Salesforce user records before they initially authenticate.

Question 78

A solution review asks whether this control is effective: Evaluate SAML just-in-time provisioning with required attributes, federation identifiers and controlled defaults. The business setting is: A limited partner population signs into Salesforce for the first time through a trusted SAML IdP. What should a demonstrable successful outcome be?

  1. Accounts, entitlement assignments and deactivation reconcile before employees attempt login.
  2. Departed workers cannot use existing sessions, API tokens or stale Salesforce access.
  3. The same Salesforce user is updated without creating a duplicate account when non-key attributes change.
  4. A correctly signed initial assertion creates a scoped user who can access the permitted site.

Explanation

Correct Answer

D:

Best. The verification target is: A correctly signed initial assertion creates a scoped user who can access the permitted site. It tests whether the chosen approach—Evaluate SAML just-in-time provisioning with required attributes, federation identifiers and controlled defaults.—actually resolves the specific finding: The partners may not have Salesforce user records before they initially authenticate.

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 partners may not have Salesforce user records before they initially authenticate. The direct answer here is: A correctly signed initial assertion creates a scoped user who can access the permitted site.

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 partners may not have Salesforce user records before they initially authenticate. The direct answer here is: A correctly signed initial assertion creates a scoped user who can access the permitted site.

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 partners may not have Salesforce user records before they initially authenticate. The direct answer here is: A correctly signed initial assertion creates a scoped user who can access the permitted site.

Question 79

A Salesforce integration initiative faces this situation: A limited partner population signs into Salesforce for the first time through a trusted SAML IdP. The critical observation is: The partners may not have Salesforce user records before they initially authenticate. What failure is most likely if it is ignored?

  1. An account remains active indefinitely because the employee never attempts another login.
  2. Uncontrolled automatic registration creates redundant user records and inconsistent contact ownership.
  3. Missing mandatory JIT fields cause login failures or unintended profile assignment.
  4. Automating against an unreliable source creates unsponsored or long-lived identities.

Explanation

Correct Answer

C:

Best. The most direct failure is: Missing mandatory JIT fields cause login failures or unintended profile assignment. It is a consequence of the documented condition: The partners may not have Salesforce user records before they initially authenticate. A mitigation is: Evaluate SAML just-in-time provisioning with required attributes, federation identifiers and controlled defaults.

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 partners may not have Salesforce user records before they initially authenticate. The direct answer here is: Missing mandatory JIT fields cause login failures or unintended profile assignment.

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 partners may not have Salesforce user records before they initially authenticate. The direct answer here is: Missing mandatory JIT fields cause login failures or unintended profile assignment.

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 partners may not have Salesforce user records before they initially authenticate. The direct answer here is: Missing mandatory JIT fields cause login failures or unintended profile assignment.

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?

  1. Include lifecycle-driven deactivation, session cleanup and periodic reconciliation beyond JIT creation.
  2. Define allowed JIT update attributes and stable Federation IDs, and retest existing-user matches.
  3. Use supported external-user registration and provisioning with identity matching and approved license checks.
  4. 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.

Certified Platform Identity and Access Management Architect Practice Tests