In Salesforce, Trusted IP Ranges (configured under Network Access in Setup) define a set of IP addresses from which users can log in without being prompted for a verification code (identity confirmation). In a call center environment where reps use different machines but are all within the same corporate network (sharing a common external IP or range), adding those corporate IPs to the Trusted IP Ranges list " streamlines " the login process. This prevents the system from seeing each new machine as an " unrecognized device " . Multi- factor Authentication (Option C) actually adds an extra step to the login process, which is the opposite of streamlining28. Profiles (Option A) and Permission Sets (Option D) can manage " Login IP Ranges " (which restrict access to specific IPs), but Trusted IP Ranges are the primary tool for bypassing identity verification within a known network.

When an administrator needs to extract a specific subset of records (e.g., Opportunities filtered by stage and date) with specific fields, the Data Loader is the most appropriate tool . Data Loader is a client application that allows for bulk operations, including " Export " and " Export All " 43. It allows the administrator to write a SOQL (Salesforce Object Query Language) query or use the built-in query builder to apply filters, such as StageName = ' Closed Won ' and CloseDate = LAST_90_DAYS44. The Data Import Wizard (Option B) is primarily used for importing data and has very limited export capabilities, usually confined to simple CSV samples45454545. The Data Export Service (Option D), also known as " Weekly Export, " is designed for full backup purposes; it exports the entire database into zip files and does not allow for specific filtering of records or fields for a quick ad-hoc report . Data Cloud (Option C) is a large-scale data platform and is overkill for a simple file export task47. Thus, for targeted, field-specific exports of 90 days of data, Data Loader is the standard choice .

When a user needs to be temporarily prevented from logging in-but their records, role, and historical data need to remain intact-the best practice is to Freeze the user. Freezing an account stops the user from accessing the system immediately without " Deactivating " them. Deactivation can be problematic if the user is a " running user " for dashboards or is part of active hierarchy logic that might break if the account is disabled. Freezing is a simple " one-click " action on the user record. Reassigning the license (Option A) would require deactivating the user first. Changing login hours (Option B) or IP addresses (Option D) at the profile level would impact all users assigned to that profile, not just the individual manager on leave. Freezing provides a targeted and temporary solution for managing individual user access.

When a user is locked out of Salesforce due to too many incorrect login attempts, the Platform Administrator must take specific actions on the user's record detail page to restore access. First, the administrator should click the Unlock button19. This clears the lockout status immediately20. Second, because the user likely forgot their credentials (causing the failed attempts), the administrator should use the Reset Password button21. This sends a temporary link to the user's email, allowing them to create a new password and log in successfully. "Logging in as the user" (Option A) is a troubleshooting tool for existing sessions but cannot bypass a lockout or change a password on the user's behalf. Changing "Password Policies" (Option D) would affect the entire organization and is not a valid way to help a single locked-out individual.

To avoid the administrative burden of creating and maintaining multiple identical dashboards for different teams, a Platform Administrator should use Dashboard Filters. By adding a filter based on the " Team Assigned " custom field, the administrator can create a single dashboard that the manager can toggle between
" Team A, " " Team B, " and " Team C " . Each time a filter value is selected, all components on the dashboard that use that field (or a mapped equivalent) will automatically refresh to show the data relevant only to that team. Creating separate dashboards (Option A) is inefficient and leads to " dashboard sprawl " .
Adding specific widgets for every team on one dashboard (Option B) would result in a cluttered and confusing interface61. Cross Filters (Option D) are a reporting feature used to filter records based on their relationship to other objects, not a dashboard-level viewing tool.