ADM-201 Exam Dumps - Salesforce Administrator Questions and Answers

Agentforce is designed to handle multi-step processes that require reasoning and adaptation. Unlike traditional automation (like Workflow or simple Bots) that follows a linear, " If-This-Then-That " path, an Agentforce agent uses generative AI to understand user intent and choose the best sequence of actions to reach a goal. If a customer ' s request changes mid-conversation or requires the agent to check multiple systems and make a judgment call, the agentic loop allows it to adapt its behavior in real-time. Single-step processes (Option A) or tasks without decision-making (Option D) are better handled by standard Flow or Macros, which are more cost-effective for simple tasks. Static document generation (Option B) is a fixed output task. Agentforce ' s true value lies in managing the " gray areas " of business processes where human-like flexibility is needed.

To track specific stages of a support process and measure the time elapsed within those stages, Salesforce provides Entitlements and Milestones . Milestones represent required steps in a support process, such as " First Response Time " or " Resolution Time " 363636. When combined with Business Hours, Milestones allow the system to accurately calculate how long a case has been in a particular status or assigned to a specific team, excluding weekends or non-working hours . This provides leadership with granular reporting on " Team Performance " and SLA compliance . Escalation Rules (Option A) and Assignment Rules (Option C) are primarily routing tools; they can move a case but do not natively provide the timestamp-based tracking and reporting necessary to see duration across multiple " handoffs " . Record-Triggered Flows (Option B) could theoretically be used to stamp fields, but this would require significant custom development and would not offer the native, out-of-the-box reporting dashboards that come with the Milestones feature40. Therefore, Entitlement Management is the standard solution for tracking time-based service metrics41.

Big Deal Alerts are a specialized, " out-of-the-box " notification feature specifically for the Opportunity object. This tool allows a Platform Administrator to define a threshold based on " Amount " and " Probability. " When an opportunity is created or updated and meets these thresholds (in this case, > $250k and > 75%), Salesforce automatically sends an email notification to a specified user or a list of stakeholders. This is the most efficient way to meet the requirement because it is a native feature designed exactly for high-value deal visibility. While Reports and Dashboards (Option C) can display this data, they are " pull " mechanisms that require leadership to actively check them, whereas a Big Deal Alert is a " push " mechanism that ensures immediate awareness. Guidance for Success (Option A) provides tips within a sales path, and Similar Opportunities (Option D) helps reps find related deals, but neither is designed for automated leadership notifications.

To organize related marketing initiatives and simplify reporting, Salesforce utilizes Campaign Hierarchies. A hierarchy allows an administrator to link multiple campaigns together using the " Parent Campaign " field. In this scenario, the admin should create a " Parent " campaign to represent the entire networking series and then create individual " Child " campaigns for each monthly event. This structure provides two major benefits: it allows the sales rep to see the specific performance (ROI, members, responses) of a single monthly event, and it uses " Hierarchy Total " fields to automatically roll up all those metrics to the parent level. This provides a holistic view of the entire series ' success without requiring complex manual calculations. Using the same name for campaigns (Option A) leads to data confusion, and while member statuses (Option B) are useful, they do not provide the structural " series vs. month " reporting required here. Campaign Hierarchy is the standard architectural approach for multi-touch or recurring marketing efforts.

The Company Information page in the Setup menu is the " source of truth " for an organization ' s high-level metadata and licensing. In the User Licenses related list on this page, the administrator can see every license type purchased (e.g., Salesforce, Salesforce Platform, Force.com), the total number of seats allocated, the number of seats currently in use, and the number of remaining available licenses. This is the first place an administrator should look for budgeting and capacity planning. " Usage-based entitlements " (Option A) tracks limited-resource features like Login minutes or Data Cloud credits, but not standard seat-based user licenses. Searching for license types (Option B) or checking user management settings (Option D) will not provide a consolidated summary of the total license pool.

The most efficient and descriptive way to troubleshoot a flow is to use the native Debug feature within the Flow Builder. This tool allows the Platform Administrator to " run " the flow in a safe environment, simulating the creation or update of a record. As the flow executes, the Debugger provides a step-by-step panel showing exactly how variables were assigned, which paths were taken in " Decision " elements, and whether any " Update " or " Create " elements failed. It explicitly highlights where an error occurred and provides a detailed error message. While general Debug Logs (Option D) can capture flow information, they are much harder to read and require setting specific trace flags. The Setup Audit Trail (Option A) only shows configuration changes, not runtime errors. Email logs (Option B) are only useful if the flow is failing to send an email. The Flow Debugger is the primary tool for administrators to refine logic and fix issues before activating automation.

When a single picklist field needs to show different values to different users or for different business contexts, Record Types are the configuration point. While the master list of all possible values is defined in " Fields and Relationships " (Option D) or a " Global Value Set " (Option C), the Record Type determines which of those values are " available " for a specific type of record. For example, a " Wholesale " record type might show different discount levels than a " Retail " record type. If users are seeing inconsistent or incorrect options, the Platform Administrator must go to the specific Record Type settings for the Opportunity object, find the picklist in question, and move values between the " Available " and " Selected " columns. This provides a tailored user experience and prevents users from selecting values that do not apply to the specific type of record they are managing.

When users click the " New Report " button, they are presented with a list of Report Types, which act as templates determining which objects and fields are available for the report. Often, an org has many standard report types that are irrelevant or confusing to the average user. To " limit the kinds of reports " and simplify the user experience, a Platform Administrator can use the Select Report Types to Hide feature in the Report and Dashboard Settings. By hiding unnecessary or redundant report types, the admin ensures that users only see the specific templates that align with company reporting standards. This reduces the risk of users creating inaccurate reports using the wrong data models. Report Folder Sharing (Option B) controls who can view or edit existing reports, but it does not restrict the creation of new ones from specific templates. While creating Custom Report Types is a way to define what data is available, the specific act of " limiting " the visible list is handled by the " Hide " functionality.

The Salesforce AppExchange is a vast marketplace designed to extend the functionality of a Salesforce organization through various types of solutions.

Components: Administrators can find pre-built Lightning Components (A) to enhance record pages, such as custom maps, weather widgets, or specialized data entry forms. These can be dragged and dropped directly in the Lightning App Builder.

Consultants: The AppExchange also serves as a directory for certified Salesforce Consultants (D). This allows organizations to find and vet professional partners who specialize in specific industries or technical implementations to help them scale their Salesforce instance.

While " Communities " (Option C) refers to a Salesforce product (now Experience Cloud), you don ' t " find " them on the AppExchange to enhance an org; rather, you might find packages to enhance them. " Customers " (Option B) are not a solution found on the marketplace. By leveraging the AppExchange, a Platform Administrator can quickly implement proven solutions without the need for extensive internal development.

There are two primary ways to display different picklist values to different groups of users. The first, and most common, is using Record Types (Option C). A single picklist field can have its available values filtered at the Record Type level. By creating a " Sales " record type and a " Marketing " record type, the admin can select which values are visible for each. These record types are then assigned to the respective users ' profiles. The second method (Option D) involves using different Page Layouts and two separate picklist fields. In this scenario, the admin creates two distinct fields (e.g., " Sales Category " and " Marketing Category " ) and places only the relevant field on the page layout assigned to that specific team. This is less common but effective if the data needs to be stored in entirely different buckets. Option B is incorrect because profiles themselves do not filter picklist values; they only control which record types a user can access.