McAfee-Secured Website

Exam Code: Certified Platform Identity and Access Management Architect

Exam Name: Certified Platform Identity and Access Management Architect

Certification Provider: Salesforce

100% Salesforce Certified Platform Identity and Access Management Architect Guaranteed Success With Testking Training Materials

Get Real Certified Platform Identity and Access Management Architect Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

58 Questions & Answers with Testing Engine

"Certified Platform Identity and Access Management Architect Exam", also known as Certified Platform Identity and Access Management Architect exam, is a Salesforce certification exam.

Pass your tests with the always up-to-date Certified Platform Identity and Access Management Architect Exam Engine. Your Certified Platform Identity and Access Management Architect training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Salesforce Certified Platform Identity and Access Management Architect Practice Test 3

Question 0020 — Identity Management Concepts

At fictional Pinehaven Commerce 02B, the team managing enterprise federation portal reports: After an enterprise directory upgrade, signed SAML responses arrive several minutes outside their assertion validity windows and users see intermittent authentication failures. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Test federation mappings with alias, rename and duplicate-name cases before production rollouts.
  2. Audit tenant-scoped identity crosswalks before each organizational directory consolidation.
  3. Review conditional access rules against known location/device test cases during policy releases.
  4. Monitor NTP drift and assertion-validity rejection rates during identity-provider upgrades.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Monitor NTP drift and assertion-validity rejection rates during identity-provider upgrades. This recurring control addresses the observed problem: After an enterprise directory upgrade, signed SAML responses arrive several minutes outside their assertion validity windows and users see intermittent authentication failures. The measurable check is: Compare failed assertion timestamps with trusted UTC logs and complete a successful time-bounded end-to-end SSO test.

Incorrect Answers

A:

Test federation mappings with alias, rename and duplicate-name cases before production rollouts. Monitor NTP drift and assertion-validity rejection rates during identity-provider upgrades.

B:

Audit tenant-scoped identity crosswalks before each organizational directory consolidation. Monitor NTP drift and assertion-validity rejection rates during identity-provider upgrades.

C:

Review conditional access rules against known location/device test cases during policy releases. Monitor NTP drift and assertion-validity rejection rates during identity-provider upgrades.

Question 0021 — Identity Management Concepts

At fictional North Lake Financial 03A, the team managing enterprise federation portal reports: A design team treats an OAuth access token as proof of a human user's identity when connecting a new external portal. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Separate OAuth delegated API authorization from OIDC authentication and validate an appropriately issued ID token when user identity is required.
  2. Coordinate signing certificate rollover between the IdP and all service providers using a published trust-change window and rollback.
  3. Model access-token expiry separately from refresh-token invalidation and enforce resource-server lifetime and revocation policies.
  4. Identify the active federation discovery and SSO endpoints for each business-unit policy and retire stale routing entries deliberately.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Separate OAuth delegated API authorization from OIDC authentication and validate an appropriately issued ID token when user identity is required. Demonstrate that the portal checks ID-token issuer, audience, signature and nonce while API calls use audience-scoped access tokens.

Incorrect Answers

B:

Coordinate signing certificate rollover between the IdP and all service providers using a published trust-change window and rollback. The needed correction is to separate OAuth delegated API authorization from OIDC authentication and validate an appropriately issued ID token when user identity is required.

C:

Model access-token expiry separately from refresh-token invalidation and enforce resource-server lifetime and revocation policies. The needed correction is to separate OAuth delegated API authorization from OIDC authentication and validate an appropriately issued ID token when user identity is required.

D:

Identify the active federation discovery and SSO endpoints for each business-unit policy and retire stale routing entries deliberately. The needed correction is to separate OAuth delegated API authorization from OIDC authentication and validate an appropriately issued ID token when user identity is required.

Question 0022 — Identity Management Concepts

At fictional North Lake Financial 03A, the team managing enterprise federation portal reports: A design team treats an OAuth access token as proof of a human user's identity when connecting a new external portal. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Confirm a new authorized employee receives exactly one correctly mapped user and a separated employee is denied.
  2. Demonstrate that the portal checks ID-token issuer, audience, signature and nonce while API calls use audience-scoped access tokens.
  3. Inspect a failing SAML assertion against the user federation field and confirm aliases no longer affect account lookup.
  4. Match IdP decision logs to Salesforce login history for allowed and blocked device/location combinations.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Demonstrate that the portal checks ID-token issuer, audience, signature and nonce while API calls use audience-scoped access tokens. The corresponding correction is to separate OAuth delegated API authorization from OIDC authentication and validate an appropriately issued ID token when user identity is required.

Incorrect Answers

A:

Confirm a new authorized employee receives exactly one correctly mapped user and a separated employee is denied. The useful check here is whether demonstrate that the portal checks ID-token issuer, audience, signature and nonce while API calls use audience-scoped access tokens.

C:

Inspect a failing SAML assertion against the user federation field and confirm aliases no longer affect account lookup. The useful check here is whether demonstrate that the portal checks ID-token issuer, audience, signature and nonce while API calls use audience-scoped access tokens.

D:

Match IdP decision logs to Salesforce login history for allowed and blocked device/location combinations. The useful check here is whether demonstrate that the portal checks ID-token issuer, audience, signature and nonce while API calls use audience-scoped access tokens.

Question 0023 — Identity Management Concepts

At fictional North Lake Financial 03A, the team managing enterprise federation portal reports: A design team treats an OAuth access token as proof of a human user's identity when connecting a new external portal. Which security architecture principle most directly explains the remediation needed for these facts?

  1. Authentication of a principal does not itself create or authorize an appropriate local account.
  2. Principal uniqueness must be preserved across organizational boundaries and mergers.
  3. OAuth and OpenID Connect provide different guarantees for resource authorization and authenticated user identity.
  4. Authentication sessions, application cookies and OAuth grants have different termination semantics.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

OAuth and OpenID Connect provide different guarantees for resource authorization and authenticated user identity. Demonstrate that the portal checks ID-token issuer, audience, signature and nonce while API calls use audience-scoped access tokens.

Incorrect Answers

A:

Authentication of a principal does not itself create or authorize an appropriate local account. OAuth and OpenID Connect provide different guarantees for resource authorization and authenticated user identity.

B:

Principal uniqueness must be preserved across organizational boundaries and mergers. OAuth and OpenID Connect provide different guarantees for resource authorization and authenticated user identity.

D:

Authentication sessions, application cookies and OAuth grants have different termination semantics. OAuth and OpenID Connect provide different guarantees for resource authorization and authenticated user identity.

Question 0024 — Identity Management Concepts

At fictional North Lake Financial 03A, the team managing enterprise federation portal reports: A design team treats an OAuth access token as proof of a human user's identity when connecting a new external portal. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. Ambiguous NameID mapping can cause account mismatches and inconsistent access between users.
  2. Cross-environment audience confusion can block login or create token acceptance risks.
  3. Users may believe all access ended while independently held sessions remain valid.
  4. Confusing token purposes allows token substitution and unsupported login conclusions.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Confusing token purposes allows token substitution and unsupported login conclusions. Separate OAuth delegated API authorization from OIDC authentication and validate an appropriately issued ID token when user identity is required.

Incorrect Answers

A:

Ambiguous NameID mapping can cause account mismatches and inconsistent access between users. Confusing token purposes allows token substitution and unsupported login conclusions.

B:

Cross-environment audience confusion can block login or create token acceptance risks. Confusing token purposes allows token substitution and unsupported login conclusions.

C:

Users may believe all access ended while independently held sessions remain valid. Confusing token purposes allows token substitution and unsupported login conclusions.

Question 0025 — Identity Management Concepts

At fictional North Lake Financial 03A, the team managing enterprise federation portal reports: A design team treats an OAuth access token as proof of a human user's identity when connecting a new external portal. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Require an architecture checkpoint that documents token type, issuer, audience and validation for every trust boundary.
  2. Reconcile permission assignments to authoritative role events on a recurring least-privilege review.
  3. Audit tenant-scoped identity crosswalks before each organizational directory consolidation.
  4. Run quarterly joiner-mover-leaver end-to-end tests across key applications and connectors.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Require an architecture checkpoint that documents token type, issuer, audience and validation for every trust boundary. This recurring control addresses the observed problem: A design team treats an OAuth access token as proof of a human user's identity when connecting a new external portal. The measurable check is: Demonstrate that the portal checks ID-token issuer, audience, signature and nonce while API calls use audience-scoped access tokens.

Incorrect Answers

B:

Reconcile permission assignments to authoritative role events on a recurring least-privilege review. Require an architecture checkpoint that documents token type, issuer, audience and validation for every trust boundary.

C:

Audit tenant-scoped identity crosswalks before each organizational directory consolidation. Require an architecture checkpoint that documents token type, issuer, audience and validation for every trust boundary.

D:

Run quarterly joiner-mover-leaver end-to-end tests across key applications and connectors. Require an architecture checkpoint that documents token type, issuer, audience and validation for every trust boundary.

Question 0026 — Identity Management Concepts

At fictional Asterline Education 03B, the team managing workforce access gateway reports: A design team treats an OAuth access token as proof of a human user's identity when connecting a new external portal. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Choose governed pre-provisioning or approved just-in-time provisioning and bind the incoming federation subject to a correctly licensed user.
  2. Separate OAuth delegated API authorization from OIDC authentication and validate an appropriately issued ID token when user identity is required.
  3. Namespace workforce subjects by authoritative directory/tenant and maintain immutable crosswalk mappings instead of merging unrelated identifiers.
  4. Document which sessions support coordinated logout and separately revoke tokens or terminate sessions where product capabilities require it.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Separate OAuth delegated API authorization from OIDC authentication and validate an appropriately issued ID token when user identity is required. Demonstrate that the portal checks ID-token issuer, audience, signature and nonce while API calls use audience-scoped access tokens.

Incorrect Answers

A:

Choose governed pre-provisioning or approved just-in-time provisioning and bind the incoming federation subject to a correctly licensed user. The needed correction is to separate OAuth delegated API authorization from OIDC authentication and validate an appropriately issued ID token when user identity is required.

C:

Namespace workforce subjects by authoritative directory/tenant and maintain immutable crosswalk mappings instead of merging unrelated identifiers. The needed correction is to separate OAuth delegated API authorization from OIDC authentication and validate an appropriately issued ID token when user identity is required.

D:

Document which sessions support coordinated logout and separately revoke tokens or terminate sessions where product capabilities require it. The needed correction is to separate OAuth delegated API authorization from OIDC authentication and validate an appropriately issued ID token when user identity is required.

Question 0027 — Identity Management Concepts

At fictional Asterline Education 03B, the team managing workforce access gateway reports: A design team treats an OAuth access token as proof of a human user's identity when connecting a new external portal. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Inspect a failing SAML assertion against the user federation field and confirm aliases no longer affect account lookup.
  2. Compare audience and ACS URLs in assertion traces with the production configuration and confirm sandbox assertions fail in production.
  3. Demonstrate that the portal checks ID-token issuer, audience, signature and nonce while API calls use audience-scoped access tokens.
  4. Prove browser logout and API token state individually across each connected app without implying universal session invalidation.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Demonstrate that the portal checks ID-token issuer, audience, signature and nonce while API calls use audience-scoped access tokens. The corresponding correction is to separate OAuth delegated API authorization from OIDC authentication and validate an appropriately issued ID token when user identity is required.

Incorrect Answers

A:

Inspect a failing SAML assertion against the user federation field and confirm aliases no longer affect account lookup. The useful check here is whether demonstrate that the portal checks ID-token issuer, audience, signature and nonce while API calls use audience-scoped access tokens.

B:

Compare audience and ACS URLs in assertion traces with the production configuration and confirm sandbox assertions fail in production. The useful check here is whether demonstrate that the portal checks ID-token issuer, audience, signature and nonce while API calls use audience-scoped access tokens.

D:

Prove browser logout and API token state individually across each connected app without implying universal session invalidation. The useful check here is whether demonstrate that the portal checks ID-token issuer, audience, signature and nonce while API calls use audience-scoped access tokens.

Question 0028 — Identity Management Concepts

At fictional Asterline Education 03B, the team managing workforce access gateway reports: A design team treats an OAuth access token as proof of a human user's identity when connecting a new external portal. Which security architecture principle most directly explains the remediation needed for these facts?

  1. Identity synchronization and authorization lifecycle must remain aligned but are distinct operations.
  2. Principal uniqueness must be preserved across organizational boundaries and mergers.
  3. Identity lifecycle accountability must cover all downstream accounts rather than a single service provider.
  4. OAuth and OpenID Connect provide different guarantees for resource authorization and authenticated user identity.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

OAuth and OpenID Connect provide different guarantees for resource authorization and authenticated user identity. Demonstrate that the portal checks ID-token issuer, audience, signature and nonce while API calls use audience-scoped access tokens.

Incorrect Answers

A:

Identity synchronization and authorization lifecycle must remain aligned but are distinct operations. OAuth and OpenID Connect provide different guarantees for resource authorization and authenticated user identity.

B:

Principal uniqueness must be preserved across organizational boundaries and mergers. OAuth and OpenID Connect provide different guarantees for resource authorization and authenticated user identity.

C:

Identity lifecycle accountability must cover all downstream accounts rather than a single service provider. OAuth and OpenID Connect provide different guarantees for resource authorization and authenticated user identity.

Question 0029 — Identity Management Concepts

At fictional Asterline Education 03B, the team managing workforce access gateway reports: A design team treats an OAuth access token as proof of a human user's identity when connecting a new external portal. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. Confusing token purposes allows token substitution and unsupported login conclusions.
  2. Cross-environment audience confusion can block login or create token acceptance risks.
  3. An unqualified identifier collision can merge audit trails or grant one worker another worker's access.
  4. Changing unrelated passwords can hide misapplied conditional access or leave prohibited sessions accessible.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Confusing token purposes allows token substitution and unsupported login conclusions. Separate OAuth delegated API authorization from OIDC authentication and validate an appropriately issued ID token when user identity is required.

Incorrect Answers

B:

Cross-environment audience confusion can block login or create token acceptance risks. Confusing token purposes allows token substitution and unsupported login conclusions.

C:

An unqualified identifier collision can merge audit trails or grant one worker another worker's access. Confusing token purposes allows token substitution and unsupported login conclusions.

D:

Changing unrelated passwords can hide misapplied conditional access or leave prohibited sessions accessible. Confusing token purposes allows token substitution and unsupported login conclusions.

Question 0030 — Identity Management Concepts

At fictional Asterline Education 03B, the team managing workforce access gateway reports: A design team treats an OAuth access token as proof of a human user's identity when connecting a new external portal. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Run recurring directory-to-Salesforce identifier collision and reuse reviews before enabling new federation partners.
  2. Require an architecture checkpoint that documents token type, issuer, audience and validation for every trust boundary.
  3. Monitor NTP drift and assertion-validity rejection rates during identity-provider upgrades.
  4. Include production-versus-sandbox audience checks in automated SSO regression cases.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Require an architecture checkpoint that documents token type, issuer, audience and validation for every trust boundary. This recurring control addresses the observed problem: A design team treats an OAuth access token as proof of a human user's identity when connecting a new external portal. The measurable check is: Demonstrate that the portal checks ID-token issuer, audience, signature and nonce while API calls use audience-scoped access tokens.

Incorrect Answers

A:

Run recurring directory-to-Salesforce identifier collision and reuse reviews before enabling new federation partners. Require an architecture checkpoint that documents token type, issuer, audience and validation for every trust boundary.

C:

Monitor NTP drift and assertion-validity rejection rates during identity-provider upgrades. Require an architecture checkpoint that documents token type, issuer, audience and validation for every trust boundary.

D:

Include production-versus-sandbox audience checks in automated SSO regression cases. Require an architecture checkpoint that documents token type, issuer, audience and validation for every trust boundary.

Certified Platform Identity and Access Management Architect Practice Tests