mcAfee Secure Website
exam =5
exam =6

Exam Code: Certified Platform Identity and Access Management Architect

Exam Name: Certified Platform Identity and Access Management Architect

Certification Provider: Salesforce

Salesforce Certified Platform Identity and Access Management Architect Questions & Answers

Reliable & Actual Study Materials for Certified Platform Identity and Access Management Architect Exam Success

58 Questions & Answers with Testing Engine

"Certified Platform Identity and Access Management Architect: Certified Platform Identity and Access Management Architect" Testing Engine covers all the knowledge points of the real Salesforce Certified Platform Identity and Access Management Architect exam.

The latest actual Certified Platform Identity and Access Management Architect Questions & Answers from Pass4sure. Everything you need to prepare and get best score at Certified Platform Identity and Access Management Architect exam easily and quickly.

exam =7
Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Salesforce Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Was: $137.49
Now: $124.99

Salesforce Certified Platform Identity and Access Management Architect Practice Test 20

Question 190

A partner account must be assigned membership based on verified identity claims beyond Salesforce's default JIT mapping. Most decisive verification?

  1. Validate API principal scope, idempotent create/update, failure retries and deactivation latency
  2. Check external IdP metadata, Salesforce SP entity ID, ACS endpoint and role mapping
  3. Inspect FederationIdentifier values, SAML NameID, duplicate users and first-login creation trace
  4. Test handler user matching, account creation, least-privilege assignment and safe exception rollback

Explanation

Correct Answer

D:

“Test handler user matching, account creation, least-privilege assignment and safe exception rollback” distinguishes sign-in from entitlement administration in a partner account must be assigned membership based on verified identity claims beyond Salesforce's default JIT mapping It checks whether use a reviewed custom SamlJitHandler only where standard JIT rules cannot express supported requirements.

Incorrect Answers

A:

“Validate API principal scope, idempotent create/update, failure retries and deactivation latency” needs to be evaluated against A partner account must be assigned membership based on verified identity claims beyond Salesforce's default JIT mapping. The relevant check is Test handler user matching, account creation, least-privilege assignment and safe exception rollback; Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated.

B:

“Check external IdP metadata, Salesforce SP entity ID, ACS endpoint and role mapping” needs to be evaluated against A partner account must be assigned membership based on verified identity claims beyond Salesforce's default JIT mapping. The relevant check is Test handler user matching, account creation, least-privilege assignment and safe exception rollback; Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated.

C:

“Inspect FederationIdentifier values, SAML NameID, duplicate users and first-login creation trace” needs to be evaluated against A partner account must be assigned membership based on verified identity claims beyond Salesforce's default JIT mapping. The relevant check is Test handler user matching, account creation, least-privilege assignment and safe exception rollback; Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated.

Question 191

A partner account must be assigned membership based on verified identity claims beyond Salesforce's default JIT mapping. Key caution for this case?

  1. Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated
  2. A permission-set change cannot fix an assertion that is addressed to the wrong service provider
  3. A valid third-party social identity is not permission to create unrestricted Salesforce users
  4. Accepting an identity token requires a trusted issuer and accurate local user mapping, not just an email claim

Explanation

Correct Answer

A:

“Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated” needs to be evaluated against A partner account must be assigned membership based on verified identity claims beyond Salesforce's default JIT mapping. The relevant check is Test handler user matching, account creation, least-privilege assignment and safe exception rollback; Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated.

Incorrect Answers

B:

“A permission-set change cannot fix an assertion that is addressed to the wrong service provider” needs to be evaluated against A partner account must be assigned membership based on verified identity claims beyond Salesforce's default JIT mapping. The relevant check is Test handler user matching, account creation, least-privilege assignment and safe exception rollback; Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated.

C:

“A valid third-party social identity is not permission to create unrestricted Salesforce users” needs to be evaluated against A partner account must be assigned membership based on verified identity claims beyond Salesforce's default JIT mapping. The relevant check is Test handler user matching, account creation, least-privilege assignment and safe exception rollback; Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated.

D:

“Accepting an identity token requires a trusted issuer and accurate local user mapping, not just an email claim” needs to be evaluated against A partner account must be assigned membership based on verified identity claims beyond Salesforce's default JIT mapping. The relevant check is Test handler user matching, account creation, least-privilege assignment and safe exception rollback; Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated.

Question 192

A partner account must be assigned membership based on verified identity claims beyond Salesforce's default JIT mapping. Best complete IAM decision record?

  1. Action: Configure standard or custom JIT account matching with unique stable subject identifiers and controlled updates. Verification: Validate API principal scope, idempotent create/update, failure retries and deactivation latency. Boundary: Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated.
  2. Action: Use Salesforce Login History and available SAML diagnostic evidence to classify the failure before remediation. Verification: Test handler user matching, account creation, least-privilege assignment and safe exception rollback. Boundary: A valid third-party social identity is not permission to create unrestricted Salesforce users.
  3. Action: Use a reviewed custom SamlJitHandler only where standard JIT rules cannot express supported requirements. Verification: Check external IdP metadata, Salesforce SP entity ID, ACS endpoint and role mapping. Boundary: A permission-set change cannot fix an assertion that is addressed to the wrong service provider.
  4. Action: Use a reviewed custom SamlJitHandler only where standard JIT rules cannot express supported requirements. Verification: Test handler user matching, account creation, least-privilege assignment and safe exception rollback. Boundary: Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated.

Explanation

Correct Answer

D:

“Action: Use a reviewed custom SamlJitHandler only where standard JIT rules cannot express supported requirements. Verification: Test handler user matching, account creation, least-privilege assignment and safe exception rollback. Boundary: Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated” addresses the access-design responsibilities in a partner account must be assigned membership based on verified identity claims beyond Salesforce's default JIT mapping Test against test handler user matching, account creation, least-privilege assignment and safe exception rollback; custom provisioning code can introduce elevated access or duplicate identities if claims are not validated.

Incorrect Answers

A:

“Action: Configure standard or custom JIT account matching with unique stable subject identifiers and controlled updates. Verification: Validate API principal scope, idempotent create/update, failure retries and deactivation latency. Boundary: Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated” may apply to a related identity task, but it does not establish test handler user matching, account creation, least-privilege assignment and safe exception rollback for a partner account must be assigned membership based on verified identity claims beyond Salesforce's default JIT mapping The controlling boundary is: Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated.

B:

“Action: Use Salesforce Login History and available SAML diagnostic evidence to classify the failure before remediation. Verification: Test handler user matching, account creation, least-privilege assignment and safe exception rollback. Boundary: A valid third-party social identity is not permission to create unrestricted Salesforce users” may apply to a related identity task, but it does not establish test handler user matching, account creation, least-privilege assignment and safe exception rollback for a partner account must be assigned membership based on verified identity claims beyond Salesforce's default JIT mapping The controlling boundary is: Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated.

C:

“Action: Use a reviewed custom SamlJitHandler only where standard JIT rules cannot express supported requirements. Verification: Check external IdP metadata, Salesforce SP entity ID, ACS endpoint and role mapping. Boundary: A permission-set change cannot fix an assertion that is addressed to the wrong service provider” may apply to a related identity task, but it does not establish test handler user matching, account creation, least-privilege assignment and safe exception rollback for a partner account must be assigned membership based on verified identity claims beyond Salesforce's default JIT mapping The controlling boundary is: Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated.

Question 193

An HR directory disables a worker immediately but Salesforce access remains active because JIT updates only at the next login. Best next IAM response?

  1. Plan a supported cutover from delegated authentication to federation with rollback and account mapping tests
  2. Design My Domain login policies with an authorized SSO entry point and a controlled account recovery path
  3. Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT
  4. Use the supported Salesforce authentication-provider integration with claim validation and account registration mapping

Explanation

Correct Answer

C:

“Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT” addresses the access-design responsibilities in an HR directory disables a worker immediately but Salesforce access remains active because JIT updates only at the next login Test against correlate HR termination event, Salesforce active status, refresh tokens and existing sessions; just-in-Time account creation is not a timely offboarding mechanism by itself.

Incorrect Answers

A:

“Plan a supported cutover from delegated authentication to federation with rollback and account mapping tests” may apply to a related identity task, but it does not establish correlate HR termination event, Salesforce active status, refresh tokens and existing sessions for an HR directory disables a worker immediately but Salesforce access remains active because JIT updates only at the next login The controlling boundary is: Just-in-Time account creation is not a timely offboarding mechanism by itself.

B:

“Design My Domain login policies with an authorized SSO entry point and a controlled account recovery path” may apply to a related identity task, but it does not establish correlate HR termination event, Salesforce active status, refresh tokens and existing sessions for an HR directory disables a worker immediately but Salesforce access remains active because JIT updates only at the next login The controlling boundary is: Just-in-Time account creation is not a timely offboarding mechanism by itself.

D:

“Use the supported Salesforce authentication-provider integration with claim validation and account registration mapping” may apply to a related identity task, but it does not establish correlate HR termination event, Salesforce active status, refresh tokens and existing sessions for an HR directory disables a worker immediately but Salesforce access remains active because JIT updates only at the next login The controlling boundary is: Just-in-Time account creation is not a timely offboarding mechanism by itself.

Question 194

An HR directory disables a worker immediately but Salesforce access remains active because JIT updates only at the next login. Most decisive verification?

  1. Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions
  2. Compare the actual assertion issuer, destination, audience, NameID format and signature chain
  3. Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs
  4. Test new and modified user assignments, permission sets, claims validation and denied-access cases

Explanation

Correct Answer

A:

“Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions” distinguishes sign-in from entitlement administration in an HR directory disables a worker immediately but Salesforce access remains active because JIT updates only at the next login It checks whether add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT.

Incorrect Answers

B:

“Compare the actual assertion issuer, destination, audience, NameID format and signature chain” needs to be evaluated against An HR directory disables a worker immediately but Salesforce access remains active because JIT updates only at the next login. The relevant check is Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions; Just-in-Time account creation is not a timely offboarding mechanism by itself.

C:

“Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs” needs to be evaluated against An HR directory disables a worker immediately but Salesforce access remains active because JIT updates only at the next login. The relevant check is Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions; Just-in-Time account creation is not a timely offboarding mechanism by itself.

D:

“Test new and modified user assignments, permission sets, claims validation and denied-access cases” needs to be evaluated against An HR directory disables a worker immediately but Salesforce access remains active because JIT updates only at the next login. The relevant check is Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions; Just-in-Time account creation is not a timely offboarding mechanism by itself.

Question 195

An HR directory disables a worker immediately but Salesforce access remains active because JIT updates only at the next login. Key caution for this case?

  1. Just-in-Time account creation is not a timely offboarding mechanism by itself
  2. Skipping signature verification to restore access would remove an essential federation security control
  3. Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated
  4. Retrying login or resetting passwords may not resolve a federation trust or provisioning failure

Explanation

Correct Answer

A:

“Just-in-Time account creation is not a timely offboarding mechanism by itself” needs to be evaluated against An HR directory disables a worker immediately but Salesforce access remains active because JIT updates only at the next login. The relevant check is Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions; Just-in-Time account creation is not a timely offboarding mechanism by itself.

Incorrect Answers

B:

“Skipping signature verification to restore access would remove an essential federation security control” needs to be evaluated against An HR directory disables a worker immediately but Salesforce access remains active because JIT updates only at the next login. The relevant check is Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions; Just-in-Time account creation is not a timely offboarding mechanism by itself.

C:

“Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated” needs to be evaluated against An HR directory disables a worker immediately but Salesforce access remains active because JIT updates only at the next login. The relevant check is Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions; Just-in-Time account creation is not a timely offboarding mechanism by itself.

D:

“Retrying login or resetting passwords may not resolve a federation trust or provisioning failure” needs to be evaluated against An HR directory disables a worker immediately but Salesforce access remains active because JIT updates only at the next login. The relevant check is Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions; Just-in-Time account creation is not a timely offboarding mechanism by itself.

Question 196

An HR directory disables a worker immediately but Salesforce access remains active because JIT updates only at the next login. Best complete IAM decision record?

  1. Action: Use the supported Salesforce authentication-provider integration with claim validation and account registration mapping. Verification: Compare the actual assertion issuer, destination, audience, NameID format and signature chain. Boundary: Just-in-Time account creation is not a timely offboarding mechanism by itself.
  2. Action: Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT. Verification: Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions. Boundary: Just-in-Time account creation is not a timely offboarding mechanism by itself.
  3. Action: Plan a supported cutover from delegated authentication to federation with rollback and account mapping tests. Verification: Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions. Boundary: Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated.
  4. Action: Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT. Verification: Test new and modified user assignments, permission sets, claims validation and denied-access cases. Boundary: Skipping signature verification to restore access would remove an essential federation security control.

Explanation

Correct Answer

B:

“Action: Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT. Verification: Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions. Boundary: Just-in-Time account creation is not a timely offboarding mechanism by itself” addresses the access-design responsibilities in an HR directory disables a worker immediately but Salesforce access remains active because JIT updates only at the next login Test against correlate HR termination event, Salesforce active status, refresh tokens and existing sessions; just-in-Time account creation is not a timely offboarding mechanism by itself.

Incorrect Answers

A:

“Action: Use the supported Salesforce authentication-provider integration with claim validation and account registration mapping. Verification: Compare the actual assertion issuer, destination, audience, NameID format and signature chain. Boundary: Just-in-Time account creation is not a timely offboarding mechanism by itself” may apply to a related identity task, but it does not establish correlate HR termination event, Salesforce active status, refresh tokens and existing sessions for an HR directory disables a worker immediately but Salesforce access remains active because JIT updates only at the next login The controlling boundary is: Just-in-Time account creation is not a timely offboarding mechanism by itself.

C:

“Action: Plan a supported cutover from delegated authentication to federation with rollback and account mapping tests. Verification: Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions. Boundary: Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated” may apply to a related identity task, but it does not establish correlate HR termination event, Salesforce active status, refresh tokens and existing sessions for an HR directory disables a worker immediately but Salesforce access remains active because JIT updates only at the next login The controlling boundary is: Just-in-Time account creation is not a timely offboarding mechanism by itself.

D:

“Action: Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT. Verification: Test new and modified user assignments, permission sets, claims validation and denied-access cases. Boundary: Skipping signature verification to restore access would remove an essential federation security control” may apply to a related identity task, but it does not establish correlate HR termination event, Salesforce active status, refresh tokens and existing sessions for an HR directory disables a worker immediately but Salesforce access remains active because JIT updates only at the next login The controlling boundary is: Just-in-Time account creation is not a timely offboarding mechanism by itself.

Question 197

A partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists. Best next IAM response?

  1. Plan a supported cutover from delegated authentication to federation with rollback and account mapping tests
  2. Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT
  3. Use the supported Salesforce authentication-provider integration with claim validation and account registration mapping
  4. Design My Domain login policies with an authorized SSO entry point and a controlled account recovery path

Explanation

Correct Answer

B:

“Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT” addresses the access-design responsibilities in a partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists Test against correlate HR termination event, Salesforce active status, refresh tokens and existing sessions; just-in-Time account creation is not a timely offboarding mechanism by itself.

Incorrect Answers

A:

“Plan a supported cutover from delegated authentication to federation with rollback and account mapping tests” may apply to a related identity task, but it does not establish correlate HR termination event, Salesforce active status, refresh tokens and existing sessions for a partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists The controlling boundary is: Just-in-Time account creation is not a timely offboarding mechanism by itself.

C:

“Use the supported Salesforce authentication-provider integration with claim validation and account registration mapping” may apply to a related identity task, but it does not establish correlate HR termination event, Salesforce active status, refresh tokens and existing sessions for a partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists The controlling boundary is: Just-in-Time account creation is not a timely offboarding mechanism by itself.

D:

“Design My Domain login policies with an authorized SSO entry point and a controlled account recovery path” may apply to a related identity task, but it does not establish correlate HR termination event, Salesforce active status, refresh tokens and existing sessions for a partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists The controlling boundary is: Just-in-Time account creation is not a timely offboarding mechanism by itself.

Question 198

A partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists. Most decisive verification?

  1. Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions
  2. Test new and modified user assignments, permission sets, claims validation and denied-access cases
  3. Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs
  4. Compare the actual assertion issuer, destination, audience, NameID format and signature chain

Explanation

Correct Answer

A:

“Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions” distinguishes sign-in from entitlement administration in a partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists It checks whether add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT.

Incorrect Answers

B:

“Test new and modified user assignments, permission sets, claims validation and denied-access cases” needs to be evaluated against A partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists. The relevant check is Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions; Just-in-Time account creation is not a timely offboarding mechanism by itself.

C:

“Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs” needs to be evaluated against A partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists. The relevant check is Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions; Just-in-Time account creation is not a timely offboarding mechanism by itself.

D:

“Compare the actual assertion issuer, destination, audience, NameID format and signature chain” needs to be evaluated against A partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists. The relevant check is Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions; Just-in-Time account creation is not a timely offboarding mechanism by itself.

Question 199

A partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists. Key caution for this case?

  1. Retrying login or resetting passwords may not resolve a federation trust or provisioning failure
  2. Just-in-Time account creation is not a timely offboarding mechanism by itself
  3. Skipping signature verification to restore access would remove an essential federation security control
  4. Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated

Explanation

Correct Answer

B:

“Just-in-Time account creation is not a timely offboarding mechanism by itself” needs to be evaluated against A partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists. The relevant check is Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions; Just-in-Time account creation is not a timely offboarding mechanism by itself.

Incorrect Answers

A:

“Retrying login or resetting passwords may not resolve a federation trust or provisioning failure” needs to be evaluated against A partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists. The relevant check is Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions; Just-in-Time account creation is not a timely offboarding mechanism by itself.

C:

“Skipping signature verification to restore access would remove an essential federation security control” needs to be evaluated against A partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists. The relevant check is Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions; Just-in-Time account creation is not a timely offboarding mechanism by itself.

D:

“Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated” needs to be evaluated against A partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists. The relevant check is Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions; Just-in-Time account creation is not a timely offboarding mechanism by itself.

Question 200

A partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists. Best complete IAM decision record?

  1. Action: Use the supported Salesforce authentication-provider integration with claim validation and account registration mapping. Verification: Compare the actual assertion issuer, destination, audience, NameID format and signature chain. Boundary: Just-in-Time account creation is not a timely offboarding mechanism by itself.
  2. Action: Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT. Verification: Test new and modified user assignments, permission sets, claims validation and denied-access cases. Boundary: Skipping signature verification to restore access would remove an essential federation security control.
  3. Action: Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT. Verification: Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions. Boundary: Just-in-Time account creation is not a timely offboarding mechanism by itself.
  4. Action: Plan a supported cutover from delegated authentication to federation with rollback and account mapping tests. Verification: Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions. Boundary: Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated.

Explanation

Correct Answer

C:

“Action: Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT. Verification: Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions. Boundary: Just-in-Time account creation is not a timely offboarding mechanism by itself” addresses the access-design responsibilities in a partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists Test against correlate HR termination event, Salesforce active status, refresh tokens and existing sessions; just-in-Time account creation is not a timely offboarding mechanism by itself.

Incorrect Answers

A:

“Action: Use the supported Salesforce authentication-provider integration with claim validation and account registration mapping. Verification: Compare the actual assertion issuer, destination, audience, NameID format and signature chain. Boundary: Just-in-Time account creation is not a timely offboarding mechanism by itself” may apply to a related identity task, but it does not establish correlate HR termination event, Salesforce active status, refresh tokens and existing sessions for a partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists The controlling boundary is: Just-in-Time account creation is not a timely offboarding mechanism by itself.

B:

“Action: Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT. Verification: Test new and modified user assignments, permission sets, claims validation and denied-access cases. Boundary: Skipping signature verification to restore access would remove an essential federation security control” may apply to a related identity task, but it does not establish correlate HR termination event, Salesforce active status, refresh tokens and existing sessions for a partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists The controlling boundary is: Just-in-Time account creation is not a timely offboarding mechanism by itself.

D:

“Action: Plan a supported cutover from delegated authentication to federation with rollback and account mapping tests. Verification: Correlate HR termination event, Salesforce active status, refresh tokens and existing sessions. Boundary: Custom provisioning code can introduce elevated access or duplicate identities if claims are not validated” may apply to a related identity task, but it does not establish correlate HR termination event, Salesforce active status, refresh tokens and existing sessions for a partner's contract ends while their Salesforce session is still open and no independent lifecycle sync exists The controlling boundary is: Just-in-Time account creation is not a timely offboarding mechanism by itself.

Certified Platform Identity and Access Management Architect Practice Tests