ADM-201 Exam Dumps - Salesforce Certified Platform Administrator (Plat-Admn-201)

Escalation Rulesare specifically designed to ensure that cases do not violate a company's Service Level Agreements (SLAs). When a case meets predefined criteria and remains open for a specific duration—such as two hours or seven days—the escalation rule automatically triggers. A Platform Administrator can configure these rules to perform two primary actions: reassigning the case to a different user or queue (such as a Tier 2 support team) and sending notification emails to managers or the new owner to ensure the delay is addressed. While Milestones and Entitlements (Option A) are used to track and display SLA compliance on a record, Escalation Rules are the functional engine used to physically "route" or move the record based on time-based triggers. Omni-Channel (Option B) handles real-time routing based on agent availability rather than time-elapsed thresholds. Auto-Response Rules (Option C) are used only to send initial confirmation emails to customers upon case creation.

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.

To "undo" a mistaken import, the administrator must delete the incorrectly created records. Two standard tools facilitate this:

Mass Delete Records (Option D):This is a browser-based tool in Setup that allows administrators to delete up to 250 records at a time (standard) or use criteria to identify and remove larger sets of records. It is the quickest way for smaller mistakes.

Data Loader (Option B): For large-scale errors, the administrator can use the Success file generated during the original import (which contains the new record IDs) and perform a "Delete" operation.

The Data Import Wizard (Option C) is for adding or updating data, but it does not have a "Delete" function. Weekly Data Export (Option A) is a backup tool and cannot be used to remove existing data from the system.

In Salesforce, Trusted IP Ranges (configured under Network Access in Setup) define a set of IP addresses from which users can log in without being prompted for a verification code (identity confirmation). In a call center environment where reps use different machines but are all within the same corporate network (sharing a common external IP or range), adding those corporate IPs to the Trusted IP Ranges list "streamlines" the login process. This prevents the system from seeing each new machine as an "unrecognized device". Multi-factor Authentication (Option C) actually adds an extra step to the login process, which is the opposite of streamlining28. Profiles (Option A) and Permission Sets (Option D) can manage "Login IP Ranges" (which restrict access to specific IPs), but Trusted IP Ranges are the primary tool for bypassing identity verification within a known network.

A Roll-up Summary Field is a powerful feature that calculates values from related records and displays them on a master record. However, this functionality is natively available only on the "Master" side of a Master-Detail relationship. For standard objects, Salesforce provides a built-in Master-Detail-like relationship between Accounts and Opportunities. Specifically, the Account object acts as the master, and the Opportunity object acts as the detail. This relationship allows a Platform Administrator to create roll-up summary fields on the Account to calculate the sum of "Total Opportunity Amount," the "Minimum Close Date," or a "Count" of all related opportunities. Other standard objects like Contacts (Option B) and Cases (Option C) have a lookup relationship to Accounts rather than a master-detail relationship, and therefore do not support native roll-up summaries20. Campaigns (Option D) also do not share this specific relationship with Accounts21. If an administrator needs to roll up data from these other objects, they would typically need to use a custom solution like Flow Builder or a third-party app, whereas Opportunities are supported natively out of the box.