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 39

Question 380

An architect must create an acceptance test after choosing: Design minimal identity claims and scope configuration for the relying application. For the situation A company publishes a Salesforce-backed account portal that issues identity to a customer mobile application. Which result most directly proves success?

  1. Unapproved retired relying parties can no longer request valid identity assertions.
  2. External apps match existing users to stable identity records after the migration.
  3. The mobile application receives only necessary authenticated identity data and access permissions.
  4. Each employee grants personal scoped access and the next kiosk user sees no prior tokens.

Explanation

Correct Answer

C:

Best. The verification target is: The mobile application receives only necessary authenticated identity data and access permissions. It tests whether the chosen approach—Design minimal identity claims and scope configuration for the relying application.—actually resolves the specific finding: The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A security review discovers an unused Salesforce identity-provider service-provider registration. Its relevant condition is: The external application's contract ended but the trusted audience remains in configuration. The present case instead turns on: The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes. The direct answer here is: The mobile application receives only necessary authenticated identity data and access permissions.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An acquired company wants to move external application login from a vendor IdP to Salesforce identity. Its relevant condition is: User subject identifiers and service-provider audience settings differ from the old federation provider. The present case instead turns on: The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes. The direct answer here is: The mobile application receives only necessary authenticated identity data and access permissions.

D:

Not best for this scenario. This option is associated with another type of requirement: A finance firm wants a Salesforce-connected kiosk to let employees approve payments and then end the session. Its relevant condition is: The kiosk is shared and tokens must not persist across people or long idle periods. The present case instead turns on: The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes. The direct answer here is: The mobile application receives only necessary authenticated identity data and access permissions.

Question 381

An incident scenario concerns this architecture: A company publishes a Salesforce-backed account portal that issues identity to a customer mobile application. The team has discovered: The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes. Which project risk requires explicit mitigation?

  1. One blanket audience value allows an assertion for a low-risk app to unlock a sensitive app.
  2. Salesforce is configured only as a relying service provider and never issues the needed assertion.
  3. A former partner continues using an abandoned federation relationship after offboarding.
  4. Excessive claims disclose internal user fields to an external app without business justification.

Explanation

Correct Answer

D:

Best. The most direct failure is: Excessive claims disclose internal user fields to an external app without business justification. It is a consequence of the documented condition: The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes. A mitigation is: Design minimal identity claims and scope configuration for the relying application.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A manufacturer is onboarding several third-party apps that should trust Salesforce sign-in. Its relevant condition is: Each service has its own audience, service-provider metadata and trust configuration. The present case instead turns on: The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes. The direct answer here is: Excessive claims disclose internal user fields to an external app without business justification.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A company wants employees to use their Salesforce identity to sign into an external procurement portal. Its relevant condition is: The portal accepts SAML assertions issued by a trusted identity provider. The present case instead turns on: The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes. The direct answer here is: Excessive claims disclose internal user fields to an external app without business justification.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A security review discovers an unused Salesforce identity-provider service-provider registration. Its relevant condition is: The external application's contract ended but the trusted audience remains in configuration. The present case instead turns on: The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes. The direct answer here is: Excessive claims disclose internal user fields to an external app without business justification.

Question 382

An architecture board reviews a proposed Salesforce integration. Context: A security review discovers an unused Salesforce identity-provider service-provider registration. Finding: The external application's contract ended but the trusted audience remains in configuration. Which decision best resolves the concern?

  1. Configure Salesforce's supported OpenID Connect issuer/client integration with exact redirect and token claims.
  2. Coordinate Salesforce IdP signing-key rotation and update the external service provider trust metadata.
  3. Remove retired IdP-connected services and review certificates, scope grants and external access logs.
  4. Register separate connected apps or service providers with correct SAML or OIDC trust and scopes.

Explanation

Correct Answer

C:

Best. The most direct action is to remove retired IdP-connected services and review certificates, scope grants and external access logs. It is supported by the specific finding that the external application's contract ended but the trusted audience remains in configuration. The expected acceptance evidence is: Unapproved retired relying parties can no longer request valid identity assertions.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external partner dashboard wants to authenticate users against Salesforce using OpenID Connect. Its relevant condition is: The dashboard can validate signed ID tokens and maintain its own app-specific session. The present case instead turns on: The external application's contract ended but the trusted audience remains in configuration. The direct answer here is: Remove retired IdP-connected services and review certificates, scope grants and external access logs.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A payroll platform consumes Salesforce-issued SAML assertions and requires a certificate rollover. Its relevant condition is: The relying party still trusts an old Salesforce IdP signing certificate. The present case instead turns on: The external application's contract ended but the trusted audience remains in configuration. The direct answer here is: Remove retired IdP-connected services and review certificates, scope grants and external access logs.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A manufacturer is onboarding several third-party apps that should trust Salesforce sign-in. Its relevant condition is: Each service has its own audience, service-provider metadata and trust configuration. The present case instead turns on: The external application's contract ended but the trusted audience remains in configuration. The direct answer here is: Remove retired IdP-connected services and review certificates, scope grants and external access logs.

Question 383

A design workshop describes this environment: A security review discovers an unused Salesforce identity-provider service-provider registration. Which concrete observation should be documented as the most decisive issue?

  1. The external application's contract ended but the trusted audience remains in configuration.
  2. User subject identifiers and service-provider audience settings differ from the old federation provider.
  3. The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes.
  4. The relying party still trusts an old Salesforce IdP signing certificate.

Explanation

Correct Answer

A:

Best. The decisive observation is: The external application's contract ended but the trusted audience remains in configuration. This is why the design response should be: Remove retired IdP-connected services and review certificates, scope grants and external access logs.

Incorrect Answers

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An acquired company wants to move external application login from a vendor IdP to Salesforce identity. Its relevant condition is: User subject identifiers and service-provider audience settings differ from the old federation provider. The present case instead turns on: The external application's contract ended but the trusted audience remains in configuration. The direct answer here is: The external application's contract ended but the trusted audience remains in configuration.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A company publishes a Salesforce-backed account portal that issues identity to a customer mobile application. Its relevant condition is: The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes. The present case instead turns on: The external application's contract ended but the trusted audience remains in configuration. The direct answer here is: The external application's contract ended but the trusted audience remains in configuration.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A payroll platform consumes Salesforce-issued SAML assertions and requires a certificate rollover. Its relevant condition is: The relying party still trusts an old Salesforce IdP signing certificate. The present case instead turns on: The external application's contract ended but the trusted audience remains in configuration. The direct answer here is: The external application's contract ended but the trusted audience remains in configuration.

Question 384

An architect must create an acceptance test after choosing: Remove retired IdP-connected services and review certificates, scope grants and external access logs. For the situation A security review discovers an unused Salesforce identity-provider service-provider registration. Which result most directly proves success?

  1. Payroll validates the new assertions while unsupported older signing keys are retired safely.
  2. Each external app receives assertions or tokens intended specifically for its own client.
  3. The dashboard accepts validated Salesforce user identity and enforces its own authorization policy.
  4. Unapproved retired relying parties can no longer request valid identity assertions.

Explanation

Correct Answer

D:

Best. The verification target is: Unapproved retired relying parties can no longer request valid identity assertions. It tests whether the chosen approach—Remove retired IdP-connected services and review certificates, scope grants and external access logs.—actually resolves the specific finding: The external application's contract ended but the trusted audience remains in configuration.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A payroll platform consumes Salesforce-issued SAML assertions and requires a certificate rollover. Its relevant condition is: The relying party still trusts an old Salesforce IdP signing certificate. The present case instead turns on: The external application's contract ended but the trusted audience remains in configuration. The direct answer here is: Unapproved retired relying parties can no longer request valid identity assertions.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A manufacturer is onboarding several third-party apps that should trust Salesforce sign-in. Its relevant condition is: Each service has its own audience, service-provider metadata and trust configuration. The present case instead turns on: The external application's contract ended but the trusted audience remains in configuration. The direct answer here is: Unapproved retired relying parties can no longer request valid identity assertions.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external partner dashboard wants to authenticate users against Salesforce using OpenID Connect. Its relevant condition is: The dashboard can validate signed ID tokens and maintain its own app-specific session. The present case instead turns on: The external application's contract ended but the trusted audience remains in configuration. The direct answer here is: Unapproved retired relying parties can no longer request valid identity assertions.

Question 385

An incident scenario concerns this architecture: A security review discovers an unused Salesforce identity-provider service-provider registration. The team has discovered: The external application's contract ended but the trusted audience remains in configuration. Which project risk requires explicit mitigation?

  1. An OAuth API access token is blindly accepted as a signed ID token by the dashboard.
  2. A former partner continues using an abandoned federation relationship after offboarding.
  3. The cutover creates duplicate external application accounts and loses prior authorization mappings.
  4. Excessive claims disclose internal user fields to an external app without business justification.

Explanation

Correct Answer

B:

Best. The most direct failure is: A former partner continues using an abandoned federation relationship after offboarding. It is a consequence of the documented condition: The external application's contract ended but the trusted audience remains in configuration. A mitigation is: Remove retired IdP-connected services and review certificates, scope grants and external access logs.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external partner dashboard wants to authenticate users against Salesforce using OpenID Connect. Its relevant condition is: The dashboard can validate signed ID tokens and maintain its own app-specific session. The present case instead turns on: The external application's contract ended but the trusted audience remains in configuration. The direct answer here is: A former partner continues using an abandoned federation relationship after offboarding.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An acquired company wants to move external application login from a vendor IdP to Salesforce identity. Its relevant condition is: User subject identifiers and service-provider audience settings differ from the old federation provider. The present case instead turns on: The external application's contract ended but the trusted audience remains in configuration. The direct answer here is: A former partner continues using an abandoned federation relationship after offboarding.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A company publishes a Salesforce-backed account portal that issues identity to a customer mobile application. Its relevant condition is: The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes. The present case instead turns on: The external application's contract ended but the trusted audience remains in configuration. The direct answer here is: A former partner continues using an abandoned federation relationship after offboarding.

Question 386

In this fictional project, A finance director must export a confidential Salesforce report only after strong identity verification. The project team has uncovered that A normal authenticated session meets standard assurance but the export policy requires High Assurance. Which action is best supported by those facts?

  1. Distinguish noninteractive OAuth grants from flows that support user-driven step-up and choose compatible policy.
  2. Assign an appropriate supported MFA method to High Assurance and enforce the report's session policy.
  3. Review Session Security Levels and map the qualifying SSO method to the intended assurance category.
  4. Choose supported phishing-resistant MFA methods and stage enrollment, exceptions and recovery procedures.

Explanation

Correct Answer

B:

Best. The most direct action is to assign an appropriate supported MFA method to High Assurance and enforce the report's session policy. It is supported by the specific finding that A normal authenticated session meets standard assurance but the export policy requires High Assurance. The expected acceptance evidence is: Approved users complete the necessary step-up before sensitive export, while unverified sessions are blocked.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A connected app performs JWT bearer OAuth integration without an interactive user approval step. Its relevant condition is: A policy demands interactive High Assurance re-verification for every machine-generated token request. The present case instead turns on: A normal authenticated session meets standard assurance but the export policy requires High Assurance. The direct answer here is: Assign an appropriate supported MFA method to High Assurance and enforce the report's session policy.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise relies on its corporate SSO provider's MFA for Salesforce employee logins. Its relevant condition is: Salesforce is configured to treat that SSO method as Standard even when approved enterprise MFA is completed. The present case instead turns on: A normal authenticated session meets standard assurance but the export policy requires High Assurance. The direct answer here is: Assign an appropriate supported MFA method to High Assurance and enforce the report's session policy.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A security administrator plans to require phishing-resistant factors for privileged Salesforce access. Its relevant condition is: The chosen rollout includes no supported second-factor registration or recovery flow for impacted users. The present case instead turns on: A normal authenticated session meets standard assurance but the export policy requires High Assurance. The direct answer here is: Assign an appropriate supported MFA method to High Assurance and enforce the report's session policy.

Question 387

An enterprise review begins with this business situation: A finance director must export a confidential Salesforce report only after strong identity verification. Which technical or process signal best identifies the obstacle?

  1. A normal authenticated session meets standard assurance but the export policy requires High Assurance.
  2. The chosen rollout includes no supported second-factor registration or recovery flow for impacted users.
  3. Salesforce is configured to treat that SSO method as Standard even when approved enterprise MFA is completed.
  4. The existing session is authenticated but its assurance does not meet the resource's protection threshold.

Explanation

Correct Answer

A:

Best. The decisive observation is: A normal authenticated session meets standard assurance but the export policy requires High Assurance. This is why the design response should be: Assign an appropriate supported MFA method to High Assurance and enforce the report's session policy.

Incorrect Answers

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A security administrator plans to require phishing-resistant factors for privileged Salesforce access. Its relevant condition is: The chosen rollout includes no supported second-factor registration or recovery flow for impacted users. The present case instead turns on: A normal authenticated session meets standard assurance but the export policy requires High Assurance. The direct answer here is: A normal authenticated session meets standard assurance but the export policy requires High Assurance.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise relies on its corporate SSO provider's MFA for Salesforce employee logins. Its relevant condition is: Salesforce is configured to treat that SSO method as Standard even when approved enterprise MFA is completed. The present case instead turns on: A normal authenticated session meets standard assurance but the export policy requires High Assurance. The direct answer here is: A normal authenticated session meets standard assurance but the export policy requires High Assurance.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A healthcare organization wants to challenge an employee again before a sensitive account-change operation. Its relevant condition is: The existing session is authenticated but its assurance does not meet the resource's protection threshold. The present case instead turns on: A normal authenticated session meets standard assurance but the export policy requires High Assurance. The direct answer here is: A normal authenticated session meets standard assurance but the export policy requires High Assurance.

Question 388

The team adopts this approach: Assign an appropriate supported MFA method to High Assurance and enforce the report's session policy. The original project scenario is: A finance director must export a confidential Salesforce report only after strong identity verification. Which verification outcome best demonstrates that it worked?

  1. An ordinary session cannot perform the protected change until the required assurance is satisfied.
  2. Approved users complete the necessary step-up before sensitive export, while unverified sessions are blocked.
  3. Authorized federated sessions can satisfy the required Salesforce assurance without a redundant challenge.
  4. Approved machine operations use an appropriately scoped noninteractive pattern without pretending to perform MFA prompts.

Explanation

Correct Answer

B:

Best. The verification target is: Approved users complete the necessary step-up before sensitive export, while unverified sessions are blocked. It tests whether the chosen approach—Assign an appropriate supported MFA method to High Assurance and enforce the report's session policy.—actually resolves the specific finding: A normal authenticated session meets standard assurance but the export policy requires High Assurance.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A healthcare organization wants to challenge an employee again before a sensitive account-change operation. Its relevant condition is: The existing session is authenticated but its assurance does not meet the resource's protection threshold. The present case instead turns on: A normal authenticated session meets standard assurance but the export policy requires High Assurance. The direct answer here is: Approved users complete the necessary step-up before sensitive export, while unverified sessions are blocked.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise relies on its corporate SSO provider's MFA for Salesforce employee logins. Its relevant condition is: Salesforce is configured to treat that SSO method as Standard even when approved enterprise MFA is completed. The present case instead turns on: A normal authenticated session meets standard assurance but the export policy requires High Assurance. The direct answer here is: Approved users complete the necessary step-up before sensitive export, while unverified sessions are blocked.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A connected app performs JWT bearer OAuth integration without an interactive user approval step. Its relevant condition is: A policy demands interactive High Assurance re-verification for every machine-generated token request. The present case instead turns on: A normal authenticated session meets standard assurance but the export policy requires High Assurance. The direct answer here is: Approved users complete the necessary step-up before sensitive export, while unverified sessions are blocked.

Question 389

A project manager declines to address this finding: A normal authenticated session meets standard assurance but the export policy requires High Assurance. The related project is: A finance director must export a confidential Salesforce report only after strong identity verification. Which consequence most directly follows?

  1. The report exports successfully with only a standard login despite an explicit assurance requirement.
  2. An abrupt requirement locks out administrators who have no eligible factor registered.
  3. A JWT bearer service is blocked because the access policy requires an impossible interactive challenge.
  4. Highly privileged users lose access because no configured authentication method qualifies for High Assurance.

Explanation

Correct Answer

A:

Best. The most direct failure is: The report exports successfully with only a standard login despite an explicit assurance requirement. It is a consequence of the documented condition: A normal authenticated session meets standard assurance but the export policy requires High Assurance. A mitigation is: Assign an appropriate supported MFA method to High Assurance and enforce the report's session policy.

Incorrect Answers

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A security administrator plans to require phishing-resistant factors for privileged Salesforce access. Its relevant condition is: The chosen rollout includes no supported second-factor registration or recovery flow for impacted users. The present case instead turns on: A normal authenticated session meets standard assurance but the export policy requires High Assurance. The direct answer here is: The report exports successfully with only a standard login despite an explicit assurance requirement.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A connected app performs JWT bearer OAuth integration without an interactive user approval step. Its relevant condition is: A policy demands interactive High Assurance re-verification for every machine-generated token request. The present case instead turns on: A normal authenticated session meets standard assurance but the export policy requires High Assurance. The direct answer here is: The report exports successfully with only a standard login despite an explicit assurance requirement.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise relies on its corporate SSO provider's MFA for Salesforce employee logins. Its relevant condition is: Salesforce is configured to treat that SSO method as Standard even when approved enterprise MFA is completed. The present case instead turns on: A normal authenticated session meets standard assurance but the export policy requires High Assurance. The direct answer here is: The report exports successfully with only a standard login despite an explicit assurance requirement.

Question 390

A business group weighs design alternatives for this situation: A finance director must export a confidential Salesforce report only after strong identity verification. The architect recommends: Assign an appropriate supported MFA method to High Assurance and enforce the report's session policy. What most clearly justifies the decision?

  1. Avoid this consequence: An abrupt requirement locks out administrators who have no eligible factor registered. Achieve instead: Privileged employees meet the enforced authentication requirement and legitimate recovery remains governed.
  2. Avoid this consequence: The report exports successfully with only a standard login despite an explicit assurance requirement. Achieve instead: Approved users complete the necessary step-up before sensitive export, while unverified sessions are blocked.
  3. Avoid this consequence: Merely enabling MFA for some users is mistaken for enforcing High Assurance on the sensitive action. Achieve instead: An ordinary session cannot perform the protected change until the required assurance is satisfied.
  4. Avoid this consequence: A shared MFA device creates a false sense of strong user accountability despite shared credentials. Achieve instead: Each warehouse action can be traced to a distinct authorized employee after proper verification.

Explanation

Correct Answer

B:

Best. This tradeoff weighs the concrete risk that The report exports successfully with only a standard login despite an explicit assurance requirement. against the successful state: Approved users complete the necessary step-up before sensitive export, while unverified sessions are blocked. It supports the stated architectural decision: Assign an appropriate supported MFA method to High Assurance and enforce the report's session policy.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A security administrator plans to require phishing-resistant factors for privileged Salesforce access. Its relevant condition is: The chosen rollout includes no supported second-factor registration or recovery flow for impacted users. The present case instead turns on: A normal authenticated session meets standard assurance but the export policy requires High Assurance. The direct answer here is: Avoid this consequence: The report exports successfully with only a standard login despite an explicit assurance requirement. Achieve instead: Approved users complete the necessary step-up before sensitive export, while unverified sessions are blocked.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A healthcare organization wants to challenge an employee again before a sensitive account-change operation. Its relevant condition is: The existing session is authenticated but its assurance does not meet the resource's protection threshold. The present case instead turns on: A normal authenticated session meets standard assurance but the export policy requires High Assurance. The direct answer here is: Avoid this consequence: The report exports successfully with only a standard login despite an explicit assurance requirement. Achieve instead: Approved users complete the necessary step-up before sensitive export, while unverified sessions are blocked.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An organization enforces Salesforce MFA but allows shared accounts at a remote warehouse kiosk. Its relevant condition is: Staff use one login and share access to the second factor, preventing individual accountability. The present case instead turns on: A normal authenticated session meets standard assurance but the export policy requires High Assurance. The direct answer here is: Avoid this consequence: The report exports successfully with only a standard login despite an explicit assurance requirement. Achieve instead: Approved users complete the necessary step-up before sensitive export, while unverified sessions are blocked.

Certified Platform Identity and Access Management Architect Practice Tests