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 12

Question 110

An acquired subsidiary switches its federation certificate without a coordinated rollover window. Most decisive verification?

  1. Test first login, required attributes, inactive status, license assignment and onboarding delay
  2. Check metadata update, active certificate fingerprint, error codes and rollback path
  3. Compare HR events, directory account changes, Salesforce active status and delayed sync recovery
  4. Validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app

Explanation

Correct Answer

B:

“Check metadata update, active certificate fingerprint, error codes and rollback path” distinguishes sign-in from entitlement administration in an acquired subsidiary switches its federation certificate without a coordinated rollover window It checks whether coordinate trusted certificate rotation and test old/new key acceptance according to supported Salesforce settings.

Incorrect Answers

A:

“Test first login, required attributes, inactive status, license assignment and onboarding delay” needs to be evaluated against An acquired subsidiary switches its federation certificate without a coordinated rollover window. The relevant check is Check metadata update, active certificate fingerprint, error codes and rollback path; A successful identity-provider change does not guarantee relying applications automatically trust the replacement key.

C:

“Compare HR events, directory account changes, Salesforce active status and delayed sync recovery” needs to be evaluated against An acquired subsidiary switches its federation certificate without a coordinated rollover window. The relevant check is Check metadata update, active certificate fingerprint, error codes and rollback path; A successful identity-provider change does not guarantee relying applications automatically trust the replacement key.

D:

“Validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app” needs to be evaluated against An acquired subsidiary switches its federation certificate without a coordinated rollover window. The relevant check is Check metadata update, active certificate fingerprint, error codes and rollback path; A successful identity-provider change does not guarantee relying applications automatically trust the replacement key.

Question 111

An acquired subsidiary switches its federation certificate without a coordinated rollover window. Key caution for this case?

  1. Sign-in-triggered changes alone cannot guarantee off-session user lifecycle compliance
  2. A successful identity-provider change does not guarantee relying applications automatically trust the replacement key
  3. OIDC authentication and OAuth resource authorization solve related but different requirements
  4. Different SAML initiation patterns cannot be assumed to produce identical request validation and RelayState behavior

Explanation

Correct Answer

B:

“A successful identity-provider change does not guarantee relying applications automatically trust the replacement key” needs to be evaluated against An acquired subsidiary switches its federation certificate without a coordinated rollover window. The relevant check is Check metadata update, active certificate fingerprint, error codes and rollback path; A successful identity-provider change does not guarantee relying applications automatically trust the replacement key.

Incorrect Answers

A:

“Sign-in-triggered changes alone cannot guarantee off-session user lifecycle compliance” needs to be evaluated against An acquired subsidiary switches its federation certificate without a coordinated rollover window. The relevant check is Check metadata update, active certificate fingerprint, error codes and rollback path; A successful identity-provider change does not guarantee relying applications automatically trust the replacement key.

C:

“OIDC authentication and OAuth resource authorization solve related but different requirements” needs to be evaluated against An acquired subsidiary switches its federation certificate without a coordinated rollover window. The relevant check is Check metadata update, active certificate fingerprint, error codes and rollback path; A successful identity-provider change does not guarantee relying applications automatically trust the replacement key.

D:

“Different SAML initiation patterns cannot be assumed to produce identical request validation and RelayState behavior” needs to be evaluated against An acquired subsidiary switches its federation certificate without a coordinated rollover window. The relevant check is Check metadata update, active certificate fingerprint, error codes and rollback path; A successful identity-provider change does not guarantee relying applications automatically trust the replacement key.

Question 112

An acquired subsidiary switches its federation certificate without a coordinated rollover window. Best complete IAM decision record?

  1. Action: Coordinate trusted certificate rotation and test old/new key acceptance according to supported Salesforce settings. Verification: Compare HR events, directory account changes, Salesforce active status and delayed sync recovery. Boundary: Sign-in-triggered changes alone cannot guarantee off-session user lifecycle compliance.
  2. Action: Coordinate trusted certificate rotation and test old/new key acceptance according to supported Salesforce settings. Verification: Check metadata update, active certificate fingerprint, error codes and rollback path. Boundary: A successful identity-provider change does not guarantee relying applications automatically trust the replacement key.
  3. Action: Distinguish identity assertions from API authorization grants and use a suitable authenticated identity protocol when user login is required. Verification: Test first login, required attributes, inactive status, license assignment and onboarding delay. Boundary: A successful identity-provider change does not guarantee relying applications automatically trust the replacement key.
  4. Action: Validate audience restriction, entity IDs, assertion recipient and ACS address as a matched trust configuration. Verification: Check metadata update, active certificate fingerprint, error codes and rollback path. Boundary: Different SAML initiation patterns cannot be assumed to produce identical request validation and RelayState behavior.

Explanation

Correct Answer

B:

“Action: Coordinate trusted certificate rotation and test old/new key acceptance according to supported Salesforce settings. Verification: Check metadata update, active certificate fingerprint, error codes and rollback path. Boundary: A successful identity-provider change does not guarantee relying applications automatically trust the replacement key” addresses the access-design responsibilities in an acquired subsidiary switches its federation certificate without a coordinated rollover window Test against check metadata update, active certificate fingerprint, error codes and rollback path; a successful identity-provider change does not guarantee relying applications automatically trust the replacement key.

Incorrect Answers

A:

“Action: Coordinate trusted certificate rotation and test old/new key acceptance according to supported Salesforce settings. Verification: Compare HR events, directory account changes, Salesforce active status and delayed sync recovery. Boundary: Sign-in-triggered changes alone cannot guarantee off-session user lifecycle compliance” may apply to a related identity task, but it does not establish check metadata update, active certificate fingerprint, error codes and rollback path for an acquired subsidiary switches its federation certificate without a coordinated rollover window The controlling boundary is: A successful identity-provider change does not guarantee relying applications automatically trust the replacement key.

C:

“Action: Distinguish identity assertions from API authorization grants and use a suitable authenticated identity protocol when user login is required. Verification: Test first login, required attributes, inactive status, license assignment and onboarding delay. Boundary: A successful identity-provider change does not guarantee relying applications automatically trust the replacement key” may apply to a related identity task, but it does not establish check metadata update, active certificate fingerprint, error codes and rollback path for an acquired subsidiary switches its federation certificate without a coordinated rollover window The controlling boundary is: A successful identity-provider change does not guarantee relying applications automatically trust the replacement key.

D:

“Action: Validate audience restriction, entity IDs, assertion recipient and ACS address as a matched trust configuration. Verification: Check metadata update, active certificate fingerprint, error codes and rollback path. Boundary: Different SAML initiation patterns cannot be assumed to produce identical request validation and RelayState behavior” may apply to a related identity task, but it does not establish check metadata update, active certificate fingerprint, error codes and rollback path for an acquired subsidiary switches its federation certificate without a coordinated rollover window The controlling boundary is: A successful identity-provider change does not guarantee relying applications automatically trust the replacement key.

Question 113

A business renames My Domain while third-party sign-in bookmarks still target its old URL. Best next IAM response?

  1. Separate authentication, authorization and accountability responsibilities before selecting the federation pattern
  2. Use a stable unique federation subject mapping and plan conflict-safe account matching
  3. Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements
  4. Plan domain and redirect URI migration across identity providers and supported Salesforce endpoints

Explanation

Correct Answer

D:

“Plan domain and redirect URI migration across identity providers and supported Salesforce endpoints” addresses the access-design responsibilities in a business renames My Domain while third-party sign-in bookmarks still target its old URL Test against inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover; a branding or domain change can break authentication even when user credentials and permissions have not changed.

Incorrect Answers

A:

“Separate authentication, authorization and accountability responsibilities before selecting the federation pattern” may apply to a related identity task, but it does not establish inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover for a business renames My Domain while third-party sign-in bookmarks still target its old URL The controlling boundary is: A branding or domain change can break authentication even when user credentials and permissions have not changed.

B:

“Use a stable unique federation subject mapping and plan conflict-safe account matching” may apply to a related identity task, but it does not establish inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover for a business renames My Domain while third-party sign-in bookmarks still target its old URL The controlling boundary is: A branding or domain change can break authentication even when user credentials and permissions have not changed.

C:

“Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements” may apply to a related identity task, but it does not establish inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover for a business renames My Domain while third-party sign-in bookmarks still target its old URL The controlling boundary is: A branding or domain change can break authentication even when user credentials and permissions have not changed.

Question 114

A business renames My Domain while third-party sign-in bookmarks still target its old URL. Most decisive verification?

  1. Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover
  2. Verify provisioning feed events, assignment mapping, timing and reconciliation of failures
  3. Map credential issuer, application permission owner and traceable audit events for each relying system
  4. Review relying-party requirements, scopes, claims, token audiences and redirect flow

Explanation

Correct Answer

A:

“Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover” distinguishes sign-in from entitlement administration in a business renames My Domain while third-party sign-in bookmarks still target its old URL It checks whether plan domain and redirect URI migration across identity providers and supported Salesforce endpoints.

Incorrect Answers

B:

“Verify provisioning feed events, assignment mapping, timing and reconciliation of failures” needs to be evaluated against A business renames My Domain while third-party sign-in bookmarks still target its old URL. The relevant check is Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover; A branding or domain change can break authentication even when user credentials and permissions have not changed.

C:

“Map credential issuer, application permission owner and traceable audit events for each relying system” needs to be evaluated against A business renames My Domain while third-party sign-in bookmarks still target its old URL. The relevant check is Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover; A branding or domain change can break authentication even when user credentials and permissions have not changed.

D:

“Review relying-party requirements, scopes, claims, token audiences and redirect flow” needs to be evaluated against A business renames My Domain while third-party sign-in bookmarks still target its old URL. The relevant check is Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover; A branding or domain change can break authentication even when user credentials and permissions have not changed.

Question 115

A business renames My Domain while third-party sign-in bookmarks still target its old URL. Key caution for this case?

  1. A successful identity-provider change does not guarantee relying applications automatically trust the replacement key
  2. A protocol supported by the identity provider is insufficient if the relying application cannot validate it
  3. A branding or domain change can break authentication even when user credentials and permissions have not changed
  4. Even a correctly authenticated external subject must not gain access to another tenant's records by default

Explanation

Correct Answer

C:

“A branding or domain change can break authentication even when user credentials and permissions have not changed” needs to be evaluated against A business renames My Domain while third-party sign-in bookmarks still target its old URL. The relevant check is Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover; A branding or domain change can break authentication even when user credentials and permissions have not changed.

Incorrect Answers

A:

“A successful identity-provider change does not guarantee relying applications automatically trust the replacement key” needs to be evaluated against A business renames My Domain while third-party sign-in bookmarks still target its old URL. The relevant check is Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover; A branding or domain change can break authentication even when user credentials and permissions have not changed.

B:

“A protocol supported by the identity provider is insufficient if the relying application cannot validate it” needs to be evaluated against A business renames My Domain while third-party sign-in bookmarks still target its old URL. The relevant check is Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover; A branding or domain change can break authentication even when user credentials and permissions have not changed.

D:

“Even a correctly authenticated external subject must not gain access to another tenant's records by default” needs to be evaluated against A business renames My Domain while third-party sign-in bookmarks still target its old URL. The relevant check is Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover; A branding or domain change can break authentication even when user credentials and permissions have not changed.

Question 116

A business renames My Domain while third-party sign-in bookmarks still target its old URL. Best complete IAM decision record?

  1. Action: Plan domain and redirect URI migration across identity providers and supported Salesforce endpoints. Verification: Verify provisioning feed events, assignment mapping, timing and reconciliation of failures. Boundary: Even a correctly authenticated external subject must not gain access to another tenant's records by default.
  2. Action: Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements. Verification: Review relying-party requirements, scopes, claims, token audiences and redirect flow. Boundary: A branding or domain change can break authentication even when user credentials and permissions have not changed.
  3. Action: Plan domain and redirect URI migration across identity providers and supported Salesforce endpoints. Verification: Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover. Boundary: A branding or domain change can break authentication even when user credentials and permissions have not changed.
  4. Action: Separate authentication, authorization and accountability responsibilities before selecting the federation pattern. Verification: Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover. Boundary: A successful identity-provider change does not guarantee relying applications automatically trust the replacement key.

Explanation

Correct Answer

C:

“Action: Plan domain and redirect URI migration across identity providers and supported Salesforce endpoints. Verification: Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover. Boundary: A branding or domain change can break authentication even when user credentials and permissions have not changed” addresses the access-design responsibilities in a business renames My Domain while third-party sign-in bookmarks still target its old URL Test against inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover; a branding or domain change can break authentication even when user credentials and permissions have not changed.

Incorrect Answers

A:

“Action: Plan domain and redirect URI migration across identity providers and supported Salesforce endpoints. Verification: Verify provisioning feed events, assignment mapping, timing and reconciliation of failures. Boundary: Even a correctly authenticated external subject must not gain access to another tenant's records by default” may apply to a related identity task, but it does not establish inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover for a business renames My Domain while third-party sign-in bookmarks still target its old URL The controlling boundary is: A branding or domain change can break authentication even when user credentials and permissions have not changed.

B:

“Action: Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements. Verification: Review relying-party requirements, scopes, claims, token audiences and redirect flow. Boundary: A branding or domain change can break authentication even when user credentials and permissions have not changed” may apply to a related identity task, but it does not establish inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover for a business renames My Domain while third-party sign-in bookmarks still target its old URL The controlling boundary is: A branding or domain change can break authentication even when user credentials and permissions have not changed.

D:

“Action: Separate authentication, authorization and accountability responsibilities before selecting the federation pattern. Verification: Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover. Boundary: A successful identity-provider change does not guarantee relying applications automatically trust the replacement key” may apply to a related identity task, but it does not establish inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover for a business renames My Domain while third-party sign-in bookmarks still target its old URL The controlling boundary is: A branding or domain change can break authentication even when user credentials and permissions have not changed.

Question 117

A firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly. Best next IAM response?

  1. Plan domain and redirect URI migration across identity providers and supported Salesforce endpoints
  2. Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements
  3. Separate authentication, authorization and accountability responsibilities before selecting the federation pattern
  4. Use a stable unique federation subject mapping and plan conflict-safe account matching

Explanation

Correct Answer

A:

“Plan domain and redirect URI migration across identity providers and supported Salesforce endpoints” addresses the access-design responsibilities in a firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly Test against inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover; a branding or domain change can break authentication even when user credentials and permissions have not changed.

Incorrect Answers

B:

“Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements” may apply to a related identity task, but it does not establish inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover for a firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly The controlling boundary is: A branding or domain change can break authentication even when user credentials and permissions have not changed.

C:

“Separate authentication, authorization and accountability responsibilities before selecting the federation pattern” may apply to a related identity task, but it does not establish inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover for a firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly The controlling boundary is: A branding or domain change can break authentication even when user credentials and permissions have not changed.

D:

“Use a stable unique federation subject mapping and plan conflict-safe account matching” may apply to a related identity task, but it does not establish inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover for a firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly The controlling boundary is: A branding or domain change can break authentication even when user credentials and permissions have not changed.

Question 118

A firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly. Most decisive verification?

  1. Review relying-party requirements, scopes, claims, token audiences and redirect flow
  2. Verify provisioning feed events, assignment mapping, timing and reconciliation of failures
  3. Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover
  4. Map credential issuer, application permission owner and traceable audit events for each relying system

Explanation

Correct Answer

C:

“Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover” distinguishes sign-in from entitlement administration in a firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly It checks whether plan domain and redirect URI migration across identity providers and supported Salesforce endpoints.

Incorrect Answers

A:

“Review relying-party requirements, scopes, claims, token audiences and redirect flow” needs to be evaluated against A firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly. The relevant check is Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover; A branding or domain change can break authentication even when user credentials and permissions have not changed.

B:

“Verify provisioning feed events, assignment mapping, timing and reconciliation of failures” needs to be evaluated against A firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly. The relevant check is Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover; A branding or domain change can break authentication even when user credentials and permissions have not changed.

D:

“Map credential issuer, application permission owner and traceable audit events for each relying system” needs to be evaluated against A firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly. The relevant check is Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover; A branding or domain change can break authentication even when user credentials and permissions have not changed.

Question 119

A firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly. Key caution for this case?

  1. Even a correctly authenticated external subject must not gain access to another tenant's records by default
  2. A successful identity-provider change does not guarantee relying applications automatically trust the replacement key
  3. A protocol supported by the identity provider is insufficient if the relying application cannot validate it
  4. A branding or domain change can break authentication even when user credentials and permissions have not changed

Explanation

Correct Answer

D:

“A branding or domain change can break authentication even when user credentials and permissions have not changed” needs to be evaluated against A firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly. The relevant check is Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover; A branding or domain change can break authentication even when user credentials and permissions have not changed.

Incorrect Answers

A:

“Even a correctly authenticated external subject must not gain access to another tenant's records by default” needs to be evaluated against A firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly. The relevant check is Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover; A branding or domain change can break authentication even when user credentials and permissions have not changed.

B:

“A successful identity-provider change does not guarantee relying applications automatically trust the replacement key” needs to be evaluated against A firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly. The relevant check is Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover; A branding or domain change can break authentication even when user credentials and permissions have not changed.

C:

“A protocol supported by the identity provider is insufficient if the relying application cannot validate it” needs to be evaluated against A firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly. The relevant check is Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover; A branding or domain change can break authentication even when user credentials and permissions have not changed.

Question 120

A firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly. Best complete IAM decision record?

  1. Action: Plan domain and redirect URI migration across identity providers and supported Salesforce endpoints. Verification: Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover. Boundary: A branding or domain change can break authentication even when user credentials and permissions have not changed.
  2. Action: Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements. Verification: Review relying-party requirements, scopes, claims, token audiences and redirect flow. Boundary: A branding or domain change can break authentication even when user credentials and permissions have not changed.
  3. Action: Plan domain and redirect URI migration across identity providers and supported Salesforce endpoints. Verification: Verify provisioning feed events, assignment mapping, timing and reconciliation of failures. Boundary: Even a correctly authenticated external subject must not gain access to another tenant's records by default.
  4. Action: Separate authentication, authorization and accountability responsibilities before selecting the federation pattern. Verification: Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover. Boundary: A successful identity-provider change does not guarantee relying applications automatically trust the replacement key.

Explanation

Correct Answer

A:

“Action: Plan domain and redirect URI migration across identity providers and supported Salesforce endpoints. Verification: Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover. Boundary: A branding or domain change can break authentication even when user credentials and permissions have not changed” addresses the access-design responsibilities in a firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly Test against inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover; a branding or domain change can break authentication even when user credentials and permissions have not changed.

Incorrect Answers

B:

“Action: Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements. Verification: Review relying-party requirements, scopes, claims, token audiences and redirect flow. Boundary: A branding or domain change can break authentication even when user credentials and permissions have not changed” may apply to a related identity task, but it does not establish inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover for a firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly The controlling boundary is: A branding or domain change can break authentication even when user credentials and permissions have not changed.

C:

“Action: Plan domain and redirect URI migration across identity providers and supported Salesforce endpoints. Verification: Verify provisioning feed events, assignment mapping, timing and reconciliation of failures. Boundary: Even a correctly authenticated external subject must not gain access to another tenant's records by default” may apply to a related identity task, but it does not establish inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover for a firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly The controlling boundary is: A branding or domain change can break authentication even when user credentials and permissions have not changed.

D:

“Action: Separate authentication, authorization and accountability responsibilities before selecting the federation pattern. Verification: Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover. Boundary: A successful identity-provider change does not guarantee relying applications automatically trust the replacement key” may apply to a related identity task, but it does not establish inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover for a firm changes its Experience Cloud authentication hostname and expects external identity providers to keep redirecting correctly The controlling boundary is: A branding or domain change can break authentication even when user credentials and permissions have not changed.

Certified Platform Identity and Access Management Architect Practice Tests