Salesforce Plat-Admn-201 Exam Questions

In the Lightning App Builder, Component Visibility Filters allow an administrator to show or hide parts of a record page based on specific criteria, such as the user's profile, a field value, or the record type. This is the best way to make pages 'dynamic.' For example, the administrator can configure a 'Financial Details' component to only appear when the user viewing the case has the 'Finance User' profile, or hide a 'Recall Instructions' component unless the 'Case Reason' is set to 'Product Defect.' This prevents 'information overload' by ensuring that users only see the tools and data relevant to their specific role or the current state of the record. Simply deleting components (Option D) or removing fields (Option C) would affect all users equally, failing to provide role-specific utility. Component visibility creates a personalized, streamlined experience that improves user productivity and reduces clutter on complex record pages.

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 the Salesforce Setup menu, Company Settings (formerly Company Profile) is the central location where global organizational parameters are managed. This section contains several key settings. Under Company Information, the admin can view the Org ID, default time zone, and primary currency. The Fiscal Year settings allow the admin to define whether the organization follows a standard Gregorian calendar or a custom fiscal cycle. Business Hours are used to define the working times for the organization, which is critical for calculating milestones in Service Cloud or escalation rules. If Multi-Currency is enabled, this is also where exchange rates and active currencies are managed. Viewing and configuring these settings is a foundational task for any Platform Administrator, as they establish the baseline for how data is interpreted and how time-based automation functions across the entire instance. Ensuring these are correct is vital for accurate financial reporting and maintaining service level agreements (SLAs).

Opportunity Update Reminders is a specific, automated feature in Salesforce designed exactly for this purpose. When enabled, it allows managers to automatically send an email to their direct reports with a list of their open opportunities. The email serves as a prompt for the reps to review their deals and ensure close dates, amounts, and stages are current. This is more effective than a general Scheduled Report (Option D) because it is a purpose-built notification system that can be configured by the manager. Big Deal Alerts (Option C) are for high-value deal notifications, not general pipeline hygiene. Similar Opportunities (Option A) helps with sales strategy but does not encourage record updates.

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