Pass the Salesforce Salesforce Administrator ADM-201 Questions and answers with CertsForce

The Lightning App Builder is the primary tool for creating custom user interfaces in both the desktop and mobile versions of Salesforce. For mobile customization, administrators primarily focus on two page types:

App Page:These are custom "landing pages" or "home pages" for an app. They can contain a mix of components like lists, charts, and flows, and they appear as items in the mobile navigation menu.

Record Page: These allow administrators to customize the layout of a specific object (like an Account or a custom Property record) for mobile users. Admins can use "Component Visibility Rules" to show or hide specific sections when the record is viewed on a mobile device, ensuring a streamlined experience on smaller screens.

There is no such thing as a "User Page" (Option B) in the App Builder. While dashboards can be viewed on mobile, they are created in the Dashboard Builder, not the Lightning App Builder (Option D).

To align the Salesforce mobile app with a company's visual identity, a Platform Administrator can customize specific branding elements through the Salesforce Mobile App Customization settings. The two primary areas available for branding are:

Loading Page Logo:This allows the administrator to upload a company logo that appears when a user first opens the app.

Header Background Color: This allows the administrator to set the primary brand color for the top header area of the mobile interface.

These settings ensure that the user experience feels consistent with the company's internal branding from the moment they log in. Option A and B are incorrect because Salesforce does not currently allow for granular "App header" vs "Header background" color separation or the modification of the "Record background color," as the app maintains a standardized background for accessibility and readability. Customizing the loading screen and header is the standard way to implement a mobile rebrand.

Access to the Service Console and other advanced Service Cloud features (like Entitlements or Knowledge) requires a specific Feature License called the Service Cloud User. Even if a user's profile has the "Manage Cases" permission, they will not be able to access the specialized Console app unless the "Service Cloud User" checkbox is selected on their individual User record. This is a common administrative step when onboarding new support staff. Permission sets (Option B) grant functional permissions but cannot grant feature licenses. Assigning a "Platform User License" (Option D) would actually restrict them, as that license type does not include access to standard CRM objects like Cases or the Service Console.

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.

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.

The Setup Audit Trail is the primary tool for tracking administrative and configuration changes within a Salesforce organization. It records a history of modifications made by any administrator, including the date and time of the change, which user made it, and exactly what was altered (e.g., creating a new field, changing a profile permission, or modifying a workflow rule). The history is available for the last six months of activity. Health Check (Option A) is a security tool that compares your settings against Salesforce standards. History Tracking (Option C) and Feed Tracking (Option D) are used to track changes to records (like an Account's phone number), whereas the Setup Audit Trail is dedicated to tracking metadata and system configuration.

A Master-Detail Relationship is a tight coupling between two objects that provides several unique functionalities:

Master Object Types:The master can be either a standard object (like Account) or a custom object (Option B).

Roll-up Summaries:This relationship type is the only one that natively supports Roll-up Summary fields, allowing the master record to calculate counts, sums, or averages of fields on the detail records (Option C).

Ownership and Security: The detail record inherits its owner and its security/sharing settings from the master record. Consequently, there is no "Owner" field on a detail record; it is always owned by the owner of the master (Option D).

Option A is incorrect because detail records cannot have independent permissions. Option E is incorrect because an object can only have a maximum of two master-detail relationships. This relationship is ideal for parent-child scenarios where the child's existence is entirely dependent on the parent.

For an AI agent to provide "complete and accurate" support, it needs access to a unified, 360-degree view of the customer data. Data Cloud is the critical prerequisite because it ingests, harmonizes, and unifies data from multiple sources (Salesforce, external databases, legacy systems) into a single "Unified Profile." When Agentforce is "grounded" in Data Cloud, it can reference real-time customer interactions, purchase history, and cross-channel behavior that might not exist in a single Case or Contact record. Without Data Cloud, the agent's knowledge is limited to siloed data, which increases the risk of providing incomplete or irrelevant answers. While Console layouts (Option B) and intake methods (Option A) are important for the UI, they do not provide the data foundation necessary for advanced AI reasoning.

Salesforce allows for the creation of multiple Business Hours records to support global teams working in different time zones. To solve the requirement for Ursa Major Solar, the Platform Administrator should create two distinct sets of business hours: one for "Pacific Support" (9 AM - 5 PM PT) and one for "Eastern Support" (9 AM - 5 PM ET). This is essential because Business Hours are used by the system to calculate escalation rules and milestones correctly. For example, an escalation rule for an Eastern-based case 1should start counting at 9 AM ET, not 9 AM PT. Adjusting the current record to "accommodate" both (Option A) would result in a 12-hour window that doesn't accurately reflect either team's true availability. Users cannot manually set their own business hours (Option B) in a way that affects system automation. Creating one set per time zone ensures that the support team's performance metrics and automated routing are accurate and localized.

For a custom object to support Tasks and Events, the "Allow Activities" setting must be enabled in the object's properties. When a Platform Administrator creates a custom object, this checkbox is often left unchecked by default35. Enabling this feature allows the "Related To" (WhatId) field on a Task or Event to be linked to records of that custom object type36. While adding the related list to the page layout (Option C) is a necessary step for visibility, it will not work if the underlying feature isn't enabled first37. Sharing rules (Option A) and profile permissions (Option D) manage access to existing records but do not control whether the object is technically capable of having activities associated with it.