Salesforce Certified Platform Identity and Access Management Architect Practice Test 38
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.
Question 371
Consider the following hypothetical Salesforce initiative: A payroll platform consumes Salesforce-issued SAML assertions and requires a certificate rollover. Which evidence would most strongly explain the current integration weakness?
- The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes.
- The portal accepts SAML assertions issued by a trusted identity provider.
- The relying party still trusts an old Salesforce IdP signing certificate.
- User subject identifiers and service-provider audience settings differ from the old federation provider.
Explanation
Correct Answer
C:Best. The decisive observation is: The relying party still trusts an old Salesforce IdP signing certificate. This is why the design response should be: Coordinate Salesforce IdP signing-key rotation and update the external service provider trust metadata.
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 relying party still trusts an old Salesforce IdP signing certificate. The direct answer here is: The relying party still trusts an old Salesforce IdP signing certificate.
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 relying party still trusts an old Salesforce IdP signing certificate. The direct answer here is: The relying party still trusts an old Salesforce IdP signing certificate.
D: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: The relying party still trusts an old Salesforce IdP signing certificate.
Question 372
Review this change: Coordinate Salesforce IdP signing-key rotation and update the external service provider trust metadata. It addresses a project where A payroll platform consumes Salesforce-issued SAML assertions and requires a certificate rollover. Which result should appear in integration acceptance evidence?
- Unapproved retired relying parties can no longer request valid identity assertions.
- Employees authenticate with Salesforce and access the portal through validated Salesforce-signed assertions.
- The mobile application receives only necessary authenticated identity data and access permissions.
- Payroll validates the new assertions while unsupported older signing keys are retired safely.
Explanation
Correct Answer
D:Best. The verification target is: Payroll validates the new assertions while unsupported older signing keys are retired safely. It tests whether the chosen approach—Coordinate Salesforce IdP signing-key rotation and update the external service provider trust metadata.—actually resolves the specific finding: The relying party still trusts an old Salesforce IdP signing certificate.
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: Payroll validates the new assertions while unsupported older signing keys are retired safely.
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 relying party still trusts an old Salesforce IdP signing certificate. The direct answer here is: Payroll validates the new assertions while unsupported older signing keys are retired safely.
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 relying party still trusts an old Salesforce IdP signing certificate. The direct answer here is: Payroll validates the new assertions while unsupported older signing keys are retired safely.
Question 373
Suppose the integration design proceeds without correcting this issue: The relying party still trusts an old Salesforce IdP signing certificate. In the environment A payroll platform consumes Salesforce-issued SAML assertions and requires a certificate rollover. What should the risk register emphasize?
- Salesforce is configured only as a relying service provider and never issues the needed assertion.
- Excessive claims disclose internal user fields to an external app without business justification.
- The payroll login fails for all users after an uncoordinated certificate renewal.
- A former partner continues using an abandoned federation relationship after offboarding.
Explanation
Correct Answer
C:Best. The most direct failure is: The payroll login fails for all users after an uncoordinated certificate renewal. It is a consequence of the documented condition: The relying party still trusts an old Salesforce IdP signing certificate. A mitigation is: Coordinate Salesforce IdP signing-key rotation and update the external service provider trust metadata.
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 relying party still trusts an old Salesforce IdP signing certificate. The direct answer here is: The payroll login fails for all users after an uncoordinated certificate renewal.
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 relying party still trusts an old Salesforce IdP signing certificate. The direct answer here is: The payroll login fails for all users after an uncoordinated certificate renewal.
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 relying party still trusts an old Salesforce IdP signing certificate. The direct answer here is: The payroll login fails for all users after an uncoordinated certificate renewal.
Question 374
An integration architect receives this requirement: An acquired company wants to move external application login from a vendor IdP to Salesforce identity. A technical discovery also finds: User subject identifiers and service-provider audience settings differ from the old federation provider. Which response most directly addresses the present constraint?
- Map account identifiers and configure Salesforce IdP signing, assertion attributes and trusted service providers.
- Configure Salesforce's supported OpenID Connect issuer/client integration with exact redirect and token claims.
- Register separate connected apps or service providers with correct SAML or OIDC trust and scopes.
- Use a supported JWT bearer flow with signed assertions and a dedicated approved integration user.
Explanation
Correct Answer
A:Best. The most direct action is to map account identifiers and configure Salesforce IdP signing, assertion attributes and trusted service providers. It is supported by the specific finding that User subject identifiers and service-provider audience settings differ from the old federation provider. The expected acceptance evidence is: External apps match existing users to stable identity records after the migration.
Incorrect Answers
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: User subject identifiers and service-provider audience settings differ from the old federation provider. The direct answer here is: Map account identifiers and configure Salesforce IdP signing, assertion attributes and trusted service providers.
C: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: User subject identifiers and service-provider audience settings differ from the old federation provider. The direct answer here is: Map account identifiers and configure Salesforce IdP signing, assertion attributes and trusted service providers.
D:Not best for this scenario. This option is associated with another type of requirement: A headless scheduled analytics job reads Salesforce records nightly without a person present. Its relevant condition is: The service holds an approved signing certificate and the Salesforce client app is preauthorized. The present case instead turns on: User subject identifiers and service-provider audience settings differ from the old federation provider. The direct answer here is: Map account identifiers and configure Salesforce IdP signing, assertion attributes and trusted service providers.
Question 375
Consider the following hypothetical Salesforce initiative: An acquired company wants to move external application login from a vendor IdP to Salesforce identity. Which evidence would most strongly explain the current integration weakness?
- 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 dashboard can validate signed ID tokens and maintain its own app-specific session.
- The relying party still trusts an old Salesforce IdP signing certificate.
Explanation
Correct Answer
B:Best. The decisive observation is: User subject identifiers and service-provider audience settings differ from the old federation provider. This is why the design response should be: Map account identifiers and configure Salesforce IdP signing, assertion attributes and trusted service providers.
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: User subject identifiers and service-provider audience settings differ from the old federation provider. The direct answer here is: User subject identifiers and service-provider audience settings differ from the old federation provider.
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: User subject identifiers and service-provider audience settings differ from the old federation provider. The direct answer here is: User subject identifiers and service-provider audience settings differ from the old federation provider.
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: User subject identifiers and service-provider audience settings differ from the old federation provider. The direct answer here is: User subject identifiers and service-provider audience settings differ from the old federation provider.
Question 376
Review this change: Map account identifiers and configure Salesforce IdP signing, assertion attributes and trusted service providers. It addresses a project where An acquired company wants to move external application login from a vendor IdP to Salesforce identity. Which result should appear in integration acceptance evidence?
- Employees authenticate with Salesforce and access the portal through validated Salesforce-signed assertions.
- The mobile application receives only necessary authenticated identity data and access permissions.
- External apps match existing users to stable identity records after the migration.
- Unapproved retired relying parties can no longer request valid identity assertions.
Explanation
Correct Answer
C:Best. The verification target is: External apps match existing users to stable identity records after the migration. It tests whether the chosen approach—Map account identifiers and configure Salesforce IdP signing, assertion attributes and trusted service providers.—actually resolves the specific finding: User subject identifiers and service-provider audience settings differ from the old federation provider.
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: User subject identifiers and service-provider audience settings differ from the old federation provider. The direct answer here is: External apps match existing users to stable identity records after the migration.
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: User subject identifiers and service-provider audience settings differ from the old federation provider. The direct answer here is: External apps match existing users to stable identity records after the migration.
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: User subject identifiers and service-provider audience settings differ from the old federation provider. The direct answer here is: External apps match existing users to stable identity records after the migration.
Question 377
Suppose the integration design proceeds without correcting this issue: User subject identifiers and service-provider audience settings differ from the old federation provider. In the environment An acquired company wants to move external application login from a vendor IdP to Salesforce identity. 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.
- Excessive claims disclose internal user fields to an external app without business justification.
Explanation
Correct Answer
B:Best. The most direct failure is: The cutover creates duplicate external application accounts and loses prior authorization mappings. It is a consequence of the documented condition: User subject identifiers and service-provider audience settings differ from the old federation provider. A mitigation is: Map account identifiers and configure Salesforce IdP signing, assertion attributes and trusted service providers.
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: User subject identifiers and service-provider audience settings differ from the old federation provider. The direct answer here is: The cutover creates duplicate external application accounts and loses prior authorization mappings.
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: User subject identifiers and service-provider audience settings differ from the old federation provider. The direct answer here is: The cutover creates duplicate external application accounts and loses prior authorization mappings.
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: User subject identifiers and service-provider audience settings differ from the old federation provider. The direct answer here is: The cutover creates duplicate external application accounts and loses prior authorization mappings.
Question 378
An architecture board reviews a proposed Salesforce integration. Context: A company publishes a Salesforce-backed account portal that issues identity to a customer mobile application. Finding: The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes. Which decision best resolves the concern?
- Configure Salesforce's supported OpenID Connect issuer/client integration with exact redirect and token claims.
- 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.
- 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 design minimal identity claims and scope configuration for the relying application. It is supported by the specific finding that the mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes. The expected acceptance evidence is: The mobile application receives only necessary authenticated identity data and access permissions.
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 mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes. The direct answer here is: Design minimal identity claims and scope configuration for the relying application.
B: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: Design minimal identity claims and scope configuration for the relying application.
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 mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes. The direct answer here is: Design minimal identity claims and scope configuration for the relying application.
Question 379
A design workshop describes this environment: A company publishes a Salesforce-backed account portal that issues identity to a customer mobile application. Which concrete observation should be documented as the most decisive issue?
- The relying party still trusts an old Salesforce IdP signing certificate.
- The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes.
- The portal accepts SAML assertions issued by a trusted identity provider.
- Each service has its own audience, service-provider metadata and trust configuration.
Explanation
Correct Answer
B:Best. The decisive observation is: The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes. This is why the design response should be: 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 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 mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes. The direct answer here is: The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes.
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 mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes. The direct answer here is: The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes.
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 mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes. The direct answer here is: The mobile client needs specific OIDC claims but should not learn internal Salesforce administrative attributes.
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?
- Unapproved retired relying parties can no longer request valid identity assertions.
- External apps match existing users to stable identity records after the migration.
- The mobile application receives only necessary authenticated identity data and access permissions.
- 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.