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

A Chatter Stream is a custom feed that users (or administrators) can create to consolidate updates from multiple sources. You can combine feeds from specific groups, individual people (like the CEO), and specific records into a single view. This allows users to stay organized and monitor diverse sets of information in one place without having to navigate between different groups or records. A Chatter Group (Option A) is for a specific set of members. A Daily Digest (Option B) is an email summary. A Chatter Feed (Option C) is a general term for the individual lists of updates but does not natively allow for the targeted "multi-source" consolidation that a Stream provides.

In the Salesforce architecture, the Username is a globally unique identifier4949. This means that once a username (e.g., admin@cloudkicks.com) is used in any Salesforce organization (including production, sandboxes, and developer editions), it cannot be used again in any other organization worldwide. This often causes confusion because while an Email Address can be reused across multiple Salesforce users and orgs, the Username must remain distinct51. If an administrator receives a duplicate username error, it means the desired username is already taken by a user in another instance of Salesforce. 54Option A is incorrect because usernames must be in email format, but they don't have to be a valid functioning email. Option B is incorrect because only the username has this global uniqueness requirement, not the email address.

The Activity Timeline is a standard Lightning component that displays open tasks, upcoming events, and past activities (like logged calls or sent emails) in a chronological view. If this timeline is missing from an Account page, it is usually because the component has been removed from the Lightning Record Page layout. To fix this, the Platform Administrator should open the Account record in the Lightning App Builder. From the list of standard components on the left, the admin must drag the Activities component onto the page canvas—typically in the right-hand column or a dedicated tab. Once the page is saved and activated, the timeline will be visible to users. Visibility of the timeline is a layout configuration, not a specific "Edit access" permission (Option B). Running a report (Option C) might confirm if data exists, but it won't fix the UI issue. There is no "button" for the Activity Timeline in the Object Manager (Option D); it is managed strictly as a component within the App Builder.

Flow Builderis the recommended tool for automating updates to multiple related records based on a change to a single record. A "Record-Triggered Flow" can be configured to execute whenever an Opportunity is updated to "Closed Won". The flow can then find all other Opportunities related to the same Account where the "IsClosed" field is false, and use anUpdate Recordselement to set their stage to "Closed Lost". Outbound Messages (Option B) are used for notifying external systems, not for internal data updates31. Flow Orchestration (Option C) is designed for multi-user, complex business processes and would be overly complicated for this simple record update32. Quick Actions (Option D) require a user to click a button, which does not meet the requirement for automatic rendering upon the stage change33.

Account Teamsare designed specifically for "collaborative selling," allowing multiple users to work together on a single Account. By using Account Teams, an administrator can define specific roles (e.g., Sales Engineer, Support Rep) and grant them varying levels of access (Read/Write or Read Only) to the Account and its related Opportunities and Case. To meet the manager's requirement of "streamlining" and "automatically adding" members, the administrator should encourage users to set upDefault Account Teams. Once a user defines their default team in their personal settings, they can click a single button to add that entire team to any Account they own. Sharing Rules (Option B) are typically too broad for this requirement because they apply to all records meeting a criteria, rather than specific collaborative groups61. The Role Hierarchy (Option C) provides vertical access but doesn't easily handle the horizontal, project-based access required for support reps and engineers working on specific accounts62. Permission Sets (Option D) grant functional permissions (what a user can do) but do not grant access to specific data records in a collaborative way63.

In Salesforce reporting, administrators can use relative date and user filters to make a single report template dynamic for every person who views it. By setting the filter to Opportunity Owner (or Order Owner) equals $USER, the report will automatically filter the results to show only those records owned by the individual currently logged in and viewing the report. This is much more efficient than creating separate reports for every rep. While setting the Organization-Wide Defaults to Private (Option C) would restrict general visibility, it does not help if the reps need to be able to see each other's data for other business reasons but simply want a "clean" personal view for daily tasks36. Saving the report in a private folder (Option D) only restricts who can see the report itself, not the data contained within it. Using the $USER variable is the standard way to provide personalized, relevant data views in a shared reporting environment.

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.

Salesforce Approval Processes allow administrators to define a series of steps to automate the approval of records. Within these processes, there are four specific types of automated actions that can be triggered during initial submission, approval, rejection, or recall:

Field Update:Used to change a value on the record, such as switching a "Status" field from "Pending" to "Approved."

Email Alert:Used to send a templated email to specific users, such as notifying the submitter that their request was granted.

Task:Used to assign a follow-up task to a user.

Outbound Message: Used to send technical data to an external system via API.

While modern automation tools like Flow can post to Chatter or launch other flows, the native approval process engine is limited to these four specific actions. For a "time-off request" scenario, an Email Alert ensures the employee is notified, and a Field Update ensures the record reflects the new status, providing a clear audit trail of the business decision.

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.

Agentforceis built to be dynamic, meaning it doesn't just follow a static script but rather "reasons" through a problem using an agentic loop. The feature that directly allows an agent to adapt its behavior and take specific, real-time steps based on customer input isCustom Actions3. When a customer provides information—such as a specific order number or a request to change an address—the agent identifies the user's intent and selects the most relevant action to execute4. These actions can be powered by Flows, Apex, or Prompt Templates, giving the agent the ability to interact with Salesforce data in real-time. While Data Cloud (Option A) provides the data foundation for grounding, it is the actions themselves that define the agent's behavioral capabilities6. Screen flows (Option C) provide a guided UI for humans, but custom actions are what allow the agent to function autonomously7. Tableau (Option D) is an analytics tool and does not drive real-time agent behavior8.