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 34

Question 0330 — Salesforce as an Identity Provider

At fictional Asterline Education 33B, the team managing external service identity reports: A public native mobile application uses an embedded password flow and stores a client secret in the distributed application binary. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Validate selected flow type against client capabilities and security requirements before deploying integrations.
  2. Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews.
  3. Test token type/audience separation at resource servers and connected-app boundaries.
  4. Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews. This recurring control addresses the observed problem: A public native mobile application uses an embedded password flow and stores a client secret in the distributed application binary. The measurable check is: Inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier.

Incorrect Answers

A:

Validate selected flow type against client capabilities and security requirements before deploying integrations. Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews.

C:

Test token type/audience separation at resource servers and connected-app boundaries. Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews.

D:

Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change. Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews.

Question 0331 — Salesforce as an Identity Provider

At fictional Oakridge Hospitality 34A, the team managing external service identity reports: A headless middleware service needs Salesforce API access without an interactive user, but its job stores a human employee's reusable password. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Use a server-side authorization code exchange with an approved redirect URI and secure backend token storage.
  2. Select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model.
  3. Evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization.
  4. Separate application registration and authorization policies by trust boundary, accountable owner and required data scope.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization. Demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope.

Incorrect Answers

A:

Use a server-side authorization code exchange with an approved redirect URI and secure backend token storage. The needed correction is to evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization.

B:

Select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model. The needed correction is to evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization.

D:

Separate application registration and authorization policies by trust boundary, accountable owner and required data scope. The needed correction is to evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization.

Question 0332 — Salesforce as an Identity Provider

At fictional Oakridge Hospitality 34A, the team managing external service identity reports: A headless middleware service needs Salesforce API access without an interactive user, but its job stores a human employee's reusable password. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations.
  2. Verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens.
  3. Trace a test callout using the approved credential principal with no reusable password in application code or logs.
  4. Demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope. The corresponding correction is to evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization.

Incorrect Answers

A:

Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations. The useful check here is whether demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope.

B:

Verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens. The useful check here is whether demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope.

C:

Trace a test callout using the approved credential principal with no reusable password in application code or logs. The useful check here is whether demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope.

Question 0333 — Salesforce as an Identity Provider

At fictional Oakridge Hospitality 34A, the team managing external service identity reports: A headless middleware service needs Salesforce API access without an interactive user, but its job stores a human employee's reusable password. Which security architecture principle most directly explains the remediation needed for these facts?

  1. Automated workload credentials should be independent of human interactive accounts and enforce least privilege.
  2. OAuth grants and application sessions require explicit revocation semantics separate from browser login state.
  3. Machine workloads should not emulate user-agent browser sessions to obtain unattended access.
  4. Identity assertions and resource access grants are separate token classes with different audiences and claims.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Automated workload credentials should be independent of human interactive accounts and enforce least privilege. Demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope.

Incorrect Answers

B:

OAuth grants and application sessions require explicit revocation semantics separate from browser login state. Automated workload credentials should be independent of human interactive accounts and enforce least privilege.

C:

Machine workloads should not emulate user-agent browser sessions to obtain unattended access. Automated workload credentials should be independent of human interactive accounts and enforce least privilege.

D:

Identity assertions and resource access grants are separate token classes with different audiences and claims. Automated workload credentials should be independent of human interactive accounts and enforce least privilege.

Question 0334 — Salesforce as an Identity Provider

At fictional Oakridge Hospitality 34A, the team managing external service identity reports: A headless middleware service needs Salesforce API access without an interactive user, but its job stores a human employee's reusable password. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. Misapplied browser flows create fragile token handling and unreviewed privileges in batch jobs.
  2. Reusing an employee password creates outages and untraceable automation when employment status changes.
  3. Loose redirect validation can leak authorization codes to unintended recipients.
  4. Stale issuer acceptance can create federation outages or preserve obsolete trust paths.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Reusing an employee password creates outages and untraceable automation when employment status changes. Evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization.

Incorrect Answers

A:

Misapplied browser flows create fragile token handling and unreviewed privileges in batch jobs. Reusing an employee password creates outages and untraceable automation when employment status changes.

C:

Loose redirect validation can leak authorization codes to unintended recipients. Reusing an employee password creates outages and untraceable automation when employment status changes.

D:

Stale issuer acceptance can create federation outages or preserve obsolete trust paths. Reusing an employee password creates outages and untraceable automation when employment status changes.

Question 0335 — Salesforce as an Identity Provider

At fictional Oakridge Hospitality 34A, the team managing external service identity reports: A headless middleware service needs Salesforce API access without an interactive user, but its job stores a human employee's reusable password. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Test token type/audience separation at resource servers and connected-app boundaries.
  2. Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change.
  3. Rotate integration credentials and review non-interactive principal scope during service ownership changes.
  4. Review outbound callout credential mappings and principal permissions on a schedule.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Rotate integration credentials and review non-interactive principal scope during service ownership changes. This recurring control addresses the observed problem: A headless middleware service needs Salesforce API access without an interactive user, but its job stores a human employee's reusable password. The measurable check is: Demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope.

Incorrect Answers

A:

Test token type/audience separation at resource servers and connected-app boundaries. Rotate integration credentials and review non-interactive principal scope during service ownership changes.

B:

Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change. Rotate integration credentials and review non-interactive principal scope during service ownership changes.

D:

Review outbound callout credential mappings and principal permissions on a schedule. Rotate integration credentials and review non-interactive principal scope during service ownership changes.

Question 0336 — Salesforce as an Identity Provider

At fictional Lighthouse Nonprofit 34B, the team managing OAuth token lifecycle reports: A headless middleware service needs Salesforce API access without an interactive user, but its job stores a human employee's reusable password. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Explicitly review connected-app token revocation and user deactivation behavior, then revoke the affected OAuth grants under incident procedure.
  2. Select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model.
  3. Issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose.
  4. Evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization. Demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope.

Incorrect Answers

A:

Explicitly review connected-app token revocation and user deactivation behavior, then revoke the affected OAuth grants under incident procedure. The needed correction is to evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization.

B:

Select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model. The needed correction is to evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization.

C:

Issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose. The needed correction is to evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization.

Question 0337 — Salesforce as an Identity Provider

At fictional Lighthouse Nonprofit 34B, the team managing OAuth token lifecycle reports: A headless middleware service needs Salesforce API access without an interactive user, but its job stores a human employee's reusable password. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope.
  2. Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access.
  3. Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.
  4. Validate an updated signed assertion from the active Salesforce issuer and show the partner rejects deprecated issuer metadata.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope. The corresponding correction is to evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization.

Incorrect Answers

B:

Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access. The useful check here is whether demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope.

C:

Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery. The useful check here is whether demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope.

D:

Validate an updated signed assertion from the active Salesforce issuer and show the partner rejects deprecated issuer metadata. The useful check here is whether demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope.

Question 0338 — Salesforce as an Identity Provider

At fictional Lighthouse Nonprofit 34B, the team managing OAuth token lifecycle reports: A headless middleware service needs Salesforce API access without an interactive user, but its job stores a human employee's reusable password. Which security architecture principle most directly explains the remediation needed for these facts?

  1. Identity assertions and resource access grants are separate token classes with different audiences and claims.
  2. Automated workload credentials should be independent of human interactive accounts and enforce least privilege.
  3. Device-limited clients can delegate interactive approval to a separate secure authorization channel.
  4. API authentication should be abstracted behind managed credentials with explicit principal authorization.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Automated workload credentials should be independent of human interactive accounts and enforce least privilege. Demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope.

Incorrect Answers

A:

Identity assertions and resource access grants are separate token classes with different audiences and claims. Automated workload credentials should be independent of human interactive accounts and enforce least privilege.

C:

Device-limited clients can delegate interactive approval to a separate secure authorization channel. Automated workload credentials should be independent of human interactive accounts and enforce least privilege.

D:

API authentication should be abstracted behind managed credentials with explicit principal authorization. Automated workload credentials should be independent of human interactive accounts and enforce least privilege.

Question 0339 — Salesforce as an Identity Provider

At fictional Lighthouse Nonprofit 34B, the team managing OAuth token lifecycle reports: A headless middleware service needs Salesforce API access without an interactive user, but its job stores a human employee's reusable password. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. Password replication multiplies credential exposure and obscures authoritative identity governance.
  2. Exposed access tokens in browser code can be stolen and replayed by unauthorized parties.
  3. Reusing an employee password creates outages and untraceable automation when employment status changes.
  4. Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Reusing an employee password creates outages and untraceable automation when employment status changes. Evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization.

Incorrect Answers

A:

Password replication multiplies credential exposure and obscures authoritative identity governance. Reusing an employee password creates outages and untraceable automation when employment status changes.

B:

Exposed access tokens in browser code can be stolen and replayed by unauthorized parties. Reusing an employee password creates outages and untraceable automation when employment status changes.

D:

Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges. Reusing an employee password creates outages and untraceable automation when employment status changes.

Question 0340 — Salesforce as an Identity Provider

At fictional Lighthouse Nonprofit 34B, the team managing OAuth token lifecycle reports: A headless middleware service needs Salesforce API access without an interactive user, but its job stores a human employee's reusable password. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis.
  2. Periodically test redirect URI matching and review changes to connected-app callback lists.
  3. Reconcile registered apps, scopes and named owners to the enterprise application inventory.
  4. Rotate integration credentials and review non-interactive principal scope during service ownership changes.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Rotate integration credentials and review non-interactive principal scope during service ownership changes. This recurring control addresses the observed problem: A headless middleware service needs Salesforce API access without an interactive user, but its job stores a human employee's reusable password. The measurable check is: Demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope.

Incorrect Answers

A:

Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis. Rotate integration credentials and review non-interactive principal scope during service ownership changes.

B:

Periodically test redirect URI matching and review changes to connected-app callback lists. Rotate integration credentials and review non-interactive principal scope during service ownership changes.

C:

Reconcile registered apps, scopes and named owners to the enterprise application inventory. Rotate integration credentials and review non-interactive principal scope during service ownership changes.

Certified Platform Identity and Access Management Architect Practice Tests