ADM-201 Exam Dumps - Salesforce Administrator Questions and Answers

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.

The Data Import Wizard is the ideal tool for importing a relatively small number of records (up to 50,000) when those records involve standard objects like Accounts and Contacts simultaneously. One of the unique strengths of the Data Import Wizard is its ability to handle "Account and Contact" imports in a single pass, automatically linking the contacts to the correct accounts based on name or site. Because the volume in this request is only 300 records, the Data Import Wizard provides a simple, browser-based interface that includes built-in duplicate checking, which is highly beneficial for maintaining data quality. While the Data Loader (Option D) and Dataloader.io (Option A) can also handle 300 records, they are typically reserved for much larger datasets (up to 5 million records) or more complex objects. The "Wizard" is the most user-friendly and efficient choice for this specific sales rep request.

When the Organization-Wide Default (OWD) for an object is set to Private, users can only see records they own or those shared with them. While the Role Hierarchy automatically grants "upward" visibility (managers see what subordinates own), it does not naturally allow for "lateral" visibility or visibility across different branches of the hierarchy. To solve this, a Platform Administrator should use Sharing Rules. Sharing Rules allow the admin to create exceptions to the Private OWD based on record ownership or specific criteria. For example, the admin can create an "Owner-based Sharing Rule" that shares all records owned by the "East Coast Sales" role with the VP of Sales (or a Public Group the VP belongs to). This provides a scalable way to grant the necessary visibility for reporting without making the data public to the entire company. Sharing Rules are a core security feature that ensures the right people have access to the right data while maintaining the principle of least privilege.

To ensure that a field is populated on every single record, regardless of how it is created (manually, via API, or through an integration), the best method is to make the field universally required at the field definition level. When a field is marked as "Required" in the Object Manager, the Salesforce database will reject any attempt to save a record if that field is empty. While requiring a field on a Page Layout or Record Type (Option B) provides a good user experience for manual entry, it does not prevent records from being created without that data via the API or background processes25. Using a flow (Option A) to update the field is reactive rather than preventative26. Universal requirement is the most robust way to maintain data integrity for critical fields like "Billing System" that are essential for reporting and external system alignment.

Case Escalation Rulesare specifically designed to automate actions when a case has remained in a certain state for a defined period of time. In this scenario, the requirement involves two specific time-based triggers: moving the case after 2 hours and alerting a manager. Escalation rules allow the administrator to define "Escalation Actions" that execute when the time threshold is reached, such as "Reassign to Queue" and "Notify Manager". Case Assignment Rules (Option D) only fire when a case is first created or manually triggered, not after a time delay63. Reports (Option A) and Dashboards (Option B) provide information but do not physically move records or perform automated reassignments.

The Activity Timeline is a standard Lightning component that displays open tasks, upcoming events, and past activities (like logged calls or sent emails) in a chronological view. If this timeline is missing from an Account page, it is usually because the component has been removed from the Lightning Record Page layout. To fix this, the Platform Administrator should open the Account record in the Lightning App Builder. From the list of standard components on the left, the admin must drag the Activities component onto the page canvas—typically in the right-hand column or a dedicated tab. Once the page is saved and activated, the timeline will be visible to users. Visibility of the timeline is a layout configuration, not a specific "Edit access" permission (Option B). Running a report (Option C) might confirm if data exists, but it won't fix the UI issue. There is no "button" for the Activity Timeline in the Object Manager (Option D); it is managed strictly as a component within the App Builder.

Case Assignment Rules are the standard Salesforce tool for automatically routing cases to specific users or queues based on record criteria. A single assignment rule can contain multiple "Rule Entries" processed in a specific order. To meet this requirement, the Platform Administrator would create a rule with two entries: one that checks if the Account's "Level" field equals "Platinum" and routes it to the Priority Support Queue, and another that checks if the level is "Silver" or "Gold" and routes it to the Regular Support Queue. This automation happens the moment the case is created, ensuring that high-value customers receive immediate attention from the appropriate team. Escalation Rules (Option A) are used to move a case after it has been sitting for a period of time, not for initial routing. Workflow Rules (Option D) are a legacy tool that cannot natively assign cases to queues in the same direct manner as Assignment Rules.

The Kanban view provides a visual representation of a set of records, such as an opportunity pipeline, organized by a specific field like "Stage". It allows sales teams to see all their deals as cards in columns. The primary benefit of Kanban is its "drag-and-drop" functionality, which lets users move a card from one column to another to automatically update the stage, effectively "moving opportunities forward" with minimal effort. While reports (Option A) and dashboards (Option B) provide visual summaries, they do not allow for the interactive, one-click record updates that the Kanban view offers11. Standard list views (Option D) show data in a grid format which is less visual for tracking pipeline progress compared to the column-based Kanban layout.

A Validation Rule is the only way to enforce conditional requirement logic based on both record data (the stage) and user data (the user's profile or role). To achieve this, the Platform Administrator would write a formula that checks three things: if the Stage is "Negotiation," if the Amount field is blank, and if the user is not a manager. The formula would look something like: AND(ISPICKVAL(StageName, "Negotiation"), ISBLANK(Amount), $Profile.Name <> "Sales Manager"). This allows the system to block standard sales users from saving the record without an amount, while the exception for the manager's profile allows them to bypass the requirement. Making the field required on the page layout (Option A) would affect all users equally, failing to meet the requirement for managers. Assigning the Admin profile to managers (Option B) is a major security risk and violates the principle of least privilege.1

In the Salesforce Lightning Experience, the fields displayed in the "header" of a record and on the cards in the Kanban view are controlled by the Compact Layout. Each object has a System Default compact layout, but a Platform Administrator can create custom ones to prioritize the most important information, such as "Account Name" and "Close Date." By editing the primary compact layout for the Opportunity object, the admin directly controls which fields the sales team sees as they drag and drop deals through the Kanban stages. While Page Layouts (Option C) control the main record detail page and Kanban Settings (Option D) control which field is used for columns and summaries, the individual "card" content is always driven by the Compact Layout. This ensures that users can quickly gather key context without needing to open every individual record.