IDENTITY-AND-ACCESS-MANAGEMENT-ARCHITECT practice question 30 of 30

Universal containers (UC) uses a legacy Employee portal for their employees to collaborate and post their ideas. UC decides to use salesforce ideas…

Full set: 248 questions
Universal containers (UC) uses a legacy Employee portal for their employees to collaborate and post their ideas. UC decides to use salesforce ideas for voting and better tracking purposes. To avoid provisioning users on Salesforce, UC decides to push ideas posted on the Employee portal to salesforce through API. UC decides to use an API user using Oauth Username - password flow for the connection. How can the connection to salesforce be restricted only to the employee portal server?
Answer options
A: Add the Employee portals IP address to the Trusted IP range for the connected App Correct answer
B: Use a digital certificate signed by the employee portal Server.
C: Add the employee portals IP address to the login IP range on the user profile.
D: Use a dedicated profile for the user the Employee portal uses.
Correct Answer:
A. Add the Employee portals IP address to the Trusted IP range for the connected App
Explanation

The most direct and specific method to restrict an API connection for a particular integration is at the application entry point, which is the Connected App. By defining a "Trusted IP Range" directly on the Connected App settings, Salesforce will only allow OAuth requests for that app to originate from the specified IP addresses, such as the Employee Portal server. This isolates the restriction to this specific integration, adhering to the principle of least privilege for the application's access scope. This method is more granular than profile-level restrictions as it applies only to this specific connection point.

Why Incorrect

B. This suggests a different authentication mechanism (like JWT Bearer flow) and is not applicable to the specified OAuth Username-Password flow.
C. While functional, this restricts the user at the profile level. This is a broader control than necessary and less specific than restricting the Connected App directly.
D. Using a dedicated profile is a security best practice for the integration user, but it does not, by itself, implement any IP-based restrictions. ---

References

1. Salesforce Help Documentation, "Manage IP Addresses for a Connected App": This document explicitly states, "You can limit the IP addresses from which users can access a connected app. You do this by defining a permitted IP range on the connected app’s definition." This directly supports configuring the IP range on the Connected App itself. (Salesforce Help, Article 000327938).

2. Salesforce Help Documentation, "Edit a Connected App": In the detailed settings for a Connected App, under the "IP Relaxation" section, the option to "Enforce IP restrictions" and define a specific "Trusted IP Range for the Connected App" is described. The documentation confirms that when this range is set, "a login from an unspecified IP address is denied." (Salesforce Help, Article 000326252).

3. Salesforce Security Guide, "Control API Access" section: This guide discusses various layers of security. It outlines that Connected App policies, including IP range restrictions, provide application-specific controls, which is a more granular approach than profile-level settings for securing a specific integration point. (Refer to the "Connected App IP and Session Policies" subsection).

4. Salesforce Help Documentation, "Restrict Login IP Ranges in the Original Profile User Interface": This document describes profile-level IP restrictions. While a valid security control, it applies to all login attempts by the user, not just through a specific Connected App, making it a less precise solution for the stated requirement. (Salesforce Help, Article 000320381).

Scroll to Top