Salesforce Certified Platform Identity and Access Management Architect Practice Test 48
Question 470
Suppose the integration design proceeds without correcting this issue: Connected-app permitted-user policy allows all users to self-authorize new sessions without prior review. In the environment An external reporting app should be restricted to a vetted group of Salesforce employees. What should the risk register emphasize?
- A hidden application keeps pulling records despite being removed from the user navigation.
- An unapproved employee grants the app API access to records beyond the organization's policy.
- Overly broad network rules allow unmanaged devices to obtain app sessions without review.
- A former contractor uses stored refresh tokens long after the business relationship ends.
Explanation
Correct Answer
B:Best. The most direct failure is: An unapproved employee grants the app API access to records beyond the organization's policy. It is a consequence of the documented condition: Connected-app permitted-user policy allows all users to self-authorize new sessions without prior review. A mitigation is: Restrict application access to approved users and govern grants through profile or permission-set authorization.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise bans a previously trusted external app after detecting a vendor security incident. Its relevant condition is: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The present case instead turns on: Connected-app permitted-user policy allows all users to self-authorize new sessions without prior review. The direct answer here is: An unapproved employee grants the app API access to records beyond the organization's policy.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A new Salesforce connected app wants access from a narrow set of corporate networks. Its relevant condition is: The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices. The present case instead turns on: Connected-app permitted-user policy allows all users to self-authorize new sessions without prior review. The direct answer here is: An unapproved employee grants the app API access to records beyond the organization's policy.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A mobile connected app must not continue operating indefinitely after a contractor's account is disabled. Its relevant condition is: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. The present case instead turns on: Connected-app permitted-user policy allows all users to self-authorize new sessions without prior review. The direct answer here is: An unapproved employee grants the app API access to records beyond the organization's policy.
Question 471
In this fictional project, A Salesforce-connected finance app must require High Assurance when employees authorize new access. The project team has uncovered that The app's session policy is set to Standard despite handling highly sensitive payroll information. Which action is best supported by those facts?
- Configure appropriate refresh-token and session policies plus offboarding revocation controls.
- Restrict application access to approved users and govern grants through profile or permission-set authorization.
- Combine minimal connected-app scopes with an appropriately restricted service-user license and permissions.
- Choose the supported connected-app session policy and ensure an eligible High Assurance method exists.
Explanation
Correct Answer
D:Best. The most direct action is to choose the supported connected-app session policy and ensure an eligible High Assurance method exists. It is supported by the specific finding that the app's session policy is set to Standard despite handling highly sensitive payroll information. The expected acceptance evidence is: Sensitive app access is challenged or blocked according to the documented session level.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A mobile connected app must not continue operating indefinitely after a contractor's account is disabled. Its relevant condition is: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. The present case instead turns on: The app's session policy is set to Standard despite handling highly sensitive payroll information. The direct answer here is: Choose the supported connected-app session policy and ensure an eligible High Assurance method exists.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external reporting app should be restricted to a vetted group of Salesforce employees. Its relevant condition is: Connected-app permitted-user policy allows all users to self-authorize new sessions without prior review. The present case instead turns on: The app's session policy is set to Standard despite handling highly sensitive payroll information. The direct answer here is: Choose the supported connected-app session policy and ensure an eligible High Assurance method exists.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A vendor integration used by a nonprofit requests full API scope for a read-only dashboard. Its relevant condition is: The administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions. The present case instead turns on: The app's session policy is set to Standard despite handling highly sensitive payroll information. The direct answer here is: Choose the supported connected-app session policy and ensure an eligible High Assurance method exists.
Question 472
An enterprise review begins with this business situation: A Salesforce-connected finance app must require High Assurance when employees authorize new access. Which technical or process signal best identifies the obstacle?
- The app's session policy is set to Standard despite handling highly sensitive payroll information.
- Connected-app permitted-user policy allows all users to self-authorize new sessions without prior review.
- The application issues persistent refresh tokens and has no documented inactivity or revocation procedure.
- Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain.
Explanation
Correct Answer
A:Best. The decisive observation is: The app's session policy is set to Standard despite handling highly sensitive payroll information. This is why the design response should be: Choose the supported connected-app session policy and ensure an eligible High Assurance method exists.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external reporting app should be restricted to a vetted group of Salesforce employees. Its relevant condition is: Connected-app permitted-user policy allows all users to self-authorize new sessions without prior review. The present case instead turns on: The app's session policy is set to Standard despite handling highly sensitive payroll information. The direct answer here is: The app's session policy is set to Standard despite handling highly sensitive payroll information.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A mobile connected app must not continue operating indefinitely after a contractor's account is disabled. Its relevant condition is: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. The present case instead turns on: The app's session policy is set to Standard despite handling highly sensitive payroll information. The direct answer here is: The app's session policy is set to Standard despite handling highly sensitive payroll information.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise bans a previously trusted external app after detecting a vendor security incident. Its relevant condition is: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The present case instead turns on: The app's session policy is set to Standard despite handling highly sensitive payroll information. The direct answer here is: The app's session policy is set to Standard despite handling highly sensitive payroll information.
Question 473
The team adopts this approach: Choose the supported connected-app session policy and ensure an eligible High Assurance method exists. The original project scenario is: A Salesforce-connected finance app must require High Assurance when employees authorize new access. Which verification outcome best demonstrates that it worked?
- Approved environments can connect and disallowed origins follow the configured restriction.
- Sensitive app access is challenged or blocked according to the documented session level.
- Read-only reports work while object writes and unrelated fields fail authorization tests.
- Existing and future access from the blocked application are contained and auditable.
Explanation
Correct Answer
B:Best. The verification target is: Sensitive app access is challenged or blocked according to the documented session level. It tests whether the chosen approach—Choose the supported connected-app session policy and ensure an eligible High Assurance method exists.—actually resolves the specific finding: The app's session policy is set to Standard despite handling highly sensitive payroll information.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A new Salesforce connected app wants access from a narrow set of corporate networks. Its relevant condition is: The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices. The present case instead turns on: The app's session policy is set to Standard despite handling highly sensitive payroll information. The direct answer here is: Sensitive app access is challenged or blocked according to the documented session level.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A vendor integration used by a nonprofit requests full API scope for a read-only dashboard. Its relevant condition is: The administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions. The present case instead turns on: The app's session policy is set to Standard despite handling highly sensitive payroll information. The direct answer here is: Sensitive app access is challenged or blocked according to the documented session level.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise bans a previously trusted external app after detecting a vendor security incident. Its relevant condition is: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The present case instead turns on: The app's session policy is set to Standard despite handling highly sensitive payroll information. The direct answer here is: Sensitive app access is challenged or blocked according to the documented session level.
Question 474
A project manager declines to address this finding: The app's session policy is set to Standard despite handling highly sensitive payroll information. The related project is: A Salesforce-connected finance app must require High Assurance when employees authorize new access. Which consequence most directly follows?
- A hidden application keeps pulling records despite being removed from the user navigation.
- Overly broad network rules allow unmanaged devices to obtain app sessions without review.
- A user with only basic authentication can enter the protected finance application.
- A former contractor uses stored refresh tokens long after the business relationship ends.
Explanation
Correct Answer
C:Best. The most direct failure is: A user with only basic authentication can enter the protected finance application. It is a consequence of the documented condition: The app's session policy is set to Standard despite handling highly sensitive payroll information. A mitigation is: Choose the supported connected-app session policy and ensure an eligible High Assurance method exists.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise bans a previously trusted external app after detecting a vendor security incident. Its relevant condition is: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The present case instead turns on: The app's session policy is set to Standard despite handling highly sensitive payroll information. The direct answer here is: A user with only basic authentication can enter the protected finance application.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A new Salesforce connected app wants access from a narrow set of corporate networks. Its relevant condition is: The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices. The present case instead turns on: The app's session policy is set to Standard despite handling highly sensitive payroll information. The direct answer here is: A user with only basic authentication can enter the protected finance application.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A mobile connected app must not continue operating indefinitely after a contractor's account is disabled. Its relevant condition is: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. The present case instead turns on: The app's session policy is set to Standard despite handling highly sensitive payroll information. The direct answer here is: A user with only basic authentication can enter the protected finance application.
Question 475
An integration architect receives this requirement: A mobile connected app must not continue operating indefinitely after a contractor's account is disabled. A technical discovery also finds: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. Which response most directly addresses the present constraint?
- Apply the supported connected-app block/revocation policy and inspect remaining token/session use.
- Configure appropriate refresh-token and session policies plus offboarding revocation controls.
- Restrict application access to approved users and govern grants through profile or permission-set authorization.
- Apply supported connected-app network restrictions and test legitimate user paths before rollout.
Explanation
Correct Answer
B:Best. The most direct action is to configure appropriate refresh-token and session policies plus offboarding revocation controls. It is supported by the specific finding that the application issues persistent refresh tokens and has no documented inactivity or revocation procedure. The expected acceptance evidence is: Inactive or revoked users cannot silently renew API sessions beyond the approved lifetime.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise bans a previously trusted external app after detecting a vendor security incident. Its relevant condition is: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The present case instead turns on: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. The direct answer here is: Configure appropriate refresh-token and session policies plus offboarding revocation controls.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external reporting app should be restricted to a vetted group of Salesforce employees. Its relevant condition is: Connected-app permitted-user policy allows all users to self-authorize new sessions without prior review. The present case instead turns on: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. The direct answer here is: Configure appropriate refresh-token and session policies plus offboarding revocation controls.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A new Salesforce connected app wants access from a narrow set of corporate networks. Its relevant condition is: The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices. The present case instead turns on: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. The direct answer here is: Configure appropriate refresh-token and session policies plus offboarding revocation controls.
Question 476
Consider the following hypothetical Salesforce initiative: A mobile connected app must not continue operating indefinitely after a contractor's account is disabled. Which evidence would most strongly explain the current integration weakness?
- The administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions.
- Connected-app permitted-user policy allows all users to self-authorize new sessions without prior review.
- The app's session policy is set to Standard despite handling highly sensitive payroll information.
- The application issues persistent refresh tokens and has no documented inactivity or revocation procedure.
Explanation
Correct Answer
D:Best. The decisive observation is: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. This is why the design response should be: Configure appropriate refresh-token and session policies plus offboarding revocation controls.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A vendor integration used by a nonprofit requests full API scope for a read-only dashboard. Its relevant condition is: The administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions. The present case instead turns on: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. The direct answer here is: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external reporting app should be restricted to a vetted group of Salesforce employees. Its relevant condition is: Connected-app permitted-user policy allows all users to self-authorize new sessions without prior review. The present case instead turns on: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. The direct answer here is: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A Salesforce-connected finance app must require High Assurance when employees authorize new access. Its relevant condition is: The app's session policy is set to Standard despite handling highly sensitive payroll information. The present case instead turns on: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. The direct answer here is: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure.
Question 477
Review this change: Configure appropriate refresh-token and session policies plus offboarding revocation controls. It addresses a project where A mobile connected app must not continue operating indefinitely after a contractor's account is disabled. Which result should appear in integration acceptance evidence?
- Existing and future access from the blocked application are contained and auditable.
- Approved environments can connect and disallowed origins follow the configured restriction.
- Inactive or revoked users cannot silently renew API sessions beyond the approved lifetime.
- Sensitive app access is challenged or blocked according to the documented session level.
Explanation
Correct Answer
C:Best. The verification target is: Inactive or revoked users cannot silently renew API sessions beyond the approved lifetime. It tests whether the chosen approach—Configure appropriate refresh-token and session policies plus offboarding revocation controls.—actually resolves the specific finding: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise bans a previously trusted external app after detecting a vendor security incident. Its relevant condition is: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The present case instead turns on: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. The direct answer here is: Inactive or revoked users cannot silently renew API sessions beyond the approved lifetime.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A new Salesforce connected app wants access from a narrow set of corporate networks. Its relevant condition is: The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices. The present case instead turns on: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. The direct answer here is: Inactive or revoked users cannot silently renew API sessions beyond the approved lifetime.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A Salesforce-connected finance app must require High Assurance when employees authorize new access. Its relevant condition is: The app's session policy is set to Standard despite handling highly sensitive payroll information. The present case instead turns on: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. The direct answer here is: Inactive or revoked users cannot silently renew API sessions beyond the approved lifetime.
Question 478
Suppose the integration design proceeds without correcting this issue: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. In the environment A mobile connected app must not continue operating indefinitely after a contractor's account is disabled. What should the risk register emphasize?
- Untrusted mutable attributes from a signed assertion silently assign system administrator rights.
- A hidden application keeps pulling records despite being removed from the user navigation.
- A former contractor uses stored refresh tokens long after the business relationship ends.
- An unapproved employee grants the app API access to records beyond the organization's policy.
Explanation
Correct Answer
C:Best. The most direct failure is: A former contractor uses stored refresh tokens long after the business relationship ends. It is a consequence of the documented condition: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. A mitigation is: Configure appropriate refresh-token and session policies plus offboarding revocation controls.
Incorrect Answers
A:Not best for this scenario. This option is associated with another type of requirement: A company wants JIT provisioning to grant Salesforce Administrator rights based on an arbitrary IdP attribute. Its relevant condition is: The federation team has not defined which identity source may authorize sensitive entitlements. The present case instead turns on: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. The direct answer here is: A former contractor uses stored refresh tokens long after the business relationship ends.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise bans a previously trusted external app after detecting a vendor security incident. Its relevant condition is: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The present case instead turns on: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. The direct answer here is: A former contractor uses stored refresh tokens long after the business relationship ends.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external reporting app should be restricted to a vetted group of Salesforce employees. Its relevant condition is: Connected-app permitted-user policy allows all users to self-authorize new sessions without prior review. The present case instead turns on: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. The direct answer here is: A former contractor uses stored refresh tokens long after the business relationship ends.
Question 479
An architecture board reviews a proposed Salesforce integration. Context: A new Salesforce connected app wants access from a narrow set of corporate networks. Finding: The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices. Which decision best resolves the concern?
- Configure appropriate refresh-token and session policies plus offboarding revocation controls.
- Apply supported connected-app network restrictions and test legitimate user paths before rollout.
- Choose the supported connected-app session policy and ensure an eligible High Assurance method exists.
- Apply the supported connected-app block/revocation policy and inspect remaining token/session use.
Explanation
Correct Answer
B:Best. The most direct action is to apply supported connected-app network restrictions and test legitimate user paths before rollout. It is supported by the specific finding that the proposed deployment ignores trusted IP policies and access exceptions for remote managed devices. The expected acceptance evidence is: Approved environments can connect and disallowed origins follow the configured restriction.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A mobile connected app must not continue operating indefinitely after a contractor's account is disabled. Its relevant condition is: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. The present case instead turns on: The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices. The direct answer here is: Apply supported connected-app network restrictions and test legitimate user paths before rollout.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A Salesforce-connected finance app must require High Assurance when employees authorize new access. Its relevant condition is: The app's session policy is set to Standard despite handling highly sensitive payroll information. The present case instead turns on: The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices. The direct answer here is: Apply supported connected-app network restrictions and test legitimate user paths before rollout.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise bans a previously trusted external app after detecting a vendor security incident. Its relevant condition is: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The present case instead turns on: The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices. The direct answer here is: Apply supported connected-app network restrictions and test legitimate user paths before rollout.
Question 480
A design workshop describes this environment: A new Salesforce connected app wants access from a narrow set of corporate networks. Which concrete observation should be documented as the most decisive issue?
- The app's session policy is set to Standard despite handling highly sensitive payroll information.
- Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain.
- The application issues persistent refresh tokens and has no documented inactivity or revocation procedure.
- The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices.
Explanation
Correct Answer
D:Best. The decisive observation is: The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices. This is why the design response should be: Apply supported connected-app network restrictions and test legitimate user paths before rollout.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A Salesforce-connected finance app must require High Assurance when employees authorize new access. Its relevant condition is: The app's session policy is set to Standard despite handling highly sensitive payroll information. The present case instead turns on: The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices. The direct answer here is: The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise bans a previously trusted external app after detecting a vendor security incident. Its relevant condition is: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The present case instead turns on: The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices. The direct answer here is: The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A mobile connected app must not continue operating indefinitely after a contractor's account is disabled. Its relevant condition is: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. The present case instead turns on: The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices. The direct answer here is: The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices.