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 27

Question 260

A helpdesk sees repeated Salesforce SSO failures only for recently onboarded accounts. Best complete IAM decision record?

  1. Action: Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT. Verification: Correlate time, username, error code, assertion claims and IdP logs under authorized access. Boundary: Disabling temporal validation is not an acceptable workaround for clock-skew problems.
  2. Action: Agree on an unambiguous NameID or federation identifier claim before accepting the identity. Verification: Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs. Boundary: Retrying login or resetting passwords may not resolve a federation trust or provisioning failure.
  3. Action: Use Salesforce Login History and available SAML diagnostic evidence to classify the failure before remediation. Verification: Test trusted claims, contact matching, consent record and duplicate-registration failures. Boundary: Moving password verification does not automatically migrate SAML trust, MFA assurance or local authorization.
  4. Action: Use Salesforce Login History and available SAML diagnostic evidence to classify the failure before remediation. Verification: Correlate time, username, error code, assertion claims and IdP logs under authorized access. Boundary: Retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

Explanation

Correct Answer

D:

“Action: Use Salesforce Login History and available SAML diagnostic evidence to classify the failure before remediation. Verification: Correlate time, username, error code, assertion claims and IdP logs under authorized access. Boundary: Retrying login or resetting passwords may not resolve a federation trust or provisioning failure” addresses the access-design responsibilities in a helpdesk sees repeated Salesforce SSO failures only for recently onboarded accounts Test against correlate time, username, error code, assertion claims and IdP logs under authorized access; retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

Incorrect Answers

A:

“Action: Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT. Verification: Correlate time, username, error code, assertion claims and IdP logs under authorized access. Boundary: Disabling temporal validation is not an acceptable workaround for clock-skew problems” may apply to a related identity task, but it does not establish correlate time, username, error code, assertion claims and IdP logs under authorized access for a helpdesk sees repeated Salesforce SSO failures only for recently onboarded accounts The controlling boundary is: Retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

B:

“Action: Agree on an unambiguous NameID or federation identifier claim before accepting the identity. Verification: Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs. Boundary: Retrying login or resetting passwords may not resolve a federation trust or provisioning failure” may apply to a related identity task, but it does not establish correlate time, username, error code, assertion claims and IdP logs under authorized access for a helpdesk sees repeated Salesforce SSO failures only for recently onboarded accounts The controlling boundary is: Retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

C:

“Action: Use Salesforce Login History and available SAML diagnostic evidence to classify the failure before remediation. Verification: Test trusted claims, contact matching, consent record and duplicate-registration failures. Boundary: Moving password verification does not automatically migrate SAML trust, MFA assurance or local authorization” may apply to a related identity task, but it does not establish correlate time, username, error code, assertion claims and IdP logs under authorized access for a helpdesk sees repeated Salesforce SSO failures only for recently onboarded accounts The controlling boundary is: Retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

Question 261

A security engineer must distinguish signature errors from missing user mappings in a failed login sequence. Best next IAM response?

  1. Agree on an unambiguous NameID or federation identifier claim before accepting the identity
  2. Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT
  3. Diagnose cryptographic trust using approved IdP metadata and correct certificate rotation
  4. Use Salesforce Login History and available SAML diagnostic evidence to classify the failure before remediation

Explanation

Correct Answer

D:

“Use Salesforce Login History and available SAML diagnostic evidence to classify the failure before remediation” addresses the access-design responsibilities in a security engineer must distinguish signature errors from missing user mappings in a failed login sequence Test against correlate time, username, error code, assertion claims and IdP logs under authorized access; retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

Incorrect Answers

A:

“Agree on an unambiguous NameID or federation identifier claim before accepting the identity” may apply to a related identity task, but it does not establish correlate time, username, error code, assertion claims and IdP logs under authorized access for a security engineer must distinguish signature errors from missing user mappings in a failed login sequence The controlling boundary is: Retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

B:

“Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT” may apply to a related identity task, but it does not establish correlate time, username, error code, assertion claims and IdP logs under authorized access for a security engineer must distinguish signature errors from missing user mappings in a failed login sequence The controlling boundary is: Retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

C:

“Diagnose cryptographic trust using approved IdP metadata and correct certificate rotation” may apply to a related identity task, but it does not establish correlate time, username, error code, assertion claims and IdP logs under authorized access for a security engineer must distinguish signature errors from missing user mappings in a failed login sequence The controlling boundary is: Retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

Question 262

A security engineer must distinguish signature errors from missing user mappings in a failed login sequence. Most decisive verification?

  1. Correlate time, username, error code, assertion claims and IdP logs under authorized access
  2. Test trusted claims, contact matching, consent record and duplicate-registration failures
  3. Check SAML attribute names, license and profile eligibility, linked contact/account and JIT error details
  4. Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs

Explanation

Correct Answer

A:

“Correlate time, username, error code, assertion claims and IdP logs under authorized access” distinguishes sign-in from entitlement administration in a security engineer must distinguish signature errors from missing user mappings in a failed login sequence It checks whether use Salesforce Login History and available SAML diagnostic evidence to classify the failure before remediation.

Incorrect Answers

B:

“Test trusted claims, contact matching, consent record and duplicate-registration failures” needs to be evaluated against A security engineer must distinguish signature errors from missing user mappings in a failed login sequence. The relevant check is Correlate time, username, error code, assertion claims and IdP logs under authorized access; Retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

C:

“Check SAML attribute names, license and profile eligibility, linked contact/account and JIT error details” needs to be evaluated against A security engineer must distinguish signature errors from missing user mappings in a failed login sequence. The relevant check is Correlate time, username, error code, assertion claims and IdP logs under authorized access; Retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

D:

“Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs” needs to be evaluated against A security engineer must distinguish signature errors from missing user mappings in a failed login sequence. The relevant check is Correlate time, username, error code, assertion claims and IdP logs under authorized access; Retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

Question 263

A security engineer must distinguish signature errors from missing user mappings in a failed login sequence. Key caution for this case?

  1. Redirecting employees to SSO must not accidentally lock all administrators out of the org
  2. Disabling temporal validation is not an acceptable workaround for clock-skew problems
  3. Retrying login or resetting passwords may not resolve a federation trust or provisioning failure
  4. Moving password verification does not automatically migrate SAML trust, MFA assurance or local authorization

Explanation

Correct Answer

C:

“Retrying login or resetting passwords may not resolve a federation trust or provisioning failure” needs to be evaluated against A security engineer must distinguish signature errors from missing user mappings in a failed login sequence. The relevant check is Correlate time, username, error code, assertion claims and IdP logs under authorized access; Retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

Incorrect Answers

A:

“Redirecting employees to SSO must not accidentally lock all administrators out of the org” needs to be evaluated against A security engineer must distinguish signature errors from missing user mappings in a failed login sequence. The relevant check is Correlate time, username, error code, assertion claims and IdP logs under authorized access; Retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

B:

“Disabling temporal validation is not an acceptable workaround for clock-skew problems” needs to be evaluated against A security engineer must distinguish signature errors from missing user mappings in a failed login sequence. The relevant check is Correlate time, username, error code, assertion claims and IdP logs under authorized access; Retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

D:

“Moving password verification does not automatically migrate SAML trust, MFA assurance or local authorization” needs to be evaluated against A security engineer must distinguish signature errors from missing user mappings in a failed login sequence. The relevant check is Correlate time, username, error code, assertion claims and IdP logs under authorized access; Retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

Question 264

A security engineer must distinguish signature errors from missing user mappings in a failed login sequence. Best complete IAM decision record?

  1. Action: Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT. Verification: Correlate time, username, error code, assertion claims and IdP logs under authorized access. Boundary: Disabling temporal validation is not an acceptable workaround for clock-skew problems.
  2. Action: Agree on an unambiguous NameID or federation identifier claim before accepting the identity. Verification: Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs. Boundary: Retrying login or resetting passwords may not resolve a federation trust or provisioning failure.
  3. Action: Use Salesforce Login History and available SAML diagnostic evidence to classify the failure before remediation. Verification: Test trusted claims, contact matching, consent record and duplicate-registration failures. Boundary: Moving password verification does not automatically migrate SAML trust, MFA assurance or local authorization.
  4. Action: Use Salesforce Login History and available SAML diagnostic evidence to classify the failure before remediation. Verification: Correlate time, username, error code, assertion claims and IdP logs under authorized access. Boundary: Retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

Explanation

Correct Answer

D:

“Action: Use Salesforce Login History and available SAML diagnostic evidence to classify the failure before remediation. Verification: Correlate time, username, error code, assertion claims and IdP logs under authorized access. Boundary: Retrying login or resetting passwords may not resolve a federation trust or provisioning failure” addresses the access-design responsibilities in a security engineer must distinguish signature errors from missing user mappings in a failed login sequence Test against correlate time, username, error code, assertion claims and IdP logs under authorized access; retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

Incorrect Answers

A:

“Action: Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT. Verification: Correlate time, username, error code, assertion claims and IdP logs under authorized access. Boundary: Disabling temporal validation is not an acceptable workaround for clock-skew problems” may apply to a related identity task, but it does not establish correlate time, username, error code, assertion claims and IdP logs under authorized access for a security engineer must distinguish signature errors from missing user mappings in a failed login sequence The controlling boundary is: Retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

B:

“Action: Agree on an unambiguous NameID or federation identifier claim before accepting the identity. Verification: Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs. Boundary: Retrying login or resetting passwords may not resolve a federation trust or provisioning failure” may apply to a related identity task, but it does not establish correlate time, username, error code, assertion claims and IdP logs under authorized access for a security engineer must distinguish signature errors from missing user mappings in a failed login sequence The controlling boundary is: Retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

C:

“Action: Use Salesforce Login History and available SAML diagnostic evidence to classify the failure before remediation. Verification: Test trusted claims, contact matching, consent record and duplicate-registration failures. Boundary: Moving password verification does not automatically migrate SAML trust, MFA assurance or local authorization” may apply to a related identity task, but it does not establish correlate time, username, error code, assertion claims and IdP logs under authorized access for a security engineer must distinguish signature errors from missing user mappings in a failed login sequence The controlling boundary is: Retrying login or resetting passwords may not resolve a federation trust or provisioning failure.

Question 265

An enterprise supports two workforce identity providers and needs users routed to the correct one at sign-in. Best next IAM response?

  1. Configure standard or custom JIT account matching with unique stable subject identifiers and controlled updates
  2. Complete Salesforce SP and corporate IdP trust registration for entity ID, ACS destination, subject and certificate
  3. Configure approved identity-provider choices and login discovery or routing appropriate to the org's supported capabilities
  4. Implement a controlled authentication provider and registration handler mapping for the external customer population

Explanation

Correct Answer

C:

“Configure approved identity-provider choices and login discovery or routing appropriate to the org's supported capabilities” addresses the access-design responsibilities in an enterprise supports two workforce identity providers and needs users routed to the correct one at sign-in Test against validate entry page, provider configuration, domain discovery, callback result and error route; a provider's presence on a login page does not prove it is authorized for every account population.

Incorrect Answers

A:

“Configure standard or custom JIT account matching with unique stable subject identifiers and controlled updates” may apply to a related identity task, but it does not establish validate entry page, provider configuration, domain discovery, callback result and error route for an enterprise supports two workforce identity providers and needs users routed to the correct one at sign-in The controlling boundary is: A provider's presence on a login page does not prove it is authorized for every account population.

B:

“Complete Salesforce SP and corporate IdP trust registration for entity ID, ACS destination, subject and certificate” may apply to a related identity task, but it does not establish validate entry page, provider configuration, domain discovery, callback result and error route for an enterprise supports two workforce identity providers and needs users routed to the correct one at sign-in The controlling boundary is: A provider's presence on a login page does not prove it is authorized for every account population.

D:

“Implement a controlled authentication provider and registration handler mapping for the external customer population” may apply to a related identity task, but it does not establish validate entry page, provider configuration, domain discovery, callback result and error route for an enterprise supports two workforce identity providers and needs users routed to the correct one at sign-in The controlling boundary is: A provider's presence on a login page does not prove it is authorized for every account population.

Question 266

An enterprise supports two workforce identity providers and needs users routed to the correct one at sign-in. Most decisive verification?

  1. Test name or email changes against unchanged federation identifiers and audit links
  2. Test new and modified user assignments, permission sets, claims validation and denied-access cases
  3. Validate entry page, provider configuration, domain discovery, callback result and error route
  4. Compare Destination, AudienceRestriction, ACS, My Domain and the exact SAML error

Explanation

Correct Answer

C:

“Validate entry page, provider configuration, domain discovery, callback result and error route” distinguishes sign-in from entitlement administration in an enterprise supports two workforce identity providers and needs users routed to the correct one at sign-in It checks whether configure approved identity-provider choices and login discovery or routing appropriate to the org's supported capabilities.

Incorrect Answers

A:

“Test name or email changes against unchanged federation identifiers and audit links” needs to be evaluated against An enterprise supports two workforce identity providers and needs users routed to the correct one at sign-in. The relevant check is Validate entry page, provider configuration, domain discovery, callback result and error route; A provider's presence on a login page does not prove it is authorized for every account population.

B:

“Test new and modified user assignments, permission sets, claims validation and denied-access cases” needs to be evaluated against An enterprise supports two workforce identity providers and needs users routed to the correct one at sign-in. The relevant check is Validate entry page, provider configuration, domain discovery, callback result and error route; A provider's presence on a login page does not prove it is authorized for every account population.

D:

“Compare Destination, AudienceRestriction, ACS, My Domain and the exact SAML error” needs to be evaluated against An enterprise supports two workforce identity providers and needs users routed to the correct one at sign-in. The relevant check is Validate entry page, provider configuration, domain discovery, callback result and error route; A provider's presence on a login page does not prove it is authorized for every account population.

Question 267

An enterprise supports two workforce identity providers and needs users routed to the correct one at sign-in. Key caution for this case?

  1. A provider's presence on a login page does not prove it is authorized for every account population
  2. A permission-set change cannot fix an assertion that is addressed to the wrong service provider
  3. Display name, address or shared email alias is not a safe primary unique identity key
  4. A successful SAML login does not make an unvalidated post-login destination safe

Explanation

Correct Answer

A:

“A provider's presence on a login page does not prove it is authorized for every account population” needs to be evaluated against An enterprise supports two workforce identity providers and needs users routed to the correct one at sign-in. The relevant check is Validate entry page, provider configuration, domain discovery, callback result and error route; A provider's presence on a login page does not prove it is authorized for every account population.

Incorrect Answers

B:

“A permission-set change cannot fix an assertion that is addressed to the wrong service provider” needs to be evaluated against An enterprise supports two workforce identity providers and needs users routed to the correct one at sign-in. The relevant check is Validate entry page, provider configuration, domain discovery, callback result and error route; A provider's presence on a login page does not prove it is authorized for every account population.

C:

“Display name, address or shared email alias is not a safe primary unique identity key” needs to be evaluated against An enterprise supports two workforce identity providers and needs users routed to the correct one at sign-in. The relevant check is Validate entry page, provider configuration, domain discovery, callback result and error route; A provider's presence on a login page does not prove it is authorized for every account population.

D:

“A successful SAML login does not make an unvalidated post-login destination safe” needs to be evaluated against An enterprise supports two workforce identity providers and needs users routed to the correct one at sign-in. The relevant check is Validate entry page, provider configuration, domain discovery, callback result and error route; A provider's presence on a login page does not prove it is authorized for every account population.

Question 268

An enterprise supports two workforce identity providers and needs users routed to the correct one at sign-in. Best complete IAM decision record?

  1. Action: Implement a controlled authentication provider and registration handler mapping for the external customer population. Verification: Test new and modified user assignments, permission sets, claims validation and denied-access cases. Boundary: A provider's presence on a login page does not prove it is authorized for every account population.
  2. Action: Configure approved identity-provider choices and login discovery or routing appropriate to the org's supported capabilities. Verification: Validate entry page, provider configuration, domain discovery, callback result and error route. Boundary: A provider's presence on a login page does not prove it is authorized for every account population.
  3. Action: Configure approved identity-provider choices and login discovery or routing appropriate to the org's supported capabilities. Verification: Compare Destination, AudienceRestriction, ACS, My Domain and the exact SAML error. Boundary: A successful SAML login does not make an unvalidated post-login destination safe.
  4. Action: Complete Salesforce SP and corporate IdP trust registration for entity ID, ACS destination, subject and certificate. Verification: Validate entry page, provider configuration, domain discovery, callback result and error route. Boundary: A permission-set change cannot fix an assertion that is addressed to the wrong service provider.

Explanation

Correct Answer

B:

“Action: Configure approved identity-provider choices and login discovery or routing appropriate to the org's supported capabilities. Verification: Validate entry page, provider configuration, domain discovery, callback result and error route. Boundary: A provider's presence on a login page does not prove it is authorized for every account population” addresses the access-design responsibilities in an enterprise supports two workforce identity providers and needs users routed to the correct one at sign-in Test against validate entry page, provider configuration, domain discovery, callback result and error route; a provider's presence on a login page does not prove it is authorized for every account population.

Incorrect Answers

A:

“Action: Implement a controlled authentication provider and registration handler mapping for the external customer population. Verification: Test new and modified user assignments, permission sets, claims validation and denied-access cases. Boundary: A provider's presence on a login page does not prove it is authorized for every account population” may apply to a related identity task, but it does not establish validate entry page, provider configuration, domain discovery, callback result and error route for an enterprise supports two workforce identity providers and needs users routed to the correct one at sign-in The controlling boundary is: A provider's presence on a login page does not prove it is authorized for every account population.

C:

“Action: Configure approved identity-provider choices and login discovery or routing appropriate to the org's supported capabilities. Verification: Compare Destination, AudienceRestriction, ACS, My Domain and the exact SAML error. Boundary: A successful SAML login does not make an unvalidated post-login destination safe” may apply to a related identity task, but it does not establish validate entry page, provider configuration, domain discovery, callback result and error route for an enterprise supports two workforce identity providers and needs users routed to the correct one at sign-in The controlling boundary is: A provider's presence on a login page does not prove it is authorized for every account population.

D:

“Action: Complete Salesforce SP and corporate IdP trust registration for entity ID, ACS destination, subject and certificate. Verification: Validate entry page, provider configuration, domain discovery, callback result and error route. 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 validate entry page, provider configuration, domain discovery, callback result and error route for an enterprise supports two workforce identity providers and needs users routed to the correct one at sign-in The controlling boundary is: A provider's presence on a login page does not prove it is authorized for every account population.

Question 269

A contractor visits the Salesforce My Domain page and must choose a vetted federation provider without confusing it with customer social login. Best next IAM response?

  1. Configure approved identity-provider choices and login discovery or routing appropriate to the org's supported capabilities
  2. Configure standard or custom JIT account matching with unique stable subject identifiers and controlled updates
  3. Complete Salesforce SP and corporate IdP trust registration for entity ID, ACS destination, subject and certificate
  4. Implement a controlled authentication provider and registration handler mapping for the external customer population

Explanation

Correct Answer

A:

“Configure approved identity-provider choices and login discovery or routing appropriate to the org's supported capabilities” addresses the access-design responsibilities in a contractor visits the Salesforce My Domain page and must choose a vetted federation provider without confusing it with customer social login Test against validate entry page, provider configuration, domain discovery, callback result and error route; a provider's presence on a login page does not prove it is authorized for every account population.

Incorrect Answers

B:

“Configure standard or custom JIT account matching with unique stable subject identifiers and controlled updates” may apply to a related identity task, but it does not establish validate entry page, provider configuration, domain discovery, callback result and error route for a contractor visits the Salesforce My Domain page and must choose a vetted federation provider without confusing it with customer social login The controlling boundary is: A provider's presence on a login page does not prove it is authorized for every account population.

C:

“Complete Salesforce SP and corporate IdP trust registration for entity ID, ACS destination, subject and certificate” may apply to a related identity task, but it does not establish validate entry page, provider configuration, domain discovery, callback result and error route for a contractor visits the Salesforce My Domain page and must choose a vetted federation provider without confusing it with customer social login The controlling boundary is: A provider's presence on a login page does not prove it is authorized for every account population.

D:

“Implement a controlled authentication provider and registration handler mapping for the external customer population” may apply to a related identity task, but it does not establish validate entry page, provider configuration, domain discovery, callback result and error route for a contractor visits the Salesforce My Domain page and must choose a vetted federation provider without confusing it with customer social login The controlling boundary is: A provider's presence on a login page does not prove it is authorized for every account population.

Question 270

A contractor visits the Salesforce My Domain page and must choose a vetted federation provider without confusing it with customer social login. Most decisive verification?

  1. Compare Destination, AudienceRestriction, ACS, My Domain and the exact SAML error
  2. Test name or email changes against unchanged federation identifiers and audit links
  3. Test new and modified user assignments, permission sets, claims validation and denied-access cases
  4. Validate entry page, provider configuration, domain discovery, callback result and error route

Explanation

Correct Answer

D:

“Validate entry page, provider configuration, domain discovery, callback result and error route” distinguishes sign-in from entitlement administration in a contractor visits the Salesforce My Domain page and must choose a vetted federation provider without confusing it with customer social login It checks whether configure approved identity-provider choices and login discovery or routing appropriate to the org's supported capabilities.

Incorrect Answers

A:

“Compare Destination, AudienceRestriction, ACS, My Domain and the exact SAML error” needs to be evaluated against A contractor visits the Salesforce My Domain page and must choose a vetted federation provider without confusing it with customer social login. The relevant check is Validate entry page, provider configuration, domain discovery, callback result and error route; A provider's presence on a login page does not prove it is authorized for every account population.

B:

“Test name or email changes against unchanged federation identifiers and audit links” needs to be evaluated against A contractor visits the Salesforce My Domain page and must choose a vetted federation provider without confusing it with customer social login. The relevant check is Validate entry page, provider configuration, domain discovery, callback result and error route; A provider's presence on a login page does not prove it is authorized for every account population.

C:

“Test new and modified user assignments, permission sets, claims validation and denied-access cases” needs to be evaluated against A contractor visits the Salesforce My Domain page and must choose a vetted federation provider without confusing it with customer social login. The relevant check is Validate entry page, provider configuration, domain discovery, callback result and error route; A provider's presence on a login page does not prove it is authorized for every account population.

Certified Platform Identity and Access Management Architect Practice Tests