Salesforce Certified Platform Identity and Access Management Architect Practice Test 37
Question 360
A solution review asks whether this control is effective: Enable Salesforce's supported IdP role and configure the procurement portal as a SAML service provider. The business setting is: A company wants employees to use their Salesforce identity to sign into an external procurement portal. What should a demonstrable successful outcome be?
- The mobile application receives only necessary authenticated identity data and access permissions.
- The dashboard accepts validated Salesforce user identity and enforces its own authorization policy.
- Employees authenticate with Salesforce and access the portal through validated Salesforce-signed assertions.
- Unapproved retired relying parties can no longer request valid identity assertions.
Explanation
Correct Answer
C:Best. The verification target is: Employees authenticate with Salesforce and access the portal through validated Salesforce-signed assertions. It tests whether the chosen approach—Enable Salesforce's supported IdP role and configure the procurement portal as a SAML service provider.—actually resolves the specific finding: The portal accepts SAML assertions issued by a trusted identity provider.
Incorrect Answers
A: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 portal accepts SAML assertions issued by a trusted identity provider. The direct answer here is: Employees authenticate with Salesforce and access the portal through validated Salesforce-signed assertions.
B: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 portal accepts SAML assertions issued by a trusted identity provider. The direct answer here is: Employees authenticate with Salesforce and access the portal through validated Salesforce-signed assertions.
D: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 portal accepts SAML assertions issued by a trusted identity provider. The direct answer here is: Employees authenticate with Salesforce and access the portal through validated Salesforce-signed assertions.
Question 361
A Salesforce integration initiative faces this situation: A company wants employees to use their Salesforce identity to sign into an external procurement portal. The critical observation is: The portal accepts SAML assertions issued by a trusted identity provider. What failure is most likely if it is ignored?
- One blanket audience value allows an assertion for a low-risk app to unlock a sensitive app.
- Salesforce is configured only as a relying service provider and never issues the needed assertion.
- An OAuth API access token is blindly accepted as a signed ID token by the dashboard.
- A former partner continues using an abandoned federation relationship after offboarding.
Explanation
Correct Answer
B:Best. The most direct failure is: Salesforce is configured only as a relying service provider and never issues the needed assertion. It is a consequence of the documented condition: The portal accepts SAML assertions issued by a trusted identity provider. A mitigation is: Enable Salesforce's supported IdP role and configure the procurement portal as a SAML service provider.
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 portal accepts SAML assertions issued by a trusted identity provider. The direct answer here is: Salesforce is configured only as a relying service provider and never issues the needed assertion.
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 portal accepts SAML assertions issued by a trusted identity provider. The direct answer here is: Salesforce is configured only as a relying service provider and never issues the needed assertion.
D: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 portal accepts SAML assertions issued by a trusted identity provider. The direct answer here is: Salesforce is configured only as a relying service provider and never issues the needed assertion.
Question 362
An integration architect receives this requirement: An external partner dashboard wants to authenticate users against Salesforce using OpenID Connect. A technical discovery also finds: The dashboard can validate signed ID tokens and maintain its own app-specific session. Which response most directly addresses the present constraint?
- Map account identifiers and configure Salesforce IdP signing, assertion attributes and trusted service providers.
- Register separate connected apps or service providers with correct SAML or OIDC trust and scopes.
- Remove retired IdP-connected services and review certificates, scope grants and external access logs.
- Configure Salesforce's supported OpenID Connect issuer/client integration with exact redirect and token claims.
Explanation
Correct Answer
D:Best. The most direct action is to configure Salesforce's supported OpenID Connect issuer/client integration with exact redirect and token claims. It is supported by the specific finding that the dashboard can validate signed ID tokens and maintain its own app-specific session. The expected acceptance evidence is: The dashboard accepts validated Salesforce user identity and enforces its own authorization policy.
Incorrect Answers
A: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 dashboard can validate signed ID tokens and maintain its own app-specific session. The direct answer here is: Configure Salesforce's supported OpenID Connect issuer/client integration with exact redirect and token claims.
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 dashboard can validate signed ID tokens and maintain its own app-specific session. The direct answer here is: Configure Salesforce's supported OpenID Connect issuer/client integration with exact redirect and token claims.
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 dashboard can validate signed ID tokens and maintain its own app-specific session. The direct answer here is: Configure Salesforce's supported OpenID Connect issuer/client integration with exact redirect and token claims.
Question 363
Consider the following hypothetical Salesforce initiative: An external partner dashboard wants to authenticate users against Salesforce using OpenID Connect. Which evidence would most strongly explain the current integration weakness?
- The dashboard can validate signed ID tokens and maintain its own app-specific session.
- The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes.
- User subject identifiers and service-provider audience settings differ from the old federation provider.
- The portal accepts SAML assertions issued by a trusted identity provider.
Explanation
Correct Answer
A:Best. The decisive observation is: The dashboard can validate signed ID tokens and maintain its own app-specific session. This is why the design response should be: Configure Salesforce's supported OpenID Connect issuer/client integration with exact redirect and token claims.
Incorrect Answers
B: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 dashboard can validate signed ID tokens and maintain its own app-specific session. The direct answer here is: The dashboard can validate signed ID tokens and maintain its own app-specific session.
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 dashboard can validate signed ID tokens and maintain its own app-specific session. The direct answer here is: The dashboard can validate signed ID tokens and maintain its own app-specific session.
D: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 dashboard can validate signed ID tokens and maintain its own app-specific session. The direct answer here is: The dashboard can validate signed ID tokens and maintain its own app-specific session.
Question 364
Review this change: Configure Salesforce's supported OpenID Connect issuer/client integration with exact redirect and token claims. It addresses a project where An external partner dashboard wants to authenticate users against Salesforce using OpenID Connect. Which result should appear in integration acceptance evidence?
- Employees authenticate with Salesforce and access the portal through validated Salesforce-signed assertions.
- Each external app receives assertions or tokens intended specifically for its own client.
- The dashboard accepts validated Salesforce user identity and enforces its own authorization policy.
- The mobile application receives only necessary authenticated identity data and access permissions.
Explanation
Correct Answer
C:Best. The verification target is: The dashboard accepts validated Salesforce user identity and enforces its own authorization policy. It tests whether the chosen approach—Configure Salesforce's supported OpenID Connect issuer/client integration with exact redirect and token claims.—actually resolves the specific finding: The dashboard can validate signed ID tokens and maintain its own app-specific session.
Incorrect Answers
A: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 dashboard can validate signed ID tokens and maintain its own app-specific session. The direct answer here is: The dashboard accepts validated Salesforce user identity and enforces its own authorization policy.
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 dashboard can validate signed ID tokens and maintain its own app-specific session. The direct answer here is: The dashboard accepts validated Salesforce user identity and enforces its own authorization policy.
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 dashboard can validate signed ID tokens and maintain its own app-specific session. The direct answer here is: The dashboard accepts validated Salesforce user identity and enforces its own authorization policy.
Question 365
Suppose the integration design proceeds without correcting this issue: The dashboard can validate signed ID tokens and maintain its own app-specific session. In the environment An external partner dashboard wants to authenticate users against Salesforce using OpenID Connect. What should the risk register emphasize?
- An OAuth API access token is blindly accepted as a signed ID token by the dashboard.
- The cutover creates duplicate external application accounts and loses prior authorization mappings.
- Salesforce is configured only as a relying service provider and never issues the needed assertion.
- One blanket audience value allows an assertion for a low-risk app to unlock a sensitive app.
Explanation
Correct Answer
A:Best. The most direct failure is: An OAuth API access token is blindly accepted as a signed ID token by the dashboard. It is a consequence of the documented condition: The dashboard can validate signed ID tokens and maintain its own app-specific session. A mitigation is: Configure Salesforce's supported OpenID Connect issuer/client integration with exact redirect and token claims.
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 dashboard can validate signed ID tokens and maintain its own app-specific session. The direct answer here is: An OAuth API access token is blindly accepted as a signed ID token by the dashboard.
C: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 dashboard can validate signed ID tokens and maintain its own app-specific session. The direct answer here is: An OAuth API access token is blindly accepted as a signed ID token by the dashboard.
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 dashboard can validate signed ID tokens and maintain its own app-specific session. The direct answer here is: An OAuth API access token is blindly accepted as a signed ID token by the dashboard.
Question 366
Salesforce and its partners face the following situation: A manufacturer is onboarding several third-party apps that should trust Salesforce sign-in. The integration review notes: Each service has its own audience, service-provider metadata and trust configuration. Which architectural step should take priority?
- Remove retired IdP-connected services and review certificates, scope grants and external access logs.
- Design minimal identity claims and scope configuration for the relying application.
- Map account identifiers and configure Salesforce IdP signing, assertion attributes and trusted service providers.
- Register separate connected apps or service providers with correct SAML or OIDC trust and scopes.
Explanation
Correct Answer
D:Best. The most direct action is to register separate connected apps or service providers with correct SAML or OIDC trust and scopes. It is supported by the specific finding that Each service has its own audience, service-provider metadata and trust configuration. The expected acceptance evidence is: Each external app receives assertions or tokens intended specifically for its own client.
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: Each service has its own audience, service-provider metadata and trust configuration. The direct answer here is: Register separate connected apps or service providers with correct SAML or OIDC trust and scopes.
B: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: Each service has its own audience, service-provider metadata and trust configuration. The direct answer here is: Register separate connected apps or service providers with correct SAML or OIDC trust and scopes.
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: Each service has its own audience, service-provider metadata and trust configuration. The direct answer here is: Register separate connected apps or service providers with correct SAML or OIDC trust and scopes.
Question 367
An implementation team investigates this scenario: A manufacturer is onboarding several third-party apps that should trust Salesforce sign-in. Which finding would most directly justify a change to the integration architecture?
- Each service has its own audience, service-provider metadata and trust configuration.
- The portal accepts SAML assertions issued by a trusted identity provider.
- The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes.
- The external application's contract ended but the trusted audience remains in configuration.
Explanation
Correct Answer
A:Best. The decisive observation is: Each service has its own audience, service-provider metadata and trust configuration. This is why the design response should be: Register separate connected apps or service providers with correct SAML or OIDC trust and scopes.
Incorrect Answers
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: Each service has its own audience, service-provider metadata and trust configuration. The direct answer here is: Each service has its own audience, service-provider metadata and trust 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: Each service has its own audience, service-provider metadata and trust configuration. The direct answer here is: Each service has its own audience, service-provider metadata and trust configuration.
D: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: Each service has its own audience, service-provider metadata and trust configuration. The direct answer here is: Each service has its own audience, service-provider metadata and trust configuration.
Question 368
A solution review asks whether this control is effective: Register separate connected apps or service providers with correct SAML or OIDC trust and scopes. The business setting is: A manufacturer is onboarding several third-party apps that should trust Salesforce sign-in. What should a demonstrable successful outcome be?
- Employees authenticate with Salesforce and access the portal through validated Salesforce-signed assertions.
- Approved managed sessions gain intended access while untrusted sessions are challenged or blocked.
- The dashboard accepts validated Salesforce user identity and enforces its own authorization policy.
- Each external app receives assertions or tokens intended specifically for its own client.
Explanation
Correct Answer
D:Best. The verification target is: Each external app receives assertions or tokens intended specifically for its own client. It tests whether the chosen approach—Register separate connected apps or service providers with correct SAML or OIDC trust and scopes.—actually resolves the specific finding: Each service has its own audience, service-provider metadata and trust configuration.
Incorrect Answers
A: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: Each service has its own audience, service-provider metadata and trust configuration. The direct answer here is: Each external app receives assertions or tokens intended specifically for its own client.
B:Not best for this scenario. This option is associated with another type of requirement: A corporate mobile app must access Salesforce but only when installed on managed and approved devices. Its relevant condition is: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. The present case instead turns on: Each service has its own audience, service-provider metadata and trust configuration. The direct answer here is: Each external app receives assertions or tokens intended specifically for its own client.
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: Each service has its own audience, service-provider metadata and trust configuration. The direct answer here is: Each external app receives assertions or tokens intended specifically for its own client.
Question 369
A Salesforce integration initiative faces this situation: A manufacturer is onboarding several third-party apps that should trust Salesforce sign-in. The critical observation is: Each service has its own audience, service-provider metadata and trust configuration. What failure is most likely if it is ignored?
- The cutover creates duplicate external application accounts and loses prior authorization mappings.
- One blanket audience value allows an assertion for a low-risk app to unlock a sensitive app.
- Excessive claims disclose internal user fields to an external app without business justification.
- A former partner continues using an abandoned federation relationship after offboarding.
Explanation
Correct Answer
B:Best. The most direct failure is: One blanket audience value allows an assertion for a low-risk app to unlock a sensitive app. It is a consequence of the documented condition: Each service has its own audience, service-provider metadata and trust configuration. A mitigation is: Register separate connected apps or service providers with correct SAML or OIDC trust and scopes.
Incorrect Answers
A: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: Each service has its own audience, service-provider metadata and trust configuration. The direct answer here is: One blanket audience value allows an assertion for a low-risk app to unlock a sensitive app.
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: Each service has its own audience, service-provider metadata and trust configuration. The direct answer here is: One blanket audience value allows an assertion for a low-risk app to unlock a sensitive app.
D: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: Each service has its own audience, service-provider metadata and trust configuration. The direct answer here is: One blanket audience value allows an assertion for a low-risk app to unlock a sensitive app.
Question 370
An integration architect receives this requirement: A payroll platform consumes Salesforce-issued SAML assertions and requires a certificate rollover. A technical discovery also finds: The relying party still trusts an old Salesforce IdP signing certificate. Which response most directly addresses the present constraint?
- Remove retired IdP-connected services and review certificates, scope grants and external access logs.
- Map account identifiers and configure Salesforce IdP signing, assertion attributes and trusted service providers.
- Coordinate Salesforce IdP signing-key rotation and update the external service provider trust metadata.
- Configure Salesforce's supported OpenID Connect issuer/client integration with exact redirect and token claims.
Explanation
Correct Answer
C:Best. The most direct action is to coordinate Salesforce IdP signing-key rotation and update the external service provider trust metadata. It is supported by the specific finding that the relying party still trusts an old Salesforce IdP signing certificate. The expected acceptance evidence is: Payroll validates the new assertions while unsupported older signing keys are retired safely.
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 relying party still trusts an old Salesforce IdP signing certificate. The direct answer here is: Coordinate Salesforce IdP signing-key rotation and update the external service provider trust metadata.
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 relying party still trusts an old Salesforce IdP signing certificate. The direct answer here is: Coordinate Salesforce IdP signing-key rotation and update the external service provider trust metadata.
D: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 relying party still trusts an old Salesforce IdP signing certificate. The direct answer here is: Coordinate Salesforce IdP signing-key rotation and update the external service provider trust metadata.