Salesforce Certified Platform Identity and Access Management Architect Practice Test 11
Question 100
An architecture board reviews a proposed Salesforce integration. Context: A group of employees receives intermittent SAML signature failures after an identity-provider certificate rollover. Finding: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. Which decision best resolves the concern?
- Compare the active signature certificate with trusted metadata, then rotate without weakening signature checks.
- Compare both initiation paths, relay destination and SAML login history before changing access policies.
- Validate ID-token signature and issuer, client audience, freshness and nonce against Salesforce configuration.
- Inspect the SAML assertion and Salesforce SSO configuration; correct entity IDs and audience mapping.
Explanation
Correct Answer
A:Best. The most direct action is to compare the active signature certificate with trusted metadata, then rotate without weakening signature checks. It is supported by the specific finding that the IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The expected acceptance evidence is: Login succeeds across affected orgs with the intended trusted signing certificate.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner reports sporadic SSO failures only when opening Salesforce from a bookmarked application link. Its relevant condition is: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The present case instead turns on: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The direct answer here is: Compare the active signature certificate with trusted metadata, then rotate without weakening signature checks.
C:Not best for this scenario. This option is associated with another type of requirement: 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 IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The direct answer here is: Compare the active signature certificate with trusted metadata, then rotate without weakening signature checks.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Salesforce rejects a newly deployed SAML integration with an invalid assertion audience error. Its relevant condition is: The IdP uses a destination string copied from a sandbox while the user is signing into production. The present case instead turns on: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The direct answer here is: Compare the active signature certificate with trusted metadata, then rotate without weakening signature checks.
Question 101
A design workshop describes this environment: A group of employees receives intermittent SAML signature failures after an identity-provider certificate rollover. Which concrete observation should be documented as the most decisive issue?
- The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState.
- The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org.
- The IdP sends a new employee email address while Salesforce user matching uses Federation ID.
- The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs.
Explanation
Correct Answer
D:Best. The decisive observation is: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. This is why the design response should be: Compare the active signature certificate with trusted metadata, then rotate without weakening signature checks.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner reports sporadic SSO failures only when opening Salesforce from a bookmarked application link. Its relevant condition is: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The present case instead turns on: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The direct answer here is: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: 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 IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The direct answer here is: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A browser SSO login returns a valid assertion but Salesforce cannot find the intended existing user. Its relevant condition is: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The present case instead turns on: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The direct answer here is: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs.
Question 102
An architect must create an acceptance test after choosing: Compare the active signature certificate with trusted metadata, then rotate without weakening signature checks. For the situation A group of employees receives intermittent SAML signature failures after an identity-provider certificate rollover. Which result most directly proves success?
- Approved entry points direct the user to the expected Salesforce page with valid authentication.
- The registered client completes its authorization flow only at an approved callback URL.
- Login succeeds across affected orgs with the intended trusted signing certificate.
- An assertion targeted at the production service provider is accepted after proper validation.
Explanation
Correct Answer
C:Best. The verification target is: Login succeeds across affected orgs with the intended trusted signing certificate. It tests whether the chosen approach—Compare the active signature certificate with trusted metadata, then rotate without weakening signature checks.—actually resolves the specific finding: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner reports sporadic SSO failures only when opening Salesforce from a bookmarked application link. Its relevant condition is: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The present case instead turns on: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The direct answer here is: Login succeeds across affected orgs with the intended trusted signing certificate.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An OAuth client receives invalid_redirect_uri after its administrator migrates from test to production. Its relevant condition is: The callback URL in the authorization request does not match the registered app redirect configuration. The present case instead turns on: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The direct answer here is: Login succeeds across affected orgs with the intended trusted signing certificate.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Salesforce rejects a newly deployed SAML integration with an invalid assertion audience error. Its relevant condition is: The IdP uses a destination string copied from a sandbox while the user is signing into production. The present case instead turns on: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The direct answer here is: Login succeeds across affected orgs with the intended trusted signing certificate.
Question 103
An incident scenario concerns this architecture: A group of employees receives intermittent SAML signature failures after an identity-provider certificate rollover. The team has discovered: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. Which project risk requires explicit mitigation?
- An outdated certificate configuration causes broad federation downtime.
- A misrouted RelayState is wrongly diagnosed as a user-permission problem.
- Allowing arbitrary redirect URIs exposes the authorization result to attacker-controlled endpoints.
- Admins disable assertion validation instead of correcting the environment mismatch.
Explanation
Correct Answer
A:Best. The most direct failure is: An outdated certificate configuration causes broad federation downtime. It is a consequence of the documented condition: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. A mitigation is: Compare the active signature certificate with trusted metadata, then rotate without weakening signature checks.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner reports sporadic SSO failures only when opening Salesforce from a bookmarked application link. Its relevant condition is: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The present case instead turns on: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The direct answer here is: An outdated certificate configuration causes broad federation downtime.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An OAuth client receives invalid_redirect_uri after its administrator migrates from test to production. Its relevant condition is: The callback URL in the authorization request does not match the registered app redirect configuration. The present case instead turns on: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The direct answer here is: An outdated certificate configuration causes broad federation downtime.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Salesforce rejects a newly deployed SAML integration with an invalid assertion audience error. Its relevant condition is: The IdP uses a destination string copied from a sandbox while the user is signing into production. The present case instead turns on: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The direct answer here is: An outdated certificate configuration causes broad federation downtime.
Question 104
An integration architect receives this requirement: A browser SSO login returns a valid assertion but Salesforce cannot find the intended existing user. A technical discovery also finds: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. Which response most directly addresses the present constraint?
- Inspect the SAML assertion and Salesforce SSO configuration; correct entity IDs and audience mapping.
- Inspect NameID or federation identifier and user matching, then align immutable account identifiers.
- Correct the client redirect-URI registration and verify exact authorization endpoint and app identity.
- Compare the active signature certificate with trusted metadata, then rotate without weakening signature checks.
Explanation
Correct Answer
B:Best. The most direct action is to inspect NameID or federation identifier and user matching, then align immutable account identifiers. It is supported by the specific finding that the IdP sends a new employee email address while Salesforce user matching uses Federation ID. The expected acceptance evidence is: The assertion maps to the correct existing Salesforce account without accidental user duplication.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Salesforce rejects a newly deployed SAML integration with an invalid assertion audience error. Its relevant condition is: The IdP uses a destination string copied from a sandbox while the user is signing into production. The present case instead turns on: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The direct answer here is: Inspect NameID or federation identifier and user matching, then align immutable account identifiers.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An OAuth client receives invalid_redirect_uri after its administrator migrates from test to production. Its relevant condition is: The callback URL in the authorization request does not match the registered app redirect configuration. The present case instead turns on: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The direct answer here is: Inspect NameID or federation identifier and user matching, then align immutable account identifiers.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A group of employees receives intermittent SAML signature failures after an identity-provider certificate rollover. Its relevant condition is: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The present case instead turns on: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The direct answer here is: Inspect NameID or federation identifier and user matching, then align immutable account identifiers.
Question 105
Consider the following hypothetical Salesforce initiative: A browser SSO login returns a valid assertion but Salesforce cannot find the intended existing user. Which evidence would most strongly explain the current integration weakness?
- The callback URL in the authorization request does not match the registered app redirect configuration.
- The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs.
- The IdP sends a new employee email address while Salesforce user matching uses Federation ID.
- The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState.
Explanation
Correct Answer
C:Best. The decisive observation is: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. This is why the design response should be: Inspect NameID or federation identifier and user matching, then align immutable account identifiers.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An OAuth client receives invalid_redirect_uri after its administrator migrates from test to production. Its relevant condition is: The callback URL in the authorization request does not match the registered app redirect configuration. The present case instead turns on: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The direct answer here is: The IdP sends a new employee email address while Salesforce user matching uses Federation ID.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A group of employees receives intermittent SAML signature failures after an identity-provider certificate rollover. Its relevant condition is: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The present case instead turns on: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The direct answer here is: The IdP sends a new employee email address while Salesforce user matching uses Federation ID.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner reports sporadic SSO failures only when opening Salesforce from a bookmarked application link. Its relevant condition is: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The present case instead turns on: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The direct answer here is: The IdP sends a new employee email address while Salesforce user matching uses Federation ID.
Question 106
Review this change: Inspect NameID or federation identifier and user matching, then align immutable account identifiers. It addresses a project where A browser SSO login returns a valid assertion but Salesforce cannot find the intended existing user. Which result should appear in integration acceptance evidence?
- A correctly signed and scoped assertion receives an access token without password storage.
- The registered client completes its authorization flow only at an approved callback URL.
- Approved entry points direct the user to the expected Salesforce page with valid authentication.
- The assertion maps to the correct existing Salesforce account without accidental user duplication.
Explanation
Correct Answer
D:Best. The verification target is: The assertion maps to the correct existing Salesforce account without accidental user duplication. It tests whether the chosen approach—Inspect NameID or federation identifier and user matching, then align immutable account identifiers.—actually resolves the specific finding: The IdP sends a new employee email address while Salesforce user matching uses Federation ID.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: 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 IdP sends a new employee email address while Salesforce user matching uses Federation ID. The direct answer here is: The assertion maps to the correct existing Salesforce account without accidental user duplication.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An OAuth client receives invalid_redirect_uri after its administrator migrates from test to production. Its relevant condition is: The callback URL in the authorization request does not match the registered app redirect configuration. The present case instead turns on: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The direct answer here is: The assertion maps to the correct existing Salesforce account without accidental user duplication.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner reports sporadic SSO failures only when opening Salesforce from a bookmarked application link. Its relevant condition is: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The present case instead turns on: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The direct answer here is: The assertion maps to the correct existing Salesforce account without accidental user duplication.
Question 107
Suppose the integration design proceeds without correcting this issue: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. In the environment A browser SSO login returns a valid assertion but Salesforce cannot find the intended existing user. What should the risk register emphasize?
- The team disables token checks or embeds human passwords to hide a configuration issue.
- Admins disable assertion validation instead of correcting the environment mismatch.
- A valid employee is repeatedly rejected or provisioned as another identity.
- An outdated certificate configuration causes broad federation downtime.
Explanation
Correct Answer
C:Best. The most direct failure is: A valid employee is repeatedly rejected or provisioned as another identity. It is a consequence of the documented condition: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. A mitigation is: Inspect NameID or federation identifier and user matching, then align immutable account identifiers.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: 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 IdP sends a new employee email address while Salesforce user matching uses Federation ID. The direct answer here is: A valid employee is repeatedly rejected or provisioned as another identity.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Salesforce rejects a newly deployed SAML integration with an invalid assertion audience error. Its relevant condition is: The IdP uses a destination string copied from a sandbox while the user is signing into production. The present case instead turns on: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The direct answer here is: A valid employee is repeatedly rejected or provisioned as another identity.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A group of employees receives intermittent SAML signature failures after an identity-provider certificate rollover. Its relevant condition is: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The present case instead turns on: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The direct answer here is: A valid employee is repeatedly rejected or provisioned as another identity.
Question 108
An architecture board reviews a proposed Salesforce integration. Context: An OAuth client receives invalid_redirect_uri after its administrator migrates from test to production. Finding: The callback URL in the authorization request does not match the registered app redirect configuration. Which decision best resolves the concern?
- Inspect the SAML assertion and Salesforce SSO configuration; correct entity IDs and audience mapping.
- Inspect NameID or federation identifier and user matching, then align immutable account identifiers.
- Inspect JWT signature, audience, issuer, subject, expiry and prior authorization settings.
- Correct the client redirect-URI registration and verify exact authorization endpoint and app identity.
Explanation
Correct Answer
D:Best. The most direct action is to correct the client redirect-URI registration and verify exact authorization endpoint and app identity. It is supported by the specific finding that the callback URL in the authorization request does not match the registered app redirect configuration. The expected acceptance evidence is: The registered client completes its authorization flow only at an approved callback URL.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Salesforce rejects a newly deployed SAML integration with an invalid assertion audience error. Its relevant condition is: The IdP uses a destination string copied from a sandbox while the user is signing into production. The present case instead turns on: The callback URL in the authorization request does not match the registered app redirect configuration. The direct answer here is: Correct the client redirect-URI registration and verify exact authorization endpoint and app identity.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A browser SSO login returns a valid assertion but Salesforce cannot find the intended existing user. Its relevant condition is: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The present case instead turns on: The callback URL in the authorization request does not match the registered app redirect configuration. The direct answer here is: Correct the client redirect-URI registration and verify exact authorization endpoint and app identity.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: 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 callback URL in the authorization request does not match the registered app redirect configuration. The direct answer here is: Correct the client redirect-URI registration and verify exact authorization endpoint and app identity.
Question 109
A design workshop describes this environment: An OAuth client receives invalid_redirect_uri after its administrator migrates from test to production. Which concrete observation should be documented as the most decisive issue?
- The callback URL in the authorization request does not match the registered app redirect configuration.
- The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState.
- The IdP uses a destination string copied from a sandbox while the user is signing into production.
- The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org.
Explanation
Correct Answer
A:Best. The decisive observation is: The callback URL in the authorization request does not match the registered app redirect configuration. This is why the design response should be: Correct the client redirect-URI registration and verify exact authorization endpoint and app identity.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner reports sporadic SSO failures only when opening Salesforce from a bookmarked application link. Its relevant condition is: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The present case instead turns on: The callback URL in the authorization request does not match the registered app redirect configuration. The direct answer here is: The callback URL in the authorization request does not match the registered app redirect configuration.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Salesforce rejects a newly deployed SAML integration with an invalid assertion audience error. Its relevant condition is: The IdP uses a destination string copied from a sandbox while the user is signing into production. The present case instead turns on: The callback URL in the authorization request does not match the registered app redirect configuration. The direct answer here is: The callback URL in the authorization request does not match the registered app redirect configuration.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: 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 callback URL in the authorization request does not match the registered app redirect configuration. The direct answer here is: The callback URL in the authorization request does not match the registered app redirect configuration.
Question 110
An architect must create an acceptance test after choosing: Correct the client redirect-URI registration and verify exact authorization endpoint and app identity. For the situation An OAuth client receives invalid_redirect_uri after its administrator migrates from test to production. Which result most directly proves success?
- Login succeeds across affected orgs with the intended trusted signing certificate.
- An assertion targeted at the production service provider is accepted after proper validation.
- The assertion maps to the correct existing Salesforce account without accidental user duplication.
- The registered client completes its authorization flow only at an approved callback URL.
Explanation
Correct Answer
D:Best. The verification target is: The registered client completes its authorization flow only at an approved callback URL. It tests whether the chosen approach—Correct the client redirect-URI registration and verify exact authorization endpoint and app identity.—actually resolves the specific finding: The callback URL in the authorization request does not match the registered app redirect configuration.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A group of employees receives intermittent SAML signature failures after an identity-provider certificate rollover. Its relevant condition is: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The present case instead turns on: The callback URL in the authorization request does not match the registered app redirect configuration. The direct answer here is: The registered client completes its authorization flow only at an approved callback URL.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Salesforce rejects a newly deployed SAML integration with an invalid assertion audience error. Its relevant condition is: The IdP uses a destination string copied from a sandbox while the user is signing into production. The present case instead turns on: The callback URL in the authorization request does not match the registered app redirect configuration. The direct answer here is: The registered client completes its authorization flow only at an approved callback URL.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A browser SSO login returns a valid assertion but Salesforce cannot find the intended existing user. Its relevant condition is: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The present case instead turns on: The callback URL in the authorization request does not match the registered app redirect configuration. The direct answer here is: The registered client completes its authorization flow only at an approved callback URL.