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 35

Question 340

A headless internal report service authenticates under a controlled integration identity with signed key material. Best complete IAM decision record?

  1. Action: Evaluate a supported JWT bearer or service-oriented OAuth flow with strictly managed keys, audience and least privilege. Verification: Verify signed assertion claims, token audience, issuer binding, scope and key rotation. Boundary: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.
  2. Action: Apply app access policies, understandable consent and administrative approval for sensitive integrations. Verification: Test code verifier/challenge, redirect registration, user grant and token exchange. Boundary: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.
  3. Action: Plan new OAuth integrations with the external client app framework and confirm exception procedures only when genuinely needed. Verification: Verify signed assertion claims, token audience, issuer binding, scope and key rotation. Boundary: A public client cannot rely on an embedded long-term secret as a confidential client would.
  4. Action: Evaluate a supported JWT bearer or service-oriented OAuth flow with strictly managed keys, audience and least privilege. Verification: Compare supported release, SAML settings, service provider registration and permission assignments. Boundary: Salesforce can issue trusted SAML assertions only for applications and subjects registered in its identity provider trust configuration.

Explanation

Correct Answer

A:

“Action: Evaluate a supported JWT bearer or service-oriented OAuth flow with strictly managed keys, audience and least privilege. Verification: Verify signed assertion claims, token audience, issuer binding, scope and key rotation. Boundary: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy” addresses the access-design responsibilities in a headless internal report service authenticates under a controlled integration identity with signed key material Test against verify signed assertion claims, token audience, issuer binding, scope and key rotation; a JWT's signature alone does not authorize any user or resource outside the registered app and org policy.

Incorrect Answers

B:

“Action: Apply app access policies, understandable consent and administrative approval for sensitive integrations. Verification: Test code verifier/challenge, redirect registration, user grant and token exchange. Boundary: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy” may apply to a related identity task, but it does not establish verify signed assertion claims, token audience, issuer binding, scope and key rotation for a headless internal report service authenticates under a controlled integration identity with signed key material The controlling boundary is: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.

C:

“Action: Plan new OAuth integrations with the external client app framework and confirm exception procedures only when genuinely needed. Verification: Verify signed assertion claims, token audience, issuer binding, scope and key rotation. Boundary: A public client cannot rely on an embedded long-term secret as a confidential client would” may apply to a related identity task, but it does not establish verify signed assertion claims, token audience, issuer binding, scope and key rotation for a headless internal report service authenticates under a controlled integration identity with signed key material The controlling boundary is: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.

D:

“Action: Evaluate a supported JWT bearer or service-oriented OAuth flow with strictly managed keys, audience and least privilege. Verification: Compare supported release, SAML settings, service provider registration and permission assignments. Boundary: Salesforce can issue trusted SAML assertions only for applications and subjects registered in its identity provider trust configuration” may apply to a related identity task, but it does not establish verify signed assertion claims, token audience, issuer binding, scope and key rotation for a headless internal report service authenticates under a controlled integration identity with signed key material The controlling boundary is: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.

Question 341

An automated partner service is registered to exchange a signed assertion for limited Salesforce access without a human prompt. Best next IAM response?

  1. Apply app access policies, understandable consent and administrative approval for sensitive integrations
  2. Enable Salesforce as the identity provider and register the external service provider using supported SAML app configuration
  3. Evaluate a supported JWT bearer or service-oriented OAuth flow with strictly managed keys, audience and least privilege
  4. Plan new OAuth integrations with the external client app framework and confirm exception procedures only when genuinely needed

Explanation

Correct Answer

C:

“Evaluate a supported JWT bearer or service-oriented OAuth flow with strictly managed keys, audience and least privilege” addresses the access-design responsibilities in an automated partner service is registered to exchange a signed assertion for limited Salesforce access without a human prompt Test against verify signed assertion claims, token audience, issuer binding, scope and key rotation; a JWT's signature alone does not authorize any user or resource outside the registered app and org policy.

Incorrect Answers

A:

“Apply app access policies, understandable consent and administrative approval for sensitive integrations” may apply to a related identity task, but it does not establish verify signed assertion claims, token audience, issuer binding, scope and key rotation for an automated partner service is registered to exchange a signed assertion for limited Salesforce access without a human prompt The controlling boundary is: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.

B:

“Enable Salesforce as the identity provider and register the external service provider using supported SAML app configuration” may apply to a related identity task, but it does not establish verify signed assertion claims, token audience, issuer binding, scope and key rotation for an automated partner service is registered to exchange a signed assertion for limited Salesforce access without a human prompt The controlling boundary is: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.

D:

“Plan new OAuth integrations with the external client app framework and confirm exception procedures only when genuinely needed” may apply to a related identity task, but it does not establish verify signed assertion claims, token audience, issuer binding, scope and key rotation for an automated partner service is registered to exchange a signed assertion for limited Salesforce access without a human prompt The controlling boundary is: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.

Question 342

An automated partner service is registered to exchange a signed assertion for limited Salesforce access without a human prompt. Most decisive verification?

  1. Validate Salesforce IdP certificate, SP entity ID, ACS URL and authorized user assignments
  2. Test code verifier/challenge, redirect registration, user grant and token exchange
  3. Verify signed assertion claims, token audience, issuer binding, scope and key rotation
  4. Compare supported release, SAML settings, service provider registration and permission assignments

Explanation

Correct Answer

C:

“Verify signed assertion claims, token audience, issuer binding, scope and key rotation” distinguishes sign-in from entitlement administration in an automated partner service is registered to exchange a signed assertion for limited Salesforce access without a human prompt It checks whether evaluate a supported JWT bearer or service-oriented OAuth flow with strictly managed keys, audience and least privilege.

Incorrect Answers

A:

“Validate Salesforce IdP certificate, SP entity ID, ACS URL and authorized user assignments” needs to be evaluated against An automated partner service is registered to exchange a signed assertion for limited Salesforce access without a human prompt. The relevant check is Verify signed assertion claims, token audience, issuer binding, scope and key rotation; A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.

B:

“Test code verifier/challenge, redirect registration, user grant and token exchange” needs to be evaluated against An automated partner service is registered to exchange a signed assertion for limited Salesforce access without a human prompt. The relevant check is Verify signed assertion claims, token audience, issuer binding, scope and key rotation; A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.

D:

“Compare supported release, SAML settings, service provider registration and permission assignments” needs to be evaluated against An automated partner service is registered to exchange a signed assertion for limited Salesforce access without a human prompt. The relevant check is Verify signed assertion claims, token audience, issuer binding, scope and key rotation; A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.

Question 343

An automated partner service is registered to exchange a signed assertion for limited Salesforce access without a human prompt. Key caution for this case?

  1. A valid Salesforce user session does not authorize a SAML assertion for an unrelated target audience
  2. A JWT's signature alone does not authorize any user or resource outside the registered app and org policy
  3. A public client cannot rely on an embedded long-term secret as a confidential client would
  4. Salesforce can issue trusted SAML assertions only for applications and subjects registered in its identity provider trust configuration

Explanation

Correct Answer

B:

“A JWT's signature alone does not authorize any user or resource outside the registered app and org policy” needs to be evaluated against An automated partner service is registered to exchange a signed assertion for limited Salesforce access without a human prompt. The relevant check is Verify signed assertion claims, token audience, issuer binding, scope and key rotation; A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.

Incorrect Answers

A:

“A valid Salesforce user session does not authorize a SAML assertion for an unrelated target audience” needs to be evaluated against An automated partner service is registered to exchange a signed assertion for limited Salesforce access without a human prompt. The relevant check is Verify signed assertion claims, token audience, issuer binding, scope and key rotation; A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.

C:

“A public client cannot rely on an embedded long-term secret as a confidential client would” needs to be evaluated against An automated partner service is registered to exchange a signed assertion for limited Salesforce access without a human prompt. The relevant check is Verify signed assertion claims, token audience, issuer binding, scope and key rotation; A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.

D:

“Salesforce can issue trusted SAML assertions only for applications and subjects registered in its identity provider trust configuration” needs to be evaluated against An automated partner service is registered to exchange a signed assertion for limited Salesforce access without a human prompt. The relevant check is Verify signed assertion claims, token audience, issuer binding, scope and key rotation; A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.

Question 344

An automated partner service is registered to exchange a signed assertion for limited Salesforce access without a human prompt. Best complete IAM decision record?

  1. Action: Evaluate a supported JWT bearer or service-oriented OAuth flow with strictly managed keys, audience and least privilege. Verification: Verify signed assertion claims, token audience, issuer binding, scope and key rotation. Boundary: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.
  2. Action: Apply app access policies, understandable consent and administrative approval for sensitive integrations. Verification: Test code verifier/challenge, redirect registration, user grant and token exchange. Boundary: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.
  3. Action: Evaluate a supported JWT bearer or service-oriented OAuth flow with strictly managed keys, audience and least privilege. Verification: Compare supported release, SAML settings, service provider registration and permission assignments. Boundary: Salesforce can issue trusted SAML assertions only for applications and subjects registered in its identity provider trust configuration.
  4. Action: Plan new OAuth integrations with the external client app framework and confirm exception procedures only when genuinely needed. Verification: Verify signed assertion claims, token audience, issuer binding, scope and key rotation. Boundary: A public client cannot rely on an embedded long-term secret as a confidential client would.

Explanation

Correct Answer

A:

“Action: Evaluate a supported JWT bearer or service-oriented OAuth flow with strictly managed keys, audience and least privilege. Verification: Verify signed assertion claims, token audience, issuer binding, scope and key rotation. Boundary: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy” addresses the access-design responsibilities in an automated partner service is registered to exchange a signed assertion for limited Salesforce access without a human prompt Test against verify signed assertion claims, token audience, issuer binding, scope and key rotation; a JWT's signature alone does not authorize any user or resource outside the registered app and org policy.

Incorrect Answers

B:

“Action: Apply app access policies, understandable consent and administrative approval for sensitive integrations. Verification: Test code verifier/challenge, redirect registration, user grant and token exchange. Boundary: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy” may apply to a related identity task, but it does not establish verify signed assertion claims, token audience, issuer binding, scope and key rotation for an automated partner service is registered to exchange a signed assertion for limited Salesforce access without a human prompt The controlling boundary is: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.

C:

“Action: Evaluate a supported JWT bearer or service-oriented OAuth flow with strictly managed keys, audience and least privilege. Verification: Compare supported release, SAML settings, service provider registration and permission assignments. Boundary: Salesforce can issue trusted SAML assertions only for applications and subjects registered in its identity provider trust configuration” may apply to a related identity task, but it does not establish verify signed assertion claims, token audience, issuer binding, scope and key rotation for an automated partner service is registered to exchange a signed assertion for limited Salesforce access without a human prompt The controlling boundary is: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.

D:

“Action: Plan new OAuth integrations with the external client app framework and confirm exception procedures only when genuinely needed. Verification: Verify signed assertion claims, token audience, issuer binding, scope and key rotation. Boundary: A public client cannot rely on an embedded long-term secret as a confidential client would” may apply to a related identity task, but it does not establish verify signed assertion claims, token audience, issuer binding, scope and key rotation for an automated partner service is registered to exchange a signed assertion for limited Salesforce access without a human prompt The controlling boundary is: A JWT's signature alone does not authorize any user or resource outside the registered app and org policy.

Question 345

A nightly backend integration accesses Salesforce using an approved service identity and no user interaction. Best next IAM response?

  1. Prefer the supported external client app framework for new identity-provider integrations and preserve validated legacy app behavior
  2. Choose narrowly scoped OAuth grants and enforce least-privilege access independently of the OAuth scope string
  3. Consider supported OAuth client credentials under a dedicated run-as user and explicit access policy where appropriate
  4. Align external service provider entity ID, assertion audience, ACS recipient and NameID mapping

Explanation

Correct Answer

C:

“Consider supported OAuth client credentials under a dedicated run-as user and explicit access policy where appropriate” addresses the access-design responsibilities in a nightly backend integration accesses Salesforce using an approved service identity and no user interaction Test against review external client app settings, execution identity, object permissions and token lifetime; client credentials does not implicitly represent an individual interactive user or bypass org authorization.

Incorrect Answers

A:

“Prefer the supported external client app framework for new identity-provider integrations and preserve validated legacy app behavior” may apply to a related identity task, but it does not establish review external client app settings, execution identity, object permissions and token lifetime for a nightly backend integration accesses Salesforce using an approved service identity and no user interaction The controlling boundary is: Client credentials does not implicitly represent an individual interactive user or bypass org authorization.

B:

“Choose narrowly scoped OAuth grants and enforce least-privilege access independently of the OAuth scope string” may apply to a related identity task, but it does not establish review external client app settings, execution identity, object permissions and token lifetime for a nightly backend integration accesses Salesforce using an approved service identity and no user interaction The controlling boundary is: Client credentials does not implicitly represent an individual interactive user or bypass org authorization.

D:

“Align external service provider entity ID, assertion audience, ACS recipient and NameID mapping” may apply to a related identity task, but it does not establish review external client app settings, execution identity, object permissions and token lifetime for a nightly backend integration accesses Salesforce using an approved service identity and no user interaction The controlling boundary is: Client credentials does not implicitly represent an individual interactive user or bypass org authorization.

Question 346

A nightly backend integration accesses Salesforce using an approved service identity and no user interaction. Most decisive verification?

  1. Test device/user codes, verification URI, polling interval, expiration and consent
  2. Review integration user permission sets, requested scopes and negative authorization tests
  3. Validate Salesforce IdP certificate, SP entity ID, ACS URL and authorized user assignments
  4. Review external client app settings, execution identity, object permissions and token lifetime

Explanation

Correct Answer

D:

“Review external client app settings, execution identity, object permissions and token lifetime” distinguishes sign-in from entitlement administration in a nightly backend integration accesses Salesforce using an approved service identity and no user interaction It checks whether consider supported OAuth client credentials under a dedicated run-as user and explicit access policy where appropriate.

Incorrect Answers

A:

“Test device/user codes, verification URI, polling interval, expiration and consent” needs to be evaluated against A nightly backend integration accesses Salesforce using an approved service identity and no user interaction. The relevant check is Review external client app settings, execution identity, object permissions and token lifetime; Client credentials does not implicitly represent an individual interactive user or bypass org authorization.

B:

“Review integration user permission sets, requested scopes and negative authorization tests” needs to be evaluated against A nightly backend integration accesses Salesforce using an approved service identity and no user interaction. The relevant check is Review external client app settings, execution identity, object permissions and token lifetime; Client credentials does not implicitly represent an individual interactive user or bypass org authorization.

C:

“Validate Salesforce IdP certificate, SP entity ID, ACS URL and authorized user assignments” needs to be evaluated against A nightly backend integration accesses Salesforce using an approved service identity and no user interaction. The relevant check is Review external client app settings, execution identity, object permissions and token lifetime; Client credentials does not implicitly represent an individual interactive user or bypass org authorization.

Question 347

A nightly backend integration accesses Salesforce using an approved service identity and no user interaction. Key caution for this case?

  1. Rotating a signing certificate without coordinating trust at the SP can interrupt every affected sign-in
  2. Salesforce can issue trusted SAML assertions only for applications and subjects registered in its identity provider trust configuration
  3. Client credentials does not implicitly represent an individual interactive user or bypass org authorization
  4. A valid Salesforce user session does not authorize a SAML assertion for an unrelated target audience

Explanation

Correct Answer

C:

“Client credentials does not implicitly represent an individual interactive user or bypass org authorization” needs to be evaluated against A nightly backend integration accesses Salesforce using an approved service identity and no user interaction. The relevant check is Review external client app settings, execution identity, object permissions and token lifetime; Client credentials does not implicitly represent an individual interactive user or bypass org authorization.

Incorrect Answers

A:

“Rotating a signing certificate without coordinating trust at the SP can interrupt every affected sign-in” needs to be evaluated against A nightly backend integration accesses Salesforce using an approved service identity and no user interaction. The relevant check is Review external client app settings, execution identity, object permissions and token lifetime; Client credentials does not implicitly represent an individual interactive user or bypass org authorization.

B:

“Salesforce can issue trusted SAML assertions only for applications and subjects registered in its identity provider trust configuration” needs to be evaluated against A nightly backend integration accesses Salesforce using an approved service identity and no user interaction. The relevant check is Review external client app settings, execution identity, object permissions and token lifetime; Client credentials does not implicitly represent an individual interactive user or bypass org authorization.

D:

“A valid Salesforce user session does not authorize a SAML assertion for an unrelated target audience” needs to be evaluated against A nightly backend integration accesses Salesforce using an approved service identity and no user interaction. The relevant check is Review external client app settings, execution identity, object permissions and token lifetime; Client credentials does not implicitly represent an individual interactive user or bypass org authorization.

Question 348

A nightly backend integration accesses Salesforce using an approved service identity and no user interaction. Best complete IAM decision record?

  1. Action: Choose narrowly scoped OAuth grants and enforce least-privilege access independently of the OAuth scope string. Verification: Test device/user codes, verification URI, polling interval, expiration and consent. Boundary: Client credentials does not implicitly represent an individual interactive user or bypass org authorization.
  2. Action: Prefer the supported external client app framework for new identity-provider integrations and preserve validated legacy app behavior. Verification: Review external client app settings, execution identity, object permissions and token lifetime. Boundary: A valid Salesforce user session does not authorize a SAML assertion for an unrelated target audience.
  3. Action: Consider supported OAuth client credentials under a dedicated run-as user and explicit access policy where appropriate. Verification: Review external client app settings, execution identity, object permissions and token lifetime. Boundary: Client credentials does not implicitly represent an individual interactive user or bypass org authorization.
  4. Action: Consider supported OAuth client credentials under a dedicated run-as user and explicit access policy where appropriate. Verification: Validate Salesforce IdP certificate, SP entity ID, ACS URL and authorized user assignments. Boundary: Salesforce can issue trusted SAML assertions only for applications and subjects registered in its identity provider trust configuration.

Explanation

Correct Answer

C:

“Action: Consider supported OAuth client credentials under a dedicated run-as user and explicit access policy where appropriate. Verification: Review external client app settings, execution identity, object permissions and token lifetime. Boundary: Client credentials does not implicitly represent an individual interactive user or bypass org authorization” addresses the access-design responsibilities in a nightly backend integration accesses Salesforce using an approved service identity and no user interaction Test against review external client app settings, execution identity, object permissions and token lifetime; client credentials does not implicitly represent an individual interactive user or bypass org authorization.

Incorrect Answers

A:

“Action: Choose narrowly scoped OAuth grants and enforce least-privilege access independently of the OAuth scope string. Verification: Test device/user codes, verification URI, polling interval, expiration and consent. Boundary: Client credentials does not implicitly represent an individual interactive user or bypass org authorization” may apply to a related identity task, but it does not establish review external client app settings, execution identity, object permissions and token lifetime for a nightly backend integration accesses Salesforce using an approved service identity and no user interaction The controlling boundary is: Client credentials does not implicitly represent an individual interactive user or bypass org authorization.

B:

“Action: Prefer the supported external client app framework for new identity-provider integrations and preserve validated legacy app behavior. Verification: Review external client app settings, execution identity, object permissions and token lifetime. Boundary: A valid Salesforce user session does not authorize a SAML assertion for an unrelated target audience” may apply to a related identity task, but it does not establish review external client app settings, execution identity, object permissions and token lifetime for a nightly backend integration accesses Salesforce using an approved service identity and no user interaction The controlling boundary is: Client credentials does not implicitly represent an individual interactive user or bypass org authorization.

D:

“Action: Consider supported OAuth client credentials under a dedicated run-as user and explicit access policy where appropriate. Verification: Validate Salesforce IdP certificate, SP entity ID, ACS URL and authorized user assignments. Boundary: Salesforce can issue trusted SAML assertions only for applications and subjects registered in its identity provider trust configuration” may apply to a related identity task, but it does not establish review external client app settings, execution identity, object permissions and token lifetime for a nightly backend integration accesses Salesforce using an approved service identity and no user interaction The controlling boundary is: Client credentials does not implicitly represent an individual interactive user or bypass org authorization.

Question 349

A procurement system needs a server-to-server token for read-only Salesforce API queries. Best next IAM response?

  1. Align external service provider entity ID, assertion audience, ACS recipient and NameID mapping
  2. Consider supported OAuth client credentials under a dedicated run-as user and explicit access policy where appropriate
  3. Prefer the supported external client app framework for new identity-provider integrations and preserve validated legacy app behavior
  4. Choose narrowly scoped OAuth grants and enforce least-privilege access independently of the OAuth scope string

Explanation

Correct Answer

B:

“Consider supported OAuth client credentials under a dedicated run-as user and explicit access policy where appropriate” addresses the access-design responsibilities in a procurement system needs a server-to-server token for read-only Salesforce API queries Test against review external client app settings, execution identity, object permissions and token lifetime; client credentials does not implicitly represent an individual interactive user or bypass org authorization.

Incorrect Answers

A:

“Align external service provider entity ID, assertion audience, ACS recipient and NameID mapping” may apply to a related identity task, but it does not establish review external client app settings, execution identity, object permissions and token lifetime for a procurement system needs a server-to-server token for read-only Salesforce API queries The controlling boundary is: Client credentials does not implicitly represent an individual interactive user or bypass org authorization.

C:

“Prefer the supported external client app framework for new identity-provider integrations and preserve validated legacy app behavior” may apply to a related identity task, but it does not establish review external client app settings, execution identity, object permissions and token lifetime for a procurement system needs a server-to-server token for read-only Salesforce API queries The controlling boundary is: Client credentials does not implicitly represent an individual interactive user or bypass org authorization.

D:

“Choose narrowly scoped OAuth grants and enforce least-privilege access independently of the OAuth scope string” may apply to a related identity task, but it does not establish review external client app settings, execution identity, object permissions and token lifetime for a procurement system needs a server-to-server token for read-only Salesforce API queries The controlling boundary is: Client credentials does not implicitly represent an individual interactive user or bypass org authorization.

Question 350

A procurement system needs a server-to-server token for read-only Salesforce API queries. Most decisive verification?

  1. Test device/user codes, verification URI, polling interval, expiration and consent
  2. Review integration user permission sets, requested scopes and negative authorization tests
  3. Validate Salesforce IdP certificate, SP entity ID, ACS URL and authorized user assignments
  4. Review external client app settings, execution identity, object permissions and token lifetime

Explanation

Correct Answer

D:

“Review external client app settings, execution identity, object permissions and token lifetime” distinguishes sign-in from entitlement administration in a procurement system needs a server-to-server token for read-only Salesforce API queries It checks whether consider supported OAuth client credentials under a dedicated run-as user and explicit access policy where appropriate.

Incorrect Answers

A:

“Test device/user codes, verification URI, polling interval, expiration and consent” needs to be evaluated against A procurement system needs a server-to-server token for read-only Salesforce API queries. The relevant check is Review external client app settings, execution identity, object permissions and token lifetime; Client credentials does not implicitly represent an individual interactive user or bypass org authorization.

B:

“Review integration user permission sets, requested scopes and negative authorization tests” needs to be evaluated against A procurement system needs a server-to-server token for read-only Salesforce API queries. The relevant check is Review external client app settings, execution identity, object permissions and token lifetime; Client credentials does not implicitly represent an individual interactive user or bypass org authorization.

C:

“Validate Salesforce IdP certificate, SP entity ID, ACS URL and authorized user assignments” needs to be evaluated against A procurement system needs a server-to-server token for read-only Salesforce API queries. The relevant check is Review external client app settings, execution identity, object permissions and token lifetime; Client credentials does not implicitly represent an individual interactive user or bypass org authorization.

Certified Platform Identity and Access Management Architect Practice Tests