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 69

Question 680

A university alumni portal accepts federated SAML assertions and must provision only authorized graduates. Best complete IAM decision record?

  1. Action: Configure the Experience Cloud service-provider federation and subject mapping with approved membership controls. Verification: Check site ACS/issuer metadata, NameID mapping, user license and contact relationship. Boundary: Correct SAML authentication does not prove the user belongs to the intended Experience Cloud site.
  2. Action: Define an external-user MFA and recovery assurance policy consistent with supported Salesforce and IdP controls. Verification: Review privacy notice version, permission to process, retention and data field minimization. Boundary: Correct SAML authentication does not prove the user belongs to the intended Experience Cloud site.
  3. Action: Configure the Experience Cloud service-provider federation and subject mapping with approved membership controls. Verification: Inspect guest profile, object permissions, sharing rules and anonymous negative access checks. Boundary: Embedded login still requires trusted application registration, browser policy and protected token handling.
  4. Action: Design sign-out behavior and communicate supported single logout versus local session termination. Verification: Check site ACS/issuer metadata, NameID mapping, user license and contact relationship. Boundary: Custom login pages must preserve anti-phishing signals and should not expose user enumeration details.

Explanation

Correct Answer

A:

“Action: Configure the Experience Cloud service-provider federation and subject mapping with approved membership controls. Verification: Check site ACS/issuer metadata, NameID mapping, user license and contact relationship. Boundary: Correct SAML authentication does not prove the user belongs to the intended Experience Cloud site” addresses the access-design responsibilities in a university alumni portal accepts federated SAML assertions and must provision only authorized graduates Test against check site ACS/issuer metadata, NameID mapping, user license and contact relationship; correct SAML authentication does not prove the user belongs to the intended Experience Cloud site.

Incorrect Answers

B:

“Action: Define an external-user MFA and recovery assurance policy consistent with supported Salesforce and IdP controls. Verification: Review privacy notice version, permission to process, retention and data field minimization. Boundary: Correct SAML authentication does not prove the user belongs to the intended Experience Cloud site” may apply to a related identity task, but it does not establish check site ACS/issuer metadata, NameID mapping, user license and contact relationship for a university alumni portal accepts federated SAML assertions and must provision only authorized graduates The controlling boundary is: Correct SAML authentication does not prove the user belongs to the intended Experience Cloud site.

C:

“Action: Configure the Experience Cloud service-provider federation and subject mapping with approved membership controls. Verification: Inspect guest profile, object permissions, sharing rules and anonymous negative access checks. Boundary: Embedded login still requires trusted application registration, browser policy and protected token handling” may apply to a related identity task, but it does not establish check site ACS/issuer metadata, NameID mapping, user license and contact relationship for a university alumni portal accepts federated SAML assertions and must provision only authorized graduates The controlling boundary is: Correct SAML authentication does not prove the user belongs to the intended Experience Cloud site.

D:

“Action: Design sign-out behavior and communicate supported single logout versus local session termination. Verification: Check site ACS/issuer metadata, NameID mapping, user license and contact relationship. Boundary: Custom login pages must preserve anti-phishing signals and should not expose user enumeration details” may apply to a related identity task, but it does not establish check site ACS/issuer metadata, NameID mapping, user license and contact relationship for a university alumni portal accepts federated SAML assertions and must provision only authorized graduates The controlling boundary is: Correct SAML authentication does not prove the user belongs to the intended Experience Cloud site.

Question 681

A nonprofit needs first-login registration through an external IdP while checking for an existing donor contact. Best next IAM response?

  1. Choose safe browser/mobile authorization patterns with PKCE where appropriate, minimal token storage and controlled logout
  2. Configure supported authentication providers and a controlled registration handler for verified external identity claims
  3. Configure site-specific login and registration user experience with trusted providers and security-preserving branding
  4. Design a registration handler or supported registration flow with stable subject matching and minimum user creation

Explanation

Correct Answer

D:

“Design a registration handler or supported registration flow with stable subject matching and minimum user creation” addresses the access-design responsibilities in a nonprofit needs first-login registration through an external IdP while checking for an existing donor contact Test against verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure; creating a new contact on every successful login will fragment customer identity records.

Incorrect Answers

A:

“Choose safe browser/mobile authorization patterns with PKCE where appropriate, minimal token storage and controlled logout” may apply to a related identity task, but it does not establish verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure for a nonprofit needs first-login registration through an external IdP while checking for an existing donor contact The controlling boundary is: Creating a new contact on every successful login will fragment customer identity records.

B:

“Configure supported authentication providers and a controlled registration handler for verified external identity claims” may apply to a related identity task, but it does not establish verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure for a nonprofit needs first-login registration through an external IdP while checking for an existing donor contact The controlling boundary is: Creating a new contact on every successful login will fragment customer identity records.

C:

“Configure site-specific login and registration user experience with trusted providers and security-preserving branding” may apply to a related identity task, but it does not establish verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure for a nonprofit needs first-login registration through an external IdP while checking for an existing donor contact The controlling boundary is: Creating a new contact on every successful login will fragment customer identity records.

Question 682

A nonprofit needs first-login registration through an external IdP while checking for an existing donor contact. Most decisive verification?

  1. Inspect guest profile, object permissions, sharing rules and anonymous negative access checks
  2. Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure
  3. Test identity provider assurance, Salesforce session needs, recovery verification and failed challenge handling
  4. Test login discovery, site settings, reset flow, error messaging and accessibility

Explanation

Correct Answer

B:

“Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure” distinguishes sign-in from entitlement administration in a nonprofit needs first-login registration through an external IdP while checking for an existing donor contact It checks whether design a registration handler or supported registration flow with stable subject matching and minimum user creation.

Incorrect Answers

A:

“Inspect guest profile, object permissions, sharing rules and anonymous negative access checks” needs to be evaluated against A nonprofit needs first-login registration through an external IdP while checking for an existing donor contact. The relevant check is Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure; Creating a new contact on every successful login will fragment customer identity records.

C:

“Test identity provider assurance, Salesforce session needs, recovery verification and failed challenge handling” needs to be evaluated against A nonprofit needs first-login registration through an external IdP while checking for an existing donor contact. The relevant check is Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure; Creating a new contact on every successful login will fragment customer identity records.

D:

“Test login discovery, site settings, reset flow, error messaging and accessibility” needs to be evaluated against A nonprofit needs first-login registration through an external IdP while checking for an existing donor contact. The relevant check is Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure; Creating a new contact on every successful login will fragment customer identity records.

Question 683

A nonprofit needs first-login registration through an external IdP while checking for an existing donor contact. Key caution for this case?

  1. Social login alone must not create broad or duplicate Salesforce account entitlements
  2. A third-party MFA claim does not by itself prove the target Salesforce session meets every high-assurance policy
  3. Creating a new contact on every successful login will fragment customer identity records
  4. A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app

Explanation

Correct Answer

C:

“Creating a new contact on every successful login will fragment customer identity records” needs to be evaluated against A nonprofit needs first-login registration through an external IdP while checking for an existing donor contact. The relevant check is Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure; Creating a new contact on every successful login will fragment customer identity records.

Incorrect Answers

A:

“Social login alone must not create broad or duplicate Salesforce account entitlements” needs to be evaluated against A nonprofit needs first-login registration through an external IdP while checking for an existing donor contact. The relevant check is Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure; Creating a new contact on every successful login will fragment customer identity records.

B:

“A third-party MFA claim does not by itself prove the target Salesforce session meets every high-assurance policy” needs to be evaluated against A nonprofit needs first-login registration through an external IdP while checking for an existing donor contact. The relevant check is Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure; Creating a new contact on every successful login will fragment customer identity records.

D:

“A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app” needs to be evaluated against A nonprofit needs first-login registration through an external IdP while checking for an existing donor contact. The relevant check is Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure; Creating a new contact on every successful login will fragment customer identity records.

Question 684

A nonprofit needs first-login registration through an external IdP while checking for an existing donor contact. Best complete IAM decision record?

  1. Action: Configure supported authentication providers and a controlled registration handler for verified external identity claims. Verification: Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure. Boundary: Social login alone must not create broad or duplicate Salesforce account entitlements.
  2. Action: Design a registration handler or supported registration flow with stable subject matching and minimum user creation. Verification: Inspect guest profile, object permissions, sharing rules and anonymous negative access checks. Boundary: A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app.
  3. Action: Configure site-specific login and registration user experience with trusted providers and security-preserving branding. Verification: Test login discovery, site settings, reset flow, error messaging and accessibility. Boundary: Creating a new contact on every successful login will fragment customer identity records.
  4. Action: Design a registration handler or supported registration flow with stable subject matching and minimum user creation. Verification: Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure. Boundary: Creating a new contact on every successful login will fragment customer identity records.

Explanation

Correct Answer

D:

“Action: Design a registration handler or supported registration flow with stable subject matching and minimum user creation. Verification: Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure. Boundary: Creating a new contact on every successful login will fragment customer identity records” addresses the access-design responsibilities in a nonprofit needs first-login registration through an external IdP while checking for an existing donor contact Test against verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure; creating a new contact on every successful login will fragment customer identity records.

Incorrect Answers

A:

“Action: Configure supported authentication providers and a controlled registration handler for verified external identity claims. Verification: Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure. Boundary: Social login alone must not create broad or duplicate Salesforce account entitlements” may apply to a related identity task, but it does not establish verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure for a nonprofit needs first-login registration through an external IdP while checking for an existing donor contact The controlling boundary is: Creating a new contact on every successful login will fragment customer identity records.

B:

“Action: Design a registration handler or supported registration flow with stable subject matching and minimum user creation. Verification: Inspect guest profile, object permissions, sharing rules and anonymous negative access checks. Boundary: A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app” may apply to a related identity task, but it does not establish verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure for a nonprofit needs first-login registration through an external IdP while checking for an existing donor contact The controlling boundary is: Creating a new contact on every successful login will fragment customer identity records.

C:

“Action: Configure site-specific login and registration user experience with trusted providers and security-preserving branding. Verification: Test login discovery, site settings, reset flow, error messaging and accessibility. Boundary: Creating a new contact on every successful login will fragment customer identity records” may apply to a related identity task, but it does not establish verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure for a nonprofit needs first-login registration through an external IdP while checking for an existing donor contact The controlling boundary is: Creating a new contact on every successful login will fragment customer identity records.

Question 685

A consumer marketplace registers customers through an OpenID Connect flow and must prevent duplicate identities. Best next IAM response?

  1. Configure site-specific login and registration user experience with trusted providers and security-preserving branding
  2. Choose safe browser/mobile authorization patterns with PKCE where appropriate, minimal token storage and controlled logout
  3. Configure supported authentication providers and a controlled registration handler for verified external identity claims
  4. Design a registration handler or supported registration flow with stable subject matching and minimum user creation

Explanation

Correct Answer

D:

“Design a registration handler or supported registration flow with stable subject matching and minimum user creation” addresses the access-design responsibilities in a consumer marketplace registers customers through an OpenID Connect flow and must prevent duplicate identities Test against verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure; creating a new contact on every successful login will fragment customer identity records.

Incorrect Answers

A:

“Configure site-specific login and registration user experience with trusted providers and security-preserving branding” may apply to a related identity task, but it does not establish verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure for a consumer marketplace registers customers through an OpenID Connect flow and must prevent duplicate identities The controlling boundary is: Creating a new contact on every successful login will fragment customer identity records.

B:

“Choose safe browser/mobile authorization patterns with PKCE where appropriate, minimal token storage and controlled logout” may apply to a related identity task, but it does not establish verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure for a consumer marketplace registers customers through an OpenID Connect flow and must prevent duplicate identities The controlling boundary is: Creating a new contact on every successful login will fragment customer identity records.

C:

“Configure supported authentication providers and a controlled registration handler for verified external identity claims” may apply to a related identity task, but it does not establish verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure for a consumer marketplace registers customers through an OpenID Connect flow and must prevent duplicate identities The controlling boundary is: Creating a new contact on every successful login will fragment customer identity records.

Question 686

A consumer marketplace registers customers through an OpenID Connect flow and must prevent duplicate identities. Most decisive verification?

  1. Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure
  2. Test login discovery, site settings, reset flow, error messaging and accessibility
  3. Test identity provider assurance, Salesforce session needs, recovery verification and failed challenge handling
  4. Inspect guest profile, object permissions, sharing rules and anonymous negative access checks

Explanation

Correct Answer

A:

“Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure” distinguishes sign-in from entitlement administration in a consumer marketplace registers customers through an OpenID Connect flow and must prevent duplicate identities It checks whether design a registration handler or supported registration flow with stable subject matching and minimum user creation.

Incorrect Answers

B:

“Test login discovery, site settings, reset flow, error messaging and accessibility” needs to be evaluated against A consumer marketplace registers customers through an OpenID Connect flow and must prevent duplicate identities. The relevant check is Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure; Creating a new contact on every successful login will fragment customer identity records.

C:

“Test identity provider assurance, Salesforce session needs, recovery verification and failed challenge handling” needs to be evaluated against A consumer marketplace registers customers through an OpenID Connect flow and must prevent duplicate identities. The relevant check is Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure; Creating a new contact on every successful login will fragment customer identity records.

D:

“Inspect guest profile, object permissions, sharing rules and anonymous negative access checks” needs to be evaluated against A consumer marketplace registers customers through an OpenID Connect flow and must prevent duplicate identities. The relevant check is Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure; Creating a new contact on every successful login will fragment customer identity records.

Question 687

A consumer marketplace registers customers through an OpenID Connect flow and must prevent duplicate identities. Key caution for this case?

  1. Creating a new contact on every successful login will fragment customer identity records
  2. A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app
  3. Social login alone must not create broad or duplicate Salesforce account entitlements
  4. A third-party MFA claim does not by itself prove the target Salesforce session meets every high-assurance policy

Explanation

Correct Answer

A:

“Creating a new contact on every successful login will fragment customer identity records” needs to be evaluated against A consumer marketplace registers customers through an OpenID Connect flow and must prevent duplicate identities. The relevant check is Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure; Creating a new contact on every successful login will fragment customer identity records.

Incorrect Answers

B:

“A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app” needs to be evaluated against A consumer marketplace registers customers through an OpenID Connect flow and must prevent duplicate identities. The relevant check is Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure; Creating a new contact on every successful login will fragment customer identity records.

C:

“Social login alone must not create broad or duplicate Salesforce account entitlements” needs to be evaluated against A consumer marketplace registers customers through an OpenID Connect flow and must prevent duplicate identities. The relevant check is Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure; Creating a new contact on every successful login will fragment customer identity records.

D:

“A third-party MFA claim does not by itself prove the target Salesforce session meets every high-assurance policy” needs to be evaluated against A consumer marketplace registers customers through an OpenID Connect flow and must prevent duplicate identities. The relevant check is Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure; Creating a new contact on every successful login will fragment customer identity records.

Question 688

A consumer marketplace registers customers through an OpenID Connect flow and must prevent duplicate identities. Best complete IAM decision record?

  1. Action: Design a registration handler or supported registration flow with stable subject matching and minimum user creation. Verification: Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure. Boundary: Creating a new contact on every successful login will fragment customer identity records.
  2. Action: Design a registration handler or supported registration flow with stable subject matching and minimum user creation. Verification: Inspect guest profile, object permissions, sharing rules and anonymous negative access checks. Boundary: A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app.
  3. Action: Configure site-specific login and registration user experience with trusted providers and security-preserving branding. Verification: Test login discovery, site settings, reset flow, error messaging and accessibility. Boundary: Creating a new contact on every successful login will fragment customer identity records.
  4. Action: Configure supported authentication providers and a controlled registration handler for verified external identity claims. Verification: Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure. Boundary: Social login alone must not create broad or duplicate Salesforce account entitlements.

Explanation

Correct Answer

A:

“Action: Design a registration handler or supported registration flow with stable subject matching and minimum user creation. Verification: Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure. Boundary: Creating a new contact on every successful login will fragment customer identity records” addresses the access-design responsibilities in a consumer marketplace registers customers through an OpenID Connect flow and must prevent duplicate identities Test against verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure; creating a new contact on every successful login will fragment customer identity records.

Incorrect Answers

B:

“Action: Design a registration handler or supported registration flow with stable subject matching and minimum user creation. Verification: Inspect guest profile, object permissions, sharing rules and anonymous negative access checks. Boundary: A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app” may apply to a related identity task, but it does not establish verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure for a consumer marketplace registers customers through an OpenID Connect flow and must prevent duplicate identities The controlling boundary is: Creating a new contact on every successful login will fragment customer identity records.

C:

“Action: Configure site-specific login and registration user experience with trusted providers and security-preserving branding. Verification: Test login discovery, site settings, reset flow, error messaging and accessibility. Boundary: Creating a new contact on every successful login will fragment customer identity records” may apply to a related identity task, but it does not establish verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure for a consumer marketplace registers customers through an OpenID Connect flow and must prevent duplicate identities The controlling boundary is: Creating a new contact on every successful login will fragment customer identity records.

D:

“Action: Configure supported authentication providers and a controlled registration handler for verified external identity claims. Verification: Verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure. Boundary: Social login alone must not create broad or duplicate Salesforce account entitlements” may apply to a related identity task, but it does not establish verify duplicate matching, required contact fields, terms acknowledgment and rollback on failure for a consumer marketplace registers customers through an OpenID Connect flow and must prevent duplicate identities The controlling boundary is: Creating a new contact on every successful login will fragment customer identity records.

Question 689

A field-service portal invites registered customers but must not allow anonymous users to self-assign partner rights. Best next IAM response?

  1. Enforce appropriate external user permissions and organization-aware sharing at every access layer
  2. Separate approved self-registration from invitation-based privileged onboarding and assign narrow initial permissions
  3. Design external user, contact and account relationships before enabling authorized Experience Cloud access
  4. Implement documented consent and data-minimization handling separate from authentication success

Explanation

Correct Answer

B:

“Separate approved self-registration from invitation-based privileged onboarding and assign narrow initial permissions” addresses the access-design responsibilities in a field-service portal invites registered customers but must not allow anonymous users to self-assign partner rights Test against test unauthenticated registration path, invite token, profile selection and elevation denial; a self-service signup form must not grant privileged partner access solely from unverified user input.

Incorrect Answers

A:

“Enforce appropriate external user permissions and organization-aware sharing at every access layer” may apply to a related identity task, but it does not establish test unauthenticated registration path, invite token, profile selection and elevation denial for a field-service portal invites registered customers but must not allow anonymous users to self-assign partner rights The controlling boundary is: A self-service signup form must not grant privileged partner access solely from unverified user input.

C:

“Design external user, contact and account relationships before enabling authorized Experience Cloud access” may apply to a related identity task, but it does not establish test unauthenticated registration path, invite token, profile selection and elevation denial for a field-service portal invites registered customers but must not allow anonymous users to self-assign partner rights The controlling boundary is: A self-service signup form must not grant privileged partner access solely from unverified user input.

D:

“Implement documented consent and data-minimization handling separate from authentication success” may apply to a related identity task, but it does not establish test unauthenticated registration path, invite token, profile selection and elevation denial for a field-service portal invites registered customers but must not allow anonymous users to self-assign partner rights The controlling boundary is: A self-service signup form must not grant privileged partner access solely from unverified user input.

Question 690

A field-service portal invites registered customers but must not allow anonymous users to self-assign partner rights. Most decisive verification?

  1. Inspect guest profile, object permissions, sharing rules and anonymous negative access checks
  2. Review privacy notice version, permission to process, retention and data field minimization
  3. Test unauthenticated registration path, invite token, profile selection and elevation denial
  4. Check site ACS/issuer metadata, NameID mapping, user license and contact relationship

Explanation

Correct Answer

C:

“Test unauthenticated registration path, invite token, profile selection and elevation denial” distinguishes sign-in from entitlement administration in a field-service portal invites registered customers but must not allow anonymous users to self-assign partner rights It checks whether separate approved self-registration from invitation-based privileged onboarding and assign narrow initial permissions.

Incorrect Answers

A:

“Inspect guest profile, object permissions, sharing rules and anonymous negative access checks” needs to be evaluated against A field-service portal invites registered customers but must not allow anonymous users to self-assign partner rights. The relevant check is Test unauthenticated registration path, invite token, profile selection and elevation denial; A self-service signup form must not grant privileged partner access solely from unverified user input.

B:

“Review privacy notice version, permission to process, retention and data field minimization” needs to be evaluated against A field-service portal invites registered customers but must not allow anonymous users to self-assign partner rights. The relevant check is Test unauthenticated registration path, invite token, profile selection and elevation denial; A self-service signup form must not grant privileged partner access solely from unverified user input.

D:

“Check site ACS/issuer metadata, NameID mapping, user license and contact relationship” needs to be evaluated against A field-service portal invites registered customers but must not allow anonymous users to self-assign partner rights. The relevant check is Test unauthenticated registration path, invite token, profile selection and elevation denial; A self-service signup form must not grant privileged partner access solely from unverified user input.

Certified Platform Identity and Access Management Architect Practice Tests