Salesforce ADM-201 Questions Answers

In Salesforce reporting, administrators can use relative date and user filters to make a single report template dynamic for every person who views it. By setting the filter to Opportunity Owner (or Order Owner) equals $USER, the report will automatically filter the results to show only those records owned by the individual currently logged in and viewing the report. This is much more efficient than creating separate reports for every rep. While setting the Organization-Wide Defaults to Private (Option C) would restrict general visibility, it does not help if the reps need to be able to see each other ' s data for other business reasons but simply want a " clean " personal view for daily tasks36. Saving the report in a private folder (Option D) only restricts who can see the report itself, not the data contained within it. Using the $USER variable is the standard way to provide personalized, relevant data views in a shared reporting environment.

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.

The most efficient and standard way to automate case creation from inbound emails is by using Email-to-Case . When setting up Email-to-Case, the Platform Administrator configures " Routing Addresses " . For each routing address (e.g., support@company.com or billing@company.com), the administrator can specify a default owner or queue for the cases created via that specific address . This ensures that when a customer sends an email to the " Support " address, it is automatically routed to the Support Queue, and an email to the " Billing " address is routed to the Billing Queue . This configuration is handled directly within the Email-to-Case setup pages and does not require additional escalation rules (Option A) or complex custom flows (Option C) for the initial assignment . While a custom email service (Option B) is possible, it is a developer-centric approach that is generally unnecessary given the robust native capabilities of the standard Email-to-Case feature . This setup streamlines the intake process and ensures that customer issues are immediately visible to the correct service team34.

Escalation Rules are designed specifically to perform actions when a Case record has remained in a certain state (like " Open " ) for a specified period. In this scenario, the Platform Administrator would set an escalation rule entry with the age set to 168 hours (7 days). When this time threshold is reached, the rule can automatically reassign the case to a new owner or a management queue 51 . Assignment Rules (Option C) are only triggered upon the initial creation of a record or when manually triggered by a user, and they do not have a built-in " timer " capability to fire days later 52 . Auto-Response Rules (Option B) are only for sending automated emails to customers, not for internal ownership changes 53 . Validation Rules (Option D) are used to prevent data entry errors and cannot change record ownership 54 .