ADM-201 Salesforce Certified Platform Administrator (Plat-Admn-201) Free Practice Exam Questions (2026 Updated)

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 allow users to post snapshots of dashboard components and engage in discussions about data directly on the dashboard, the Platform Administrator must enable Feed Tracking for dashboards. In Salesforce, Chatter Feed Tracking allows changes to records and interactions to be tracked and shared in the Chatter feed. For dashboards specifically, enabling this feature allows users to " Follow " a dashboard and use the " Post to Feed " functionality on individual dashboard components. This is highly effective for management teams who want to call out specific successes or areas of concern by tagging team members in a post that includes the visual chart. Reporting snapshots (Option A) are used for historical trend reporting, not social sharing. Downloading charts (Option B) is a manual file-handling process rather than an integrated social feature. Setting the " View Dashboard As " (Option C) determines data visibility but does not control Chatter functionality.

Salesforce Approval Processes allow administrators to define a series of steps to automate the approval of records. Within these processes, there are four specific types of automated actions that can be triggered during initial submission, approval, rejection, or recall:

Field Update: Used to change a value on the record, such as switching a " Status " field from " Pending " to " Approved. "

Email Alert: Used to send a templated email to specific users, such as notifying the submitter that their request was granted.

Task: Used to assign a follow-up task to a user.

Outbound Message: Used to send technical data to an external system via API.

While modern automation tools like Flow can post to Chatter or launch other flows, the native approval process engine is limited to these four specific actions. For a " time-off request " scenario, an Email Alert ensures the employee is notified, and a Field Update ensures the record reflects the new status, providing a clear audit trail of the business decision.

In the Salesforce Lightning Experience, the Highlights Panel at the top of a record page is controlled by the Compact Layout. The compact layout determines which fields (up to 7) appear in the record header and in the hover-over details. To add a new custom field to this area, the Platform Administrator must go to the Object Manager for Accounts, select Compact Layouts, and either edit the existing primary layout or create a new custom one. After adding the custom text area field to the " Selected Fields " list and saving, the field will immediately appear in the Highlights Panel for users. It is a common misconception that the standard Page Layout editor (Option D) controls the highlights panel; while the page layout controls the " Details " section and " Related Lists, " it does not manage the header area. Option B might make the field easier to find in the details section but will not place it in the highlights panel.