Explanation:
For Agentforce to adapt its behavior in real time based on customer input, it needs the ability to execute logic that can branch, transform data, or call external systems dynamically. Custom actions (often built as Flows or Apex actions) allow Agentforce to process variable inputs, make decisions, and return tailored responses, enabling adaptive behavior.

Correct Option: B

Custom actions enable Agentforce to run logic (e.g., Flow, Apex) that evaluates real-time customer input.

Based on input values, the action can return different responses, update records, or call external APIs.

This allows the agent to adapt—for example, checking inventory and replying differently for in-stock vs. out-of-stock items.

Without custom actions, the agent can only provide static or grounded responses without dynamic behavior.

Incorrect Option: A

Data Cloud unifies customer data from multiple sources but does not directly enable adaptive agent behavior.

It provides richer data for grounding, but the agent still requires custom actions to act on that data conditionally.

Data Cloud is a data source, not a decision-execution engine for real-time adaptation.

Incorrect Option: C

Screen Flow is a declarative automation tool for guiding users through screens in a Lightning component or Experience Cloud site.

Agentforce cannot directly execute a Screen Flow as an adaptive response because screen flows require user interface interaction.

While a custom action can call a flow, the flow itself is not the feature that enables agent adaptation.

Incorrect Option: D

Tableau is an analytics and data visualization platform.

It does not enable real-time adaptive behavior within an Agentforce conversation.

Tableau can be embedded to show dashboards, but the agent cannot use it to conditionally change its responses based on live input.

Reference:
Salesforce Help Article: Add Custom Actions to Agentforce – Custom actions (built with Flow or Apex) allow Agentforce to execute dynamic logic, evaluate real-time inputs, and return variable responses. This is the primary method for enabling adaptive, conditional behavior in an agent. Data Cloud and Tableau serve different purposes.

Explanation:

In Salesforce Lightning, the Activity Timeline is part of the standard Activities component. If it’s missing from the Account record page, the administrator needs to:

• Open the Lightning App Builder for the Account record page.
• Drag and drop the Activities component onto the page layout.
• Save and activate the page.

Once added, the Activity Timeline will display past activities (calls, emails, tasks, events) and allow users to log new ones.

Why not the other options?

Update the user’s permission to allow Edit access
Permissions control whether a user can create or edit activities, but they do not determine whether the Activity Timeline appears on the page.

Run a report to verify activities
Reports can show logged activities, but they do not fix or control the missing Activity Timeline component on the record page.

Add a button for the Activity Timeline in Object Manager
There is no button option for this. The Activity Timeline is a Lightning component, not a button, so it must be added via the Lightning App Builder.

Reference
Salesforce Help: Add the Activities Component to Lightning Pages

Explanation:

When Organization-Wide Defaults (OWD) are set to Private, records are only visible to their owners and those above them in the role hierarchy. In this scenario, Sales Team A and Sales Team B are siblings in the role hierarchy (both report to the same Manager role). Because sibling roles do not automatically share records with each other, the administrator must configure Owner-based Sharing Rules.

Owner-based Sharing Rules allow records owned by users in one role (Sales Team A) to be shared with users in another role (Sales Team B). This ensures collaboration between the two teams without changing the OWD or role hierarchy.

Why not the other options?
Criteria-based sharing: Shares records based on field values, not ownership.

Hierarchical sharing: Access flows upward in the role hierarchy, not sideways between sibling roles.

Manual sharing: Requires individual users to share records one by one, which is inefficient for team-wide collaboration.

Reference:
Salesforce Help: Sharing Rules Overview

Explanation:
To provide each user with an individualized view of data on a single dashboard (e.g., each sales rep sees only their own opportunities), the administrator should create a Dynamic Dashboard. Dynamic dashboards respect the running user's record-level access. When a user views the dashboard, they see only data they have permission to see, based on the dashboard's "Run As" setting (typically "View Dashboard As: Me").

Correct Option: B

Dynamic Dashboard is a dashboard where the running user is set to "Logged-in user" (View Dashboard As: Me).

Each user sees data they personally have access to (e.g., their own opportunities, cases owned by them).

No need to create separate dashboards for each user.

Meets the requirement of "individualized views" automatically.

Incorrect Option: A

Dashboard Filter allows users to filter a dashboard by selecting values (e.g., a specific owner), but it does not automatically personalize data per user.

Users must manually select filters each time; not an individualized default view.

Incorrect Option: C

Set View Dashboard As to Me is a step in creating a dynamic dashboard, but it is not the name of the feature. The feature itself is "Dynamic Dashboard."

Option C is incomplete and describes a setting, not the solution.

Incorrect Option: D

Set View Dashboard As to Another person fixes the running user to a specific other user (e.g., an admin). All viewers see the same data as that fixed user.

This provides a consistent, non-individualized view, the opposite of what is requested.

Reference:
Salesforce Help Article: Create Dynamic Dashboards – Dynamic dashboards (View Dashboard As: Logged-in user) show each viewer data personalized to their record access. Use this instead of static dashboards to provide individualized views. Dashboard filters require manual selection, and running as another person shows a shared view.

Explanation:
When an Agentforce agent (e.g., an Einstein Bot) is deactivated, it cannot be invoked for new conversations. However, any ongoing, active chat sessions that began before deactivation continue using the existing agent configuration until the conversation naturally ends. Deactivation does not abruptly terminate live sessions.

Correct Option: B

Deactivating an agent prevents new conversations from starting with that agent.

Ongoing conversations continue uninterrupted because the session state and agent logic are already loaded.

The agent remains available to those active users until they end the chat or the session times out.

This ensures customers are not disconnected mid-issue when administrators make configuration changes.

Incorrect Option: A

The agent does not pause conversations upon deactivation.

There is no automatic resume mechanism tied to reactivation.

Pausing is not a feature of agent deactivation; ongoing chats simply proceed with the existing logic.

Incorrect Option: C

The agent window does not automatically close.

Closing would cause data loss and poor customer experience.

Users can still send and receive messages within the active session.

Incorrect Option: D

The agent does not send system error messages when messages are received during an ongoing conversation after deactivation.

The agent continues to respond using its last published configuration.

Error messages would only appear if the agent's underlying action or flow fails.

Reference:
Salesforce Help Article: Deactivate an Einstein Bot – When you deactivate a bot, new chat sessions cannot start. However, any active chat sessions that began before deactivation remain active and continue using the deactivated bot until those sessions end naturally.