Salesforce Certified Platform Identity and Access Management Architect Practice Test 49
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.
Question 481
An architect must create an acceptance test after choosing: Apply supported connected-app network restrictions and test legitimate user paths before rollout. For the situation A new Salesforce connected app wants access from a narrow set of corporate networks. Which result most directly proves success?
- Read-only reports work while object writes and unrelated fields fail authorization tests.
- 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.
- Approved environments can connect and disallowed origins follow the configured restriction.
Explanation
Correct Answer
D:Best. The verification target is: Approved environments can connect and disallowed origins follow the configured restriction. It tests whether the chosen approach—Apply supported connected-app network restrictions and test legitimate user paths before rollout.—actually resolves the specific finding: The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices.
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 proposed deployment ignores trusted IP policies and access exceptions for remote managed devices. The direct answer here is: Approved environments can connect and disallowed origins follow the configured restriction.
B: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: Approved environments can connect and disallowed origins follow the configured restriction.
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: Approved environments can connect and disallowed origins follow the configured restriction.
Question 482
An incident scenario concerns this architecture: A new Salesforce connected app wants access from a narrow set of corporate networks. The team has discovered: The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices. Which project risk requires explicit mitigation?
- A compromised reporting token can administer unrelated CRM users and business data.
- 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
C:Best. The most direct failure is: Overly broad network rules allow unmanaged devices to obtain app sessions without review. It is a consequence of the documented condition: The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices. A mitigation is: 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 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 proposed deployment ignores trusted IP policies and access exceptions for remote managed devices. The direct answer here is: Overly broad network rules allow unmanaged devices to obtain app sessions without review.
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 proposed deployment ignores trusted IP policies and access exceptions for remote managed devices. The direct answer here is: Overly broad network rules allow unmanaged devices to obtain app sessions without review.
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 proposed deployment ignores trusted IP policies and access exceptions for remote managed devices. The direct answer here is: Overly broad network rules allow unmanaged devices to obtain app sessions without review.
Question 483
In this fictional project, A vendor integration used by a nonprofit requests full API scope for a read-only dashboard. The project team has uncovered that The administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions. Which action is best supported by those facts?
- 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.
- Configure appropriate refresh-token and session policies plus offboarding revocation controls.
- Combine minimal connected-app scopes with an appropriately restricted service-user license and permissions.
Explanation
Correct Answer
D:Best. The most direct action is to combine minimal connected-app scopes with an appropriately restricted service-user license and permissions. It is supported by the specific finding that the administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions. The expected acceptance evidence is: Read-only reports work while object writes and unrelated fields fail authorization tests.
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 administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions. The direct answer here is: Combine minimal connected-app scopes with an appropriately restricted service-user license and permissions.
B: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 administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions. The direct answer here is: Combine minimal connected-app scopes with an appropriately restricted service-user license and permissions.
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 administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions. The direct answer here is: Combine minimal connected-app scopes with an appropriately restricted service-user license and permissions.
Question 484
An enterprise review begins with this business situation: A vendor integration used by a nonprofit requests full API scope for a read-only dashboard. Which technical or process signal best identifies the obstacle?
- Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain.
- The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices.
- 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.
Explanation
Correct Answer
C:Best. The decisive observation is: The administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions. This is why the design response should be: Combine minimal connected-app scopes with an appropriately restricted service-user license and permissions.
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 administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions. The direct answer here is: The administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions.
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 administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions. The direct answer here is: The administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions.
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 administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions. The direct answer here is: The administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions.
Question 485
The team adopts this approach: Combine minimal connected-app scopes with an appropriately restricted service-user license and permissions. The original project scenario is: A vendor integration used by a nonprofit requests full API scope for a read-only dashboard. Which verification outcome best demonstrates that it worked?
- 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.
- Only the reviewed employee group can use the reporting connected app.
- Approved environments can connect and disallowed origins follow the configured restriction.
Explanation
Correct Answer
B:Best. The verification target is: Read-only reports work while object writes and unrelated fields fail authorization tests. It tests whether the chosen approach—Combine minimal connected-app scopes with an appropriately restricted service-user license and permissions.—actually resolves the specific finding: The administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions.
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 administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions. The direct answer here is: Read-only reports work while object writes and unrelated fields fail authorization tests.
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 administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions. The direct answer here is: Read-only reports work while object writes and unrelated fields fail authorization tests.
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 administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions. The direct answer here is: Read-only reports work while object writes and unrelated fields fail authorization tests.
Question 486
A project manager declines to address this finding: The administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions. The related project is: A vendor integration used by a nonprofit requests full API scope for a read-only dashboard. Which consequence most directly follows?
- A compromised reporting token can administer unrelated CRM users and business data.
- A former contractor uses stored refresh tokens long after the business relationship ends.
- 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.
Explanation
Correct Answer
A:Best. The most direct failure is: A compromised reporting token can administer unrelated CRM users and business data. It is a consequence of the documented condition: The administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions. A mitigation is: Combine minimal connected-app scopes with an appropriately restricted service-user license and permissions.
Incorrect Answers
B: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 administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions. The direct answer here is: A compromised reporting token can administer unrelated CRM users and business data.
C: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 administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions. The direct answer here is: A compromised reporting token can administer unrelated CRM users and business data.
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 administrators assume selecting a smaller OAuth scope eliminates all need for Salesforce permissions. The direct answer here is: A compromised reporting token can administer unrelated CRM users and business data.
Question 487
An architecture board reviews a proposed Salesforce integration. Context: An enterprise bans a previously trusted external app after detecting a vendor security incident. Finding: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. Which decision best resolves the concern?
- Apply the supported connected-app block/revocation policy and inspect remaining token/session use.
- Restrict application access to approved users and govern grants through profile or permission-set authorization.
- Map authoritative job groups to approved Salesforce permission-set groups and remove stale grants.
- Configure appropriate refresh-token and session policies plus offboarding revocation controls.
Explanation
Correct Answer
A:Best. The most direct action is to apply the supported connected-app block/revocation policy and inspect remaining token/session use. It is supported by the specific finding that Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The expected acceptance evidence is: Existing and future access from the blocked application are contained and auditable.
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: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The direct answer here is: Apply the supported connected-app block/revocation policy and inspect remaining token/session use.
C:Not best for this scenario. This option is associated with another type of requirement: An HR directory updates an employee's department while the old Salesforce permission set remains assigned. Its relevant condition is: Provisioning updates basic user fields but has no entitlement reconciliation process. The present case instead turns on: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The direct answer here is: Apply the supported connected-app block/revocation policy and inspect remaining token/session use.
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: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The direct answer here is: Apply the supported connected-app block/revocation policy and inspect remaining token/session use.
Question 488
A design workshop describes this environment: An enterprise bans a previously trusted external app after detecting a vendor security incident. Which concrete observation should be documented as the most decisive issue?
- The proposed deployment ignores trusted IP policies and access exceptions for remote managed devices.
- 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.
- Connected-app permitted-user policy allows all users to self-authorize new sessions without prior review.
Explanation
Correct Answer
C:Best. The decisive observation is: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. This is why the design response should be: Apply the supported connected-app block/revocation policy and inspect remaining token/session use.
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: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The direct answer here is: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain.
B: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: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The direct answer here is: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain.
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: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The direct answer here is: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain.
Question 489
An architect must create an acceptance test after choosing: Apply the supported connected-app block/revocation policy and inspect remaining token/session use. For the situation An enterprise bans a previously trusted external app after detecting a vendor security incident. Which result most directly proves success?
- The user retains only access required for the new job after synchronized lifecycle updates.
- Read-only reports work while object writes and unrelated fields fail authorization tests.
- Only the reviewed employee group can use the reporting connected app.
- Existing and future access from the blocked application are contained and auditable.
Explanation
Correct Answer
D:Best. The verification target is: Existing and future access from the blocked application are contained and auditable. It tests whether the chosen approach—Apply the supported connected-app block/revocation policy and inspect remaining token/session use.—actually resolves the specific finding: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain.
Incorrect Answers
A:Not best for this scenario. This option is associated with another type of requirement: An HR directory updates an employee's department while the old Salesforce permission set remains assigned. Its relevant condition is: Provisioning updates basic user fields but has no entitlement reconciliation process. The present case instead turns on: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The direct answer here is: Existing and future access from the blocked application are contained and auditable.
B: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: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The direct answer here is: Existing and future access from the blocked application are contained and auditable.
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: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The direct answer here is: Existing and future access from the blocked application are contained and auditable.
Question 490
An incident scenario concerns this architecture: An enterprise bans a previously trusted external app after detecting a vendor security incident. The team has discovered: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. Which project risk requires explicit mitigation?
- A former contractor uses stored refresh tokens long after the business relationship ends.
- A user with only basic authentication can enter the protected finance application.
- 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.
Explanation
Correct Answer
C:Best. The most direct failure is: A hidden application keeps pulling records despite being removed from the user navigation. It is a consequence of the documented condition: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. A mitigation is: Apply the supported connected-app block/revocation policy and inspect remaining token/session use.
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: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The direct answer here is: A hidden application keeps pulling records despite being removed from the user navigation.
B: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: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The direct answer here is: A hidden application keeps pulling records despite being removed from the user navigation.
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: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The direct answer here is: A hidden application keeps pulling records despite being removed from the user navigation.