An identity professional is working on the configuration of a connected app for Universal Container’s...

When an architect needs to enforce IP restrictions, session timeouts, or related access controls for a connected app, the place to do that is the connected app’s OAuth policies. Those policies let Salesforce administrators shape how the app can be used, from permitted-user policy to IP relaxation behavior and session-related restrictions. Login IP ranges on profiles are broader user controls, while custom permissions don’t govern the connected app’s OAuth runtime behavior. The important architecture distinction is that connected-app security should be controlled where the app trust is defined. Salesforce puts those controls in the connected app’s policy layer, which is why OAuth policies are the right answer for app-specific session and network enforcement. This is why option D is the best answer in Salesforce terms.