Salesforce Certified Platform Identity and Access Management Architect Practice Test 7
Question 60
Salesforce and its partners face the following situation: A distributed company adds an identity broker between an external IdP and Salesforce. The integration review notes: The proposed broker forwards assertions without documenting which component signs or verifies them. Which architectural step should take priority?
- Review and remove obsolete trusted IdP and certificate entries after migration and access testing.
- Require individually attributable administrative identities with recorded configuration changes and audit events.
- Define trust anchors, metadata exchange, signing ownership and audience restrictions at each hop.
- Validate assertion signatures, issuer, audience, destination and configured trusted IdP relationship.
Explanation
Correct Answer
C:Best. The most direct action is to define trust anchors, metadata exchange, signing ownership and audience restrictions at each hop. It is supported by the specific finding that the proposed broker forwards assertions without documenting which component signs or verifies them. The expected acceptance evidence is: The broker and Salesforce validate explicit issuer and certificate relationships for each federation step.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Security analysts discover an old Salesforce SAML configuration still trusts a retired partner certificate. Its relevant condition is: The partner relationship ended, but the IdP metadata and signing key remain active. The present case instead turns on: The proposed broker forwards assertions without documenting which component signs or verifies them. The direct answer here is: Define trust anchors, metadata exchange, signing ownership and audience restrictions at each hop.
B:Not best for this scenario. This option is associated with another type of requirement: An audit team investigates who changed a connected application's OAuth policy during an incident. Its relevant condition is: Several administrators share a single service account and change logs cannot attribute the edit to one person. The present case instead turns on: The proposed broker forwards assertions without documenting which component signs or verifies them. The direct answer here is: Define trust anchors, metadata exchange, signing ownership and audience restrictions at each hop.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A retail brand wants only its approved partner identity provider to authenticate users into Salesforce. Its relevant condition is: An incoming assertion names the right user but has an unexpected issuer and audience value. The present case instead turns on: The proposed broker forwards assertions without documenting which component signs or verifies them. The direct answer here is: Define trust anchors, metadata exchange, signing ownership and audience restrictions at each hop.
Question 61
An implementation team investigates this scenario: A distributed company adds an identity broker between an external IdP and Salesforce. Which finding would most directly justify a change to the integration architecture?
- The partner relationship ended, but the IdP metadata and signing key remain active.
- The app checks the user email claim but ignores the token signature, issuer and nonce.
- The same SAML assertion is sent to both relying parties with no service-specific recipient restriction.
- The proposed broker forwards assertions without documenting which component signs or verifies them.
Explanation
Correct Answer
D:Best. The decisive observation is: The proposed broker forwards assertions without documenting which component signs or verifies them. This is why the design response should be: Define trust anchors, metadata exchange, signing ownership and audience restrictions at each hop.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Security analysts discover an old Salesforce SAML configuration still trusts a retired partner certificate. Its relevant condition is: The partner relationship ended, but the IdP metadata and signing key remain active. The present case instead turns on: The proposed broker forwards assertions without documenting which component signs or verifies them. The direct answer here is: The proposed broker forwards assertions without documenting which component signs or verifies them.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner SaaS app signs in users using Salesforce as its OpenID Connect identity provider. Its relevant condition is: The app checks the user email claim but ignores the token signature, issuer and nonce. The present case instead turns on: The proposed broker forwards assertions without documenting which component signs or verifies them. The direct answer here is: The proposed broker forwards assertions without documenting which component signs or verifies them.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise adds two service providers that share one Salesforce identity provider. Its relevant condition is: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. The present case instead turns on: The proposed broker forwards assertions without documenting which component signs or verifies them. The direct answer here is: The proposed broker forwards assertions without documenting which component signs or verifies them.
Question 62
A solution review asks whether this control is effective: Define trust anchors, metadata exchange, signing ownership and audience restrictions at each hop. The business setting is: A distributed company adds an identity broker between an external IdP and Salesforce. What should a demonstrable successful outcome be?
- Retired federation relationships no longer provide a valid route to Salesforce authentication.
- Assertions signed by the approved IdP certificate succeed and invalid signatures are rejected.
- Only Salesforce-issued identity claims intended for this client establish user authentication.
- The broker and Salesforce validate explicit issuer and certificate relationships for each federation step.
Explanation
Correct Answer
D:Best. The verification target is: The broker and Salesforce validate explicit issuer and certificate relationships for each federation step. It tests whether the chosen approach—Define trust anchors, metadata exchange, signing ownership and audience restrictions at each hop.—actually resolves the specific finding: The proposed broker forwards assertions without documenting which component signs or verifies them.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Security analysts discover an old Salesforce SAML configuration still trusts a retired partner certificate. Its relevant condition is: The partner relationship ended, but the IdP metadata and signing key remain active. The present case instead turns on: The proposed broker forwards assertions without documenting which component signs or verifies them. The direct answer here is: The broker and Salesforce validate explicit issuer and certificate relationships for each federation step.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A corporate IdP rotates its SAML signing certificate before a scheduled release to Salesforce. Its relevant condition is: Salesforce still trusts the prior public certificate and the assertions now fail signature verification. The present case instead turns on: The proposed broker forwards assertions without documenting which component signs or verifies them. The direct answer here is: The broker and Salesforce validate explicit issuer and certificate relationships for each federation step.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner SaaS app signs in users using Salesforce as its OpenID Connect identity provider. Its relevant condition is: The app checks the user email claim but ignores the token signature, issuer and nonce. The present case instead turns on: The proposed broker forwards assertions without documenting which component signs or verifies them. The direct answer here is: The broker and Salesforce validate explicit issuer and certificate relationships for each federation step.
Question 63
A Salesforce integration initiative faces this situation: A distributed company adds an identity broker between an external IdP and Salesforce. The critical observation is: The proposed broker forwards assertions without documenting which component signs or verifies them. What failure is most likely if it is ignored?
- The broker accidentally launders untrusted identity assertions from an unrelated IdP.
- Uncontrolled automatic registration creates redundant user records and inconsistent contact ownership.
- A forged ID token or replay from another relying party is mistakenly trusted.
- All users lose federated access because the service provider trusts an expired signing key.
Explanation
Correct Answer
A:Best. The most direct failure is: The broker accidentally launders untrusted identity assertions from an unrelated IdP. It is a consequence of the documented condition: The proposed broker forwards assertions without documenting which component signs or verifies them. A mitigation is: Define trust anchors, metadata exchange, signing ownership and audience restrictions at each hop.
Incorrect Answers
B:Not best for this scenario. This option is associated with another type of requirement: A public membership site expects tens of thousands of new identity records each month. Its relevant condition is: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. The present case instead turns on: The proposed broker forwards assertions without documenting which component signs or verifies them. The direct answer here is: The broker accidentally launders untrusted identity assertions from an unrelated IdP.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner SaaS app signs in users using Salesforce as its OpenID Connect identity provider. Its relevant condition is: The app checks the user email claim but ignores the token signature, issuer and nonce. The present case instead turns on: The proposed broker forwards assertions without documenting which component signs or verifies them. The direct answer here is: The broker accidentally launders untrusted identity assertions from an unrelated IdP.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A corporate IdP rotates its SAML signing certificate before a scheduled release to Salesforce. Its relevant condition is: Salesforce still trusts the prior public certificate and the assertions now fail signature verification. The present case instead turns on: The proposed broker forwards assertions without documenting which component signs or verifies them. The direct answer here is: The broker accidentally launders untrusted identity assertions from an unrelated IdP.
Question 64
Salesforce and its partners face the following situation: An enterprise adds two service providers that share one Salesforce identity provider. The integration review notes: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. Which architectural step should take priority?
- Use service-provider-specific entity IDs, ACS destinations, audience and replay controls.
- Define trust anchors, metadata exchange, signing ownership and audience restrictions at each hop.
- Validate assertion signatures, issuer, audience, destination and configured trusted IdP relationship.
- Review and remove obsolete trusted IdP and certificate entries after migration and access testing.
Explanation
Correct Answer
A:Best. The most direct action is to use service-provider-specific entity IDs, ACS destinations, audience and replay controls. It is supported by the specific finding that the same SAML assertion is sent to both relying parties with no service-specific recipient restriction. The expected acceptance evidence is: Each relying party accepts assertions only for its own registered trust configuration.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A distributed company adds an identity broker between an external IdP and Salesforce. Its relevant condition is: The proposed broker forwards assertions without documenting which component signs or verifies them. The present case instead turns on: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. The direct answer here is: Use service-provider-specific entity IDs, ACS destinations, audience and replay controls.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A retail brand wants only its approved partner identity provider to authenticate users into Salesforce. Its relevant condition is: An incoming assertion names the right user but has an unexpected issuer and audience value. The present case instead turns on: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. The direct answer here is: Use service-provider-specific entity IDs, ACS destinations, audience and replay controls.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Security analysts discover an old Salesforce SAML configuration still trusts a retired partner certificate. Its relevant condition is: The partner relationship ended, but the IdP metadata and signing key remain active. The present case instead turns on: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. The direct answer here is: Use service-provider-specific entity IDs, ACS destinations, audience and replay controls.
Question 65
An implementation team investigates this scenario: An enterprise adds two service providers that share one Salesforce identity provider. Which finding would most directly justify a change to the integration architecture?
- The proposed broker forwards assertions without documenting which component signs or verifies them.
- Salesforce still trusts the prior public certificate and the assertions now fail signature verification.
- The same SAML assertion is sent to both relying parties with no service-specific recipient restriction.
- The app checks the user email claim but ignores the token signature, issuer and nonce.
Explanation
Correct Answer
C:Best. The decisive observation is: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. This is why the design response should be: Use service-provider-specific entity IDs, ACS destinations, audience and replay controls.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A distributed company adds an identity broker between an external IdP and Salesforce. Its relevant condition is: The proposed broker forwards assertions without documenting which component signs or verifies them. The present case instead turns on: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. The direct answer here is: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A corporate IdP rotates its SAML signing certificate before a scheduled release to Salesforce. Its relevant condition is: Salesforce still trusts the prior public certificate and the assertions now fail signature verification. The present case instead turns on: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. The direct answer here is: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner SaaS app signs in users using Salesforce as its OpenID Connect identity provider. Its relevant condition is: The app checks the user email claim but ignores the token signature, issuer and nonce. The present case instead turns on: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. The direct answer here is: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction.
Question 66
A solution review asks whether this control is effective: Use service-provider-specific entity IDs, ACS destinations, audience and replay controls. The business setting is: An enterprise adds two service providers that share one Salesforce identity provider. What should a demonstrable successful outcome be?
- Salesforce accepts only assertions addressed to its service and signed by the configured partner.
- Retired federation relationships no longer provide a valid route to Salesforce authentication.
- Assertions signed by the approved IdP certificate succeed and invalid signatures are rejected.
- Each relying party accepts assertions only for its own registered trust configuration.
Explanation
Correct Answer
D:Best. The verification target is: Each relying party accepts assertions only for its own registered trust configuration. It tests whether the chosen approach—Use service-provider-specific entity IDs, ACS destinations, audience and replay controls.—actually resolves the specific finding: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A retail brand wants only its approved partner identity provider to authenticate users into Salesforce. Its relevant condition is: An incoming assertion names the right user but has an unexpected issuer and audience value. The present case instead turns on: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. The direct answer here is: Each relying party accepts assertions only for its own registered trust configuration.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Security analysts discover an old Salesforce SAML configuration still trusts a retired partner certificate. Its relevant condition is: The partner relationship ended, but the IdP metadata and signing key remain active. The present case instead turns on: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. The direct answer here is: Each relying party accepts assertions only for its own registered trust configuration.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A corporate IdP rotates its SAML signing certificate before a scheduled release to Salesforce. Its relevant condition is: Salesforce still trusts the prior public certificate and the assertions now fail signature verification. The present case instead turns on: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. The direct answer here is: Each relying party accepts assertions only for its own registered trust configuration.
Question 67
A Salesforce integration initiative faces this situation: An enterprise adds two service providers that share one Salesforce identity provider. The critical observation is: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. What failure is most likely if it is ignored?
- A forged ID token or replay from another relying party is mistakenly trusted.
- A captured assertion for one application opens an unrelated service.
- All users lose federated access because the service provider trusts an expired signing key.
- A former partner uses stale trust metadata to keep signing accepted login assertions.
Explanation
Correct Answer
B:Best. The most direct failure is: A captured assertion for one application opens an unrelated service. It is a consequence of the documented condition: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. A mitigation is: Use service-provider-specific entity IDs, ACS destinations, audience and replay controls.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner SaaS app signs in users using Salesforce as its OpenID Connect identity provider. Its relevant condition is: The app checks the user email claim but ignores the token signature, issuer and nonce. The present case instead turns on: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. The direct answer here is: A captured assertion for one application opens an unrelated service.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A corporate IdP rotates its SAML signing certificate before a scheduled release to Salesforce. Its relevant condition is: Salesforce still trusts the prior public certificate and the assertions now fail signature verification. The present case instead turns on: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. The direct answer here is: A captured assertion for one application opens an unrelated service.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Security analysts discover an old Salesforce SAML configuration still trusts a retired partner certificate. Its relevant condition is: The partner relationship ended, but the IdP metadata and signing key remain active. The present case instead turns on: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. The direct answer here is: A captured assertion for one application opens an unrelated service.
Question 68
An architecture board reviews a proposed Salesforce integration. Context: Security analysts discover an old Salesforce SAML configuration still trusts a retired partner certificate. Finding: The partner relationship ended, but the IdP metadata and signing key remain active. Which decision best resolves the concern?
- Validate assertion signatures, issuer, audience, destination and configured trusted IdP relationship.
- Use service-provider-specific entity IDs, ACS destinations, audience and replay controls.
- Inspect JWT signature, audience, issuer, subject, expiry and prior authorization settings.
- Review and remove obsolete trusted IdP and certificate entries after migration and access testing.
Explanation
Correct Answer
D:Best. The most direct action is to review and remove obsolete trusted IdP and certificate entries after migration and access testing. It is supported by the specific finding that the partner relationship ended, but the IdP metadata and signing key remain active. The expected acceptance evidence is: Retired federation relationships no longer provide a valid route to Salesforce authentication.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A retail brand wants only its approved partner identity provider to authenticate users into Salesforce. Its relevant condition is: An incoming assertion names the right user but has an unexpected issuer and audience value. The present case instead turns on: The partner relationship ended, but the IdP metadata and signing key remain active. The direct answer here is: Review and remove obsolete trusted IdP and certificate entries after migration and access testing.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise adds two service providers that share one Salesforce identity provider. Its relevant condition is: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. The present case instead turns on: The partner relationship ended, but the IdP metadata and signing key remain active. The direct answer here is: Review and remove obsolete trusted IdP and certificate entries after migration and access testing.
C:Not best for this scenario. This option is associated with another type of requirement: A server-to-server integration fails with invalid_grant after a JWT-based OAuth rollout. Its relevant condition is: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. The present case instead turns on: The partner relationship ended, but the IdP metadata and signing key remain active. The direct answer here is: Review and remove obsolete trusted IdP and certificate entries after migration and access testing.
Question 69
A design workshop describes this environment: Security analysts discover an old Salesforce SAML configuration still trusts a retired partner certificate. Which concrete observation should be documented as the most decisive issue?
- The partner relationship ended, but the IdP metadata and signing key remain active.
- An incoming assertion names the right user but has an unexpected issuer and audience value.
- Salesforce still trusts the prior public certificate and the assertions now fail signature verification.
- The same SAML assertion is sent to both relying parties with no service-specific recipient restriction.
Explanation
Correct Answer
A:Best. The decisive observation is: The partner relationship ended, but the IdP metadata and signing key remain active. This is why the design response should be: Review and remove obsolete trusted IdP and certificate entries after migration and access testing.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A retail brand wants only its approved partner identity provider to authenticate users into Salesforce. Its relevant condition is: An incoming assertion names the right user but has an unexpected issuer and audience value. The present case instead turns on: The partner relationship ended, but the IdP metadata and signing key remain active. The direct answer here is: The partner relationship ended, but the IdP metadata and signing key remain active.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A corporate IdP rotates its SAML signing certificate before a scheduled release to Salesforce. Its relevant condition is: Salesforce still trusts the prior public certificate and the assertions now fail signature verification. The present case instead turns on: The partner relationship ended, but the IdP metadata and signing key remain active. The direct answer here is: The partner relationship ended, but the IdP metadata and signing key remain active.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise adds two service providers that share one Salesforce identity provider. Its relevant condition is: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. The present case instead turns on: The partner relationship ended, but the IdP metadata and signing key remain active. The direct answer here is: The partner relationship ended, but the IdP metadata and signing key remain active.
Question 70
An architect must create an acceptance test after choosing: Review and remove obsolete trusted IdP and certificate entries after migration and access testing. For the situation Security analysts discover an old Salesforce SAML configuration still trusts a retired partner certificate. Which result most directly proves success?
- Each relying party accepts assertions only for its own registered trust configuration.
- Only Salesforce-issued identity claims intended for this client establish user authentication.
- Retired federation relationships no longer provide a valid route to Salesforce authentication.
- Salesforce accepts only assertions addressed to its service and signed by the configured partner.
Explanation
Correct Answer
C:Best. The verification target is: Retired federation relationships no longer provide a valid route to Salesforce authentication. It tests whether the chosen approach—Review and remove obsolete trusted IdP and certificate entries after migration and access testing.—actually resolves the specific finding: The partner relationship ended, but the IdP metadata and signing key remain active.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise adds two service providers that share one Salesforce identity provider. Its relevant condition is: The same SAML assertion is sent to both relying parties with no service-specific recipient restriction. The present case instead turns on: The partner relationship ended, but the IdP metadata and signing key remain active. The direct answer here is: Retired federation relationships no longer provide a valid route to Salesforce authentication.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner SaaS app signs in users using Salesforce as its OpenID Connect identity provider. Its relevant condition is: The app checks the user email claim but ignores the token signature, issuer and nonce. The present case instead turns on: The partner relationship ended, but the IdP metadata and signing key remain active. The direct answer here is: Retired federation relationships no longer provide a valid route to Salesforce authentication.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A retail brand wants only its approved partner identity provider to authenticate users into Salesforce. Its relevant condition is: An incoming assertion names the right user but has an unexpected issuer and audience value. The present case instead turns on: The partner relationship ended, but the IdP metadata and signing key remain active. The direct answer here is: Retired federation relationships no longer provide a valid route to Salesforce authentication.