ADM-201 Exam Dumps - Salesforce Administrator Questions and Answers

4

A Master-Detail Relationship has several defining traits:5

Roll-up Summaries:This relationship is the only one that allows the Master record to summarize data (sum, count, min, max) from its Detail records (Option C).

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

Ownership and Security: The Detail record inherits its owner from the Master record, and as such, there is no "Owner" field on the Detail record (Option E). Additionally, the detail record's security and sharing settings are inherited from the master, meaning permissions are not independent (negating Option B).

Option A is incorrect because an object can only have a maximum of two master-detail relationships.

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.

When an AI agent like Agentforce transfers a conversation to a human support representative, the goal is a "warm handoff" where the rep can see exactly what the customer and the AI discussed. If reps are complaining about a lack of context, the most common administrative cause is that the Conversation History component (or Agent History component) has not been added to the Case Lightning Record Page. Without this component on their page layout, the rep sees the newly assigned case but cannot see the transcript of the preceding chat session. To resolve this, the Platform Administrator should use the Lightning App Builder to add the relevant history component to the Case page used by the support team. Option D is less likely if escalation is working but context is missing. Option A would prevent users from using Agentforce features but wouldn't specifically hide the transcript of a finished AI interaction. Ensuring the UI includes the conversation history is critical for maintaining high customer satisfaction during handoffs.

Tasks and Events are both part of the Activity object, but they often require different picklist values for the standard Subject field. To achieve this, the Platform Administrator must manage the picklist values for the Subject field specifically for each record type or activity type. In the Object Manager, under the Activity object (or Task/Event objects individually in some setups), the admin should edit the Subject field. Because Task and Event are distinct entities with their own picklist value sets for the Subject field, the admin can add "Schedule Site Visit" and "Send Contract" to the Task Subject list and "Site Visit" and "Ride Along" to the Event Subject list. This ensures that when a user creates a Task, they only see task-related subjects, and when they create an Event, they see event-related subjects. Option D is incorrect because it would mix all values together, causing confusion for the users. Option A (Predefined Field Values) is used to set a single default value for a field when an action is clicked, but it does not manage the available list of options in a picklist.

When defining Topics for an Agentforce agent, the quality of instructions is vital for ensuring the agent identifies the correct topic when a user asks a question. Best practice includes providing a variety of example user questions (utterances). This helps the agent's natural language processing (NLP) model recognize the different patterns and ways a human might phrase a request related to that specific topic. Writing instructions too generically (Option A) can lead to "topic overlap," where the agent gets confused about which topic to use75. Minimal instructions (Option C) may reduce latency slightly but often result in poor accuracy and failed topic identification76. Using "plain language" is generally preferred over overly "business-specific" jargon (Option D) because the agent needs to match the way customers or employees naturally speak during a conversation

I apologize for that mistake. I understand now that you want the citations and source markers completely removed from the entire response, including the explanations. I will ensure they are not included moving forward.

In Salesforce, when a Platform Administrator changes a field's data type from Auto Number to Text, the operation is considered "safe" regarding data retention. The existing values that were automatically generated by the system (e.g., "INV-1001") will remain unchanged and stay within the field as static text strings12. However, once the change is saved, the system will no longer increment or automatically generate new numbers for future records; users will have to enter data manually. It is important to note that the reverse operation—changing a Text field to an Auto Number—is different, as it would require the administrator to decide whether to overwrite existing data or only number new records14. Options B, C, and D are incorrect because Salesforce explicitly supports this specific conversion without deleting or fundamentally transforming the existing data into a different format other than plain text.

When an administrator needs to extract a specific subset of records (e.g., Opportunities filtered by stage and date) with specific fields, the Data Loader is the most appropriate tool. Data Loader is a client application that allows for bulk operations, including "Export" and "Export All"43. It allows the administrator to write a SOQL (Salesforce Object Query Language) query or use the built-in query builder to apply filters, such as StageName = 'Closed Won' and CloseDate = LAST_90_DAYS44. The Data Import Wizard (Option B) is primarily used for importing data and has very limited export capabilities, usually confined to simple CSV samples45454545. The Data Export Service (Option D), also known as "Weekly Export," is designed for full backup purposes; it exports the entire database into zip files and does not allow for specific filtering of records or fields for a quick ad-hoc report. Data Cloud (Option C) is a large-scale data platform and is overkill for a simple file export task47. Thus, for targeted, field-specific exports of 90 days of data, Data Loader is the standard choice.

To avoid the administrative burden of creating and maintaining multiple identical dashboards for different teams, a Platform Administrator should use Dashboard Filters. By adding a filter based on the "Team Assigned" custom field, the administrator can create a single dashboard that the manager can toggle between "Team A," "Team B," and "Team C". Each time a filter value is selected, all components on the dashboard that use that field (or a mapped equivalent) will automatically refresh to show the data relevant only to that team. Creating separate dashboards (Option A) is inefficient and leads to "dashboard sprawl". Adding specific widgets for every team on one dashboard (Option B) would result in a cluttered and confusing interface61. Cross Filters (Option D) are a reporting feature used to filter records based on their relationship to other objects, not a dashboard-level viewing tool.

When a specific user encounters an error that an administrator cannot replicate, the most effective troubleshooting technique is to "Login as" that user. This feature, which must be enabled in the organization's login policies, allows the administrator to see exactly what the user sees and experience the system through their specific profile, role, and sharing permissions22. This is vital for identifying issues related to Validation Rules, Field-Level Security, or Record-Triggered Flows that might only trigger under specific user contexts. Logging in as a system administrator (Option A) is ineffective because administrators often bypass certain restrictions that apply to standard users4. Asking for a password (Option D) is a major security violation and is never required in Salesforce5. By using the "Login as" feature, the admin can pinpoint whether the error is caused by the user's data input or a specific permission conflict assigned to their profile.

A Delegated Approver is a user designated by an individual or an administrator to act on their behalf when an approval request is received. This is particularly useful for planned absences, such as vacations. While the delegated approver has the power to approve or reject a record, they cannot reassign the request to someone else. This is a temporary manual assignment and is different from a Manager (Option D), who is part of the permanent role hierarchy, or a Queue (Option B), which allows a group of people to share approval tasks. There is no feature called an "Approval Rule" (Option A) that handles temporary user reassignment in this manner.