ADM-201 Exam Dumps - Salesforce Administrator Questions and Answers

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.

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.

When a single object like Campaigns needs to support different " types " of marketing initiatives that require different fields or picklist values, the correct architectural solution is to use Record Types and Page Layouts. By creating distinct record types for " Email, " " Trade Show, " and " Webinar, " the Platform Administrator can assign a unique Page Layout to each. For example, the Trade Show layout might include fields for " Booth Number " and " Travel Costs, " while the Webinar layout might include " Webinar URL " and " Platform Provider. " This ensures that users only see the fields that are relevant to the specific type of campaign they are running, improving data quality and the user experience. While adding a custom field (Option B) would allow for categorization, it wouldn ' t hide irrelevant fields for different initiatives. Campaign Hierarchies (Option D) are used for relating parent and child campaigns but do not manage the specific data entry requirements for different initiative types.

Flow Builder is the recommended tool for automating updates to multiple related records based on a change to a single record. A " Record-Triggered Flow " can be configured to execute whenever an Opportunity is updated to " Closed Won " . The flow can then find all other Opportunities related to the same Account where the " IsClosed " field is false, and use an Update Records element to set their stage to " Closed Lost " . Outbound Messages (Option B) are used for notifying external systems, not for internal data updates 31 . Flow Orchestration (Option C) is designed for multi-user, complex business processes and would be overly complicated for this simple record update 32 . Quick Actions (Option D) require a user to click a button, which does not meet the requirement for automatic rendering upon the stage change 33 .

The " Minimum Access - Salesforce " profile is a very restrictive standard profile designed to provide no access by default, adhering to the principle of least privilege. One of the specific permissions that is not included in this profile is the Lightning Experience User permission. Without this system permission, users will be defaulted to the Salesforce Classic interface (or potentially blocked from any UI if no other access is granted). To resolve this, the Platform Administrator should either edit the custom profile or, preferably, create a Permission Set that includes the " Lightning Experience User " checkbox and assign it to the affected users. This " unlocks " the modern Lightning interface for them. Options B and C relate to the design of specific pages, but they are irrelevant if the user isn ' t even allowed to enter the Lightning environment. Option A refers to a different feature set entirely and does not address basic UI access.

Salesforce does not provide a robust, native " document merge " engine that can handle complex templates, headers, and advanced formatting out of the box. Therefore, the standard practice for implementing such a solution is to download a third-party application from the AppExchange. The AppExchange is the primary marketplace for Salesforce-integrated solutions, offering popular document generation tools like Conga Composer, Nintex DocGen, or S-Docs. These tools allow administrators to create professional-grade documents (like quotes, contracts, and invoices) by merging Salesforce record data into Word, PDF, or Excel templates. As a Platform Administrator, the process involves researching the best-fit app for the requirements, installing the package into a Sandbox for testing, and then deploying it to Production. This approach is highly efficient because it leverages existing, vetted technology that is specifically designed to handle the complexities of document generation, saving the organization from trying to build a costly and difficult-to-maintain custom solution using code or complex automation.

The requirement to have a record " signed off " by a specific individual (the CFO) based on a dollar threshold is a classic use case for an Approval Process . While the " Submit for Approval " button (Option A) allows a user to manually start the process, the prompt specifies that the process should happen " automatically " 50. To achieve this automation, the Platform Administrator should use Flow Builder to trigger the approval process . A Record-Triggered Flow can be set to run when an Opportunity is created or updated and meets the criteria (Amount > $100,000) . The flow would then use the " Submit for Approval " action to launch the record into the predefined approval process without requiring the sales rep to click a button . Einstein Next Best Action (Option B) is a recommendation tool, not a workflow enforcement tool54. Apex Triggers (Option C) could perform this task, but Salesforce best practices recommend using " clicks not code " (Flow) whenever possible for such requirements . Using Flow to launch an Approval Process provides the necessary automation, routing, and audit trail the CFO requires

To ensure a consistent, weekly " check-in " occurs, the Platform Administrator should enable the creation of recurring tasks. This feature allows a sales rep to create a single task (e.g., " Monday Check-in " ) and set a recurring frequency of " Weekly " on " Mondays. " Salesforce then automatically generates the next task in the series once the current one is completed. This is the most effective way to provide reps with a constant reminder in their task list. Additionally, because these are standard Task records, the administrator can easily build a report and a dashboard component to track the completion status of these check-ins for the VP. Time-based workflow (Option A) is typically for one-off alerts based on a date field, not for a permanent weekly habit. Email actions (Option C) and alerts (Option D) notify users but do not create the trackable task record required for the dashboard component.

The Opportunity Path is a visual tool that guides sales reps through the stages of a sales cycle. One of its most powerful features for administrators is the ability to define Key Fields for each individual stage. For example, when an opportunity is in the " Discovery " stage, the administrator can choose to display fields like " Budget " and " Decision Maker. " When the deal moves to " Negotiation, " the Path can be configured to surface " Contract Terms " and " Discount Percentage. " This ensures that reps are prompted to enter and review the most relevant data at exactly the right time in the process. While Dynamic Forms (Option D) can show or hide fields on the main record page, the Path specifically organizes this information at the top of the record in a way that is directly tied to the sales methodology. Workflow Rules (Option A) are a legacy automation tool that cannot modify the user interface. Path Key Fields empower sales teams to maintain focus and data accuracy throughout the deal lifecycle.

In Salesforce, access to reports and dashboards is determined by the folder in which they are stored. If a dashboard is in a shared folder, anyone with access to that folder can view it. To " temporarily remove " a specific dashboard from public view without affecting the rest of the folder ' s contents, the Platform Administrator should edit the dashboard ' s properties and move it to a private dashboards folder (such as " My Private Dashboards " ). Once moved, only the administrator (and those with high-level " View All Data " permissions) can see it while the changes are being made. Removing view access to the shared folder (Option A) would hide all dashboards in that folder, which is not the goal. Permission sets (Option C) control functional access (the ability to create or edit dashboards) but not individual record/dashboard visibility. Private groups (Option D) are for Chatter collaboration, not for managing dashboard folder security.