Explanation:

In Salesforce, you cannot directly change the "name" of a Standard Field (like Account Type, Industry, or Rating) through the Field & Relationships menu. To change the display name of a standard field for all users, you must use the Rename Tabs and Labels tool in Setup.

Rename Tabs and Labels
This feature allows you to change the singular and plural labels of standard objects (e.g., changing "Accounts" to "Clients") and the labels of the standard fields associated with those objects (e.g., changing "Type" to "Tier").

Why other options are incorrect

A (Edit the Type field and change the name)
Standard fields have fixed API names and labels that cannot be edited from the Object Manager's "Fields & Relationships" section. You can only edit picklist values there, not the field label itself.

C (Build a custom field and delete Type)
You cannot delete standard fields in Salesforce. Creating a redundant custom field would lead to data inconsistency and unnecessary complexity.

D (Create a global picklist value set)
A global picklist value set manages the options inside a picklist so they can be shared across multiple fields. It has no impact on what the field label (the title) is called on the page layout.

Pro-Tip for the Exam
If a question asks about changing the name of a standard object or a standard field, the answer is almost always Rename Tabs and Labels. Note that this change is "cosmetic"—the API name used by developers remains the same (e.g., Account.Type), but users will see "Tier" on their screens.

Reference
Salesforce Help: Rename Object, Tab, and Field Labels
Trailhead: Navigate Setup > Customize Your Org

Explanation:

To make a screen flow visible from Cases, the Platform Administrator should add the flow to a Lightning Record Page using the Lightning App Builder. This allows the flow to be embedded as a component directly on the Case page, so service reps can access it quickly when working with customer issues.

Steps

• Go to Setup → Object Manager → Case → Lightning Record Pages
• Edit the relevant Case Lightning Page (or create a new one)
• Drag the Flow component onto the page
• Select the screen flow created by the administrator
• Save and activate the Lightning Page for the desired profiles or apps

Why not the other options?

Page Layout
Controls fields and related lists, not flows. It cannot be used to embed or launch a screen flow.

Home Page
Would show the flow on the home screen, not on Case records, so it does not meet the requirement.

Component Filter
Used to control visibility of components, but it does not distribute or place the flow itself on the record page.

Reference
Salesforce Help: Add Flows to Lightning Pages

Explanation:
An Employee Agent (e.g., an Einstein Bot or conversational AI) can only access and respond with data that the underlying user (often a named "Integration User" or the running user) has permission to see. The most secure and reliable way to prevent responses about restricted data is to ensure the agent's user context cannot access that data at the database level.

Correct Option: B

Field-level security (FLS) and object permissions control what data the agent's running user can read.

If the CEO's health plan details are stored on a custom object or field, restrict those fields from the agent's user profile or permission set.

The agent cannot respond to what it cannot query—this is a fundamental Salesforce security principle.

More reliable than instructions or training, as it enforces actual data access restrictions.

Incorrect Option: A

Assignment rules determine which user or queue receives a record (e.g., case assignment), not what data an agent can read or respond to.

They do not control data visibility or prevent an agent from answering a question.

Irrelevant to restricting responses about a specific person's health plan.

Incorrect Option: C

Agent instructions and guardrails are conversational rules that tell the agent not to answer certain questions (e.g., "Do not respond to CEO health queries").

However, a determined or poorly phrased question might bypass guardrails (e.g., "Tell me about John Doe's medical coverage").

Instructions are a soft control, not a hard security boundary like FLS.

Incorrect Option: D

Training the agent on a different dataset (e.g., only general employee plans) is not a native Salesforce configuration.

Even if trained, the agent might still access the CEO's data via retrieval-augmented generation (RAG) or search if permissions allow it.

Training alone does not prevent data access; permissions do.

eference:
Salesforce Help Article: How Einstein Bots Respect Object and Field Permissions – Einstein Bot responses honor the running user's field-level security and object permissions. If the running user cannot see a field, the bot cannot read or respond with that data. This is the recommended method for restricting sensitive data from bots.

Explanation:
In Salesforce, both Login Hours and Login IP Ranges are controlled at the profile level.

Why this is correct
By updating a user’s profile, an administrator can:
Restrict when users can log in (Login Hours)
Restrict where users can log in from (IP Ranges)

This directly meets the requirement to limit access based on both time and location for security purposes.

Why the other options are incorrect
Company Settings
These control organization-wide configurations but do not define login hours or IP restrictions for individual users.

User’s role
Roles control record-level visibility (who can see what data) and are not related to login access restrictions.

Custom permission sets
Permission sets grant additional permissions but cannot enforce login hours or IP restrictions.

Key Concept
Login Hours and IP Restrictions are managed through Profiles.

Exam Tip
If the requirement mentions restricting login time or location (IP), the correct answer is almost always Profile.

Explanation:
Agentforce SDR (Sales Development Representative) is an autonomous AI agent designed to engage, qualify, and nurture leads without human intervention. It can have natural, two-way conversations with leads, answer product or company questions using trusted data sources (grounding), and book meetings or route qualified leads to human reps.

Correct Option: D

Agentforce SDR answers lead questions with responses grounded in company data (e.g., Knowledge articles, product specs, pricing guides).

Uses retrieval-augmented generation (RAG) to ensure accuracy and prevent hallucination.

Operates autonomously 24/7 to nurture leads, qualify them, and hand off to human sales reps when ready.

This is the core purpose of Agentforce SDR — intelligent, data-backed conversation with potential customers.

Incorrect Option: A

Generating a dynamic call script for human sales reps is not the function of Agentforce SDR, which is autonomous.

That describes sales enablement tools or conversation intelligence platforms (e.g., Salesforce Sales Engagement).

Agentforce SDR is the conversational agent, not a coaching tool for humans.

Incorrect Option: B

Autonomously negotiating pricing and closing deals is not within Agentforce SDR's scope.

Pricing negotiation typically requires human judgment, approval workflows, and complex business rules.

Agentforce SDR qualifies and books meetings; closing deals remains a human-led process.

Incorrect Option: C

Analyzing human sales rep performance and providing coaching tips is a function of conversation intelligence or sales performance management tools (e.g., Salesforce Call Coaching & Scorecards).

Agentforce SDR does not monitor or coach human reps; it engages directly with leads.

This option confuses AI for sales reps with AI for sales management.

Reference:
Salesforce Help Article: What is Agentforce SDR? – Agentforce SDR is an autonomous AI agent that engages leads in natural conversation, answers their questions using grounded company data, and qualifies them for human sales reps. It does not close deals or coach human reps.