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 44

Question 0430 — Salesforce as an Identity Provider

At fictional Asterline Education 43B, the team managing external service identity reports: An integration team places a shared static Salesforce password inside custom Named Credential metadata instead of using supported external credential principals. 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. Review outbound callout credential mappings and principal permissions on a schedule.
  3. Rotate integration credentials and review non-interactive principal scope during service ownership changes.
  4. Reapprove connected-app scope sets during each API integration feature expansion.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Review outbound callout credential mappings and principal permissions on a schedule. This recurring control addresses the observed problem: An integration team places a shared static Salesforce password inside custom Named Credential metadata instead of using supported external credential principals. The measurable check is: Trace a test callout using the approved credential principal with no reusable password in application code or logs.

Incorrect Answers

A:

Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis. Review outbound callout credential mappings and principal permissions on a schedule.

C:

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

D:

Reapprove connected-app scope sets during each API integration feature expansion. Review outbound callout credential mappings and principal permissions on a schedule.

Question 0431 — Salesforce as an Identity Provider

At fictional Oakridge Hospitality 44A, the team managing external service identity reports: After changing a Salesforce My Domain, a partner SAML service provider continues accepting assertions with the retired issuer entity identifier. 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. Restrict redirect URIs to exact approved values and reject unregistered or ambiguously normalized callback destinations.
  3. Reconcile Salesforce identity-provider issuer metadata and partner trust anchors before switching production federation endpoints.
  4. Prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Reconcile Salesforce identity-provider issuer metadata and partner trust anchors before switching production federation endpoints. Validate an updated signed assertion from the active Salesforce issuer and show the partner rejects deprecated issuer metadata.

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 reconcile Salesforce identity-provider issuer metadata and partner trust anchors before switching production federation endpoints.

B:

Restrict redirect URIs to exact approved values and reject unregistered or ambiguously normalized callback destinations. The needed correction is to reconcile Salesforce identity-provider issuer metadata and partner trust anchors before switching production federation endpoints.

D:

Prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment. The needed correction is to reconcile Salesforce identity-provider issuer metadata and partner trust anchors before switching production federation endpoints.

Question 0432 — Salesforce as an Identity Provider

At fictional Oakridge Hospitality 44A, the team managing external service identity reports: After changing a Salesforce My Domain, a partner SAML service provider continues accepting assertions with the retired issuer entity identifier. 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. Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.
  3. Trace a test callout using the approved credential principal with no reusable password in application code or logs.
  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

D:

Validate an updated signed assertion from the active Salesforce issuer and show the partner rejects deprecated issuer metadata. The corresponding correction is to reconcile Salesforce identity-provider issuer metadata and partner trust anchors before switching production federation endpoints.

Incorrect Answers

A:

Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations. The useful check here is whether validate an updated signed assertion from the active Salesforce issuer and show the partner rejects deprecated issuer metadata.

B:

Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds. The useful check here is whether validate an updated signed assertion from the active Salesforce issuer and show the partner rejects deprecated issuer metadata.

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 validate an updated signed assertion from the active Salesforce issuer and show the partner rejects deprecated issuer metadata.

Question 0433 — Salesforce as an Identity Provider

At fictional Oakridge Hospitality 44A, the team managing external service identity reports: After changing a Salesforce My Domain, a partner SAML service provider continues accepting assertions with the retired issuer entity identifier. Which security architecture principle most directly explains the remediation needed for these facts?

  1. Identity-provider continuity requires controlled metadata changes and relying-party trust verification.
  2. Machine workloads should not emulate user-agent browser sessions to obtain unattended access.
  3. Identity assertions and resource access grants are separate token classes with different audiences and claims.
  4. Device-limited clients can delegate interactive approval to a separate secure authorization channel.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Identity-provider continuity requires controlled metadata changes and relying-party trust verification. Validate an updated signed assertion from the active Salesforce issuer and show the partner rejects deprecated issuer metadata.

Incorrect Answers

B:

Machine workloads should not emulate user-agent browser sessions to obtain unattended access. Identity-provider continuity requires controlled metadata changes and relying-party trust verification.

C:

Identity assertions and resource access grants are separate token classes with different audiences and claims. Identity-provider continuity requires controlled metadata changes and relying-party trust verification.

D:

Device-limited clients can delegate interactive approval to a separate secure authorization channel. Identity-provider continuity requires controlled metadata changes and relying-party trust verification.

Question 0434 — Salesforce as an Identity Provider

At fictional Oakridge Hospitality 44A, the team managing external service identity reports: After changing a Salesforce My Domain, a partner SAML service provider continues accepting assertions with the retired issuer entity identifier. 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. Stale issuer acceptance can create federation outages or preserve obsolete trust paths.
  3. Extracted secrets and unbound codes create credential and authorization-code interception risks.
  4. Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Stale issuer acceptance can create federation outages or preserve obsolete trust paths. Reconcile Salesforce identity-provider issuer metadata and partner trust anchors before switching production federation endpoints.

Incorrect Answers

A:

Password replication multiplies credential exposure and obscures authoritative identity governance. Stale issuer acceptance can create federation outages or preserve obsolete trust paths.

C:

Extracted secrets and unbound codes create credential and authorization-code interception risks. Stale issuer acceptance can create federation outages or preserve obsolete trust paths.

D:

Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges. Stale issuer acceptance can create federation outages or preserve obsolete trust paths.

Question 0435 — Salesforce as an Identity Provider

At fictional Oakridge Hospitality 44A, the team managing external service identity reports: After changing a Salesforce My Domain, a partner SAML service provider continues accepting assertions with the retired issuer entity identifier. 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. Reapprove connected-app scope sets during each API integration feature expansion.
  3. Rehearse My Domain issuer and metadata rollovers with every external service provider.
  4. Review outbound callout credential mappings and principal permissions on a schedule.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Rehearse My Domain issuer and metadata rollovers with every external service provider. This recurring control addresses the observed problem: After changing a Salesforce My Domain, a partner SAML service provider continues accepting assertions with the retired issuer entity identifier. The measurable check is: Validate an updated signed assertion from the active Salesforce issuer and show the partner rejects deprecated issuer metadata.

Incorrect Answers

A:

Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis. Rehearse My Domain issuer and metadata rollovers with every external service provider.

B:

Reapprove connected-app scope sets during each API integration feature expansion. Rehearse My Domain issuer and metadata rollovers with every external service provider.

D:

Review outbound callout credential mappings and principal permissions on a schedule. Rehearse My Domain issuer and metadata rollovers with every external service provider.

Question 0436 — Salesforce as an Identity Provider

At fictional Lighthouse Nonprofit 44B, the team managing OAuth token lifecycle reports: After changing a Salesforce My Domain, a partner SAML service provider continues accepting assertions with the retired issuer entity identifier. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model.
  2. Issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose.
  3. Assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements.
  4. Reconcile Salesforce identity-provider issuer metadata and partner trust anchors before switching production federation endpoints.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Reconcile Salesforce identity-provider issuer metadata and partner trust anchors before switching production federation endpoints. Validate an updated signed assertion from the active Salesforce issuer and show the partner rejects deprecated issuer metadata.

Incorrect Answers

A:

Select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model. The needed correction is to reconcile Salesforce identity-provider issuer metadata and partner trust anchors before switching production federation endpoints.

B:

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 reconcile Salesforce identity-provider issuer metadata and partner trust anchors before switching production federation endpoints.

C:

Assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements. The needed correction is to reconcile Salesforce identity-provider issuer metadata and partner trust anchors before switching production federation endpoints.

Question 0437 — Salesforce as an Identity Provider

At fictional Lighthouse Nonprofit 44B, the team managing OAuth token lifecycle reports: After changing a Salesforce My Domain, a partner SAML service provider continues accepting assertions with the retired issuer entity identifier. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Validate an updated signed assertion from the active Salesforce issuer and show the partner rejects deprecated issuer metadata.
  2. Complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient.
  3. Inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier.
  4. Trace a test callout using the approved credential principal with no reusable password in application code or logs.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Validate an updated signed assertion from the active Salesforce issuer and show the partner rejects deprecated issuer metadata. The corresponding correction is to reconcile Salesforce identity-provider issuer metadata and partner trust anchors before switching production federation endpoints.

Incorrect Answers

B:

Complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient. The useful check here is whether validate an updated signed assertion from the active Salesforce issuer and show the partner rejects deprecated issuer metadata.

C:

Inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier. The useful check here is whether validate an updated signed assertion from the active Salesforce issuer and show the partner rejects deprecated issuer metadata.

D:

Trace a test callout using the approved credential principal with no reusable password in application code or logs. The useful check here is whether validate an updated signed assertion from the active Salesforce issuer and show the partner rejects deprecated issuer metadata.

Question 0438 — Salesforce as an Identity Provider

At fictional Lighthouse Nonprofit 44B, the team managing OAuth token lifecycle reports: After changing a Salesforce My Domain, a partner SAML service provider continues accepting assertions with the retired issuer entity identifier. Which security architecture principle most directly explains the remediation needed for these facts?

  1. Federation lets a trusted identity provider authenticate principals without sharing their passwords with relying applications.
  2. Identity-provider continuity requires controlled metadata changes and relying-party trust verification.
  3. OAuth scope and local user permissions both constrain what a delegated token may do.
  4. API authentication should be abstracted behind managed credentials with explicit principal authorization.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Identity-provider continuity requires controlled metadata changes and relying-party trust verification. Validate an updated signed assertion from the active Salesforce issuer and show the partner rejects deprecated issuer metadata.

Incorrect Answers

A:

Federation lets a trusted identity provider authenticate principals without sharing their passwords with relying applications. Identity-provider continuity requires controlled metadata changes and relying-party trust verification.

C:

OAuth scope and local user permissions both constrain what a delegated token may do. Identity-provider continuity requires controlled metadata changes and relying-party trust verification.

D:

API authentication should be abstracted behind managed credentials with explicit principal authorization. Identity-provider continuity requires controlled metadata changes and relying-party trust verification.

Question 0439 — Salesforce as an Identity Provider

At fictional Lighthouse Nonprofit 44B, the team managing OAuth token lifecycle reports: After changing a Salesforce My Domain, a partner SAML service provider continues accepting assertions with the retired issuer entity identifier. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. Extracted secrets and unbound codes create credential and authorization-code interception risks.
  2. Reusing an employee password creates outages and untraceable automation when employment status changes.
  3. Stale issuer acceptance can create federation outages or preserve obsolete trust paths.
  4. Overlooking long-lived refresh grants extends access beyond intended offboarding controls.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Stale issuer acceptance can create federation outages or preserve obsolete trust paths. Reconcile Salesforce identity-provider issuer metadata and partner trust anchors before switching production federation endpoints.

Incorrect Answers

A:

Extracted secrets and unbound codes create credential and authorization-code interception risks. Stale issuer acceptance can create federation outages or preserve obsolete trust paths.

B:

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

D:

Overlooking long-lived refresh grants extends access beyond intended offboarding controls. Stale issuer acceptance can create federation outages or preserve obsolete trust paths.

Question 0440 — Salesforce as an Identity Provider

At fictional Lighthouse Nonprofit 44B, the team managing OAuth token lifecycle reports: After changing a Salesforce My Domain, a partner SAML service provider continues accepting assertions with the retired issuer entity identifier. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews.
  2. Audit high-risk refresh grants and ensure leaver runbooks cover each connected app.
  3. Test token type/audience separation at resource servers and connected-app boundaries.
  4. Rehearse My Domain issuer and metadata rollovers with every external service provider.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Rehearse My Domain issuer and metadata rollovers with every external service provider. This recurring control addresses the observed problem: After changing a Salesforce My Domain, a partner SAML service provider continues accepting assertions with the retired issuer entity identifier. The measurable check is: Validate an updated signed assertion from the active Salesforce issuer and show the partner rejects deprecated issuer metadata.

Incorrect Answers

A:

Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews. Rehearse My Domain issuer and metadata rollovers with every external service provider.

B:

Audit high-risk refresh grants and ensure leaver runbooks cover each connected app. Rehearse My Domain issuer and metadata rollovers with every external service provider.

C:

Test token type/audience separation at resource servers and connected-app boundaries. Rehearse My Domain issuer and metadata rollovers with every external service provider.

Certified Platform Identity and Access Management Architect Practice Tests