Explanation:

The issue is caused by Salesforce security, not by the Flow logic.

The Opportunity object has an Organization-Wide Default (OWD) of Private, so the Einstein Service Agent User cannot see Opportunity records unless it has both:
* The necessary object permissions (such as Read access).
* Appropriate record-level access, provided through sharing rules, role hierarchy, or another sharing mechanism.

Granting only the minimum permissions and sharing required follows the principle of least privilege, which states that users should receive only the access necessary to perform their tasks.

Why the Other Options Are Incorrect
B. ❌ Set the agent action flow to run in System Mode without sharing.
Running a Flow in System Mode bypasses normal user-level security for execution.
While this may allow access to the records, it grants broader privileges than necessary and does not adhere to the principle of least privilege.
For exam questions emphasizing security best practices, avoid bypassing sharing unless there is a specific business requirement.

C. ❌ Change the Opportunity object's organization-wide default to Public Read Only so the Einstein Service Agent User can access records.
Changing the OWD affects all users in the organization.
This unnecessarily broadens access and violates the principle of least privilege.
OWD should not be relaxed simply to solve access for a single agent.

Reference
Salesforce documentation on Organization-Wide Defaults (OWD) and record-level security.
Salesforce documentation on Flow execution context (User Mode vs. System Mode).
Salesforce Agentforce documentation on configuring permissions for the Einstein Service Agent User.
Salesforce Certified Agentforce Specialist (AI-201) Exam Guide – security and access control for Agentforce.

Exam Tip
Questions that mention "principle of least privilege" almost always favor granting targeted permissions rather than bypassing or relaxing security.

Think of the options in this order:
✅ Permission Sets + Sharing Rules → Grant only the required access (best practice).
⚠️ System Mode → Bypasses security; use only when explicitly required.
❌ Relax OWD or broad org-wide access → Usually the least secure option and rarely the correct exam answer.

Explanation:

Prompt Builder is the Salesforce AI capability designed to generate contextual insights directly on record pages. It allows admins and specialists to define prompts that leverage CRM data (such as guest profiles, interests, and activity preferences) to produce summaries, recommendations, or other AI-driven outputs. These outputs are scoped to appear only where configured — in this case, the contact record page.

Option A (Flow Builder) is incorrect:
Flow Builder automates business processes but does not generate AI-driven summaries or recommendations.

Option B (Agentforce Builder) is incorrect:
Agentforce Builder is used to design conversational AI agents, not record-specific summaries.

Option C (Prompt Builder) is correct:
Prompt Builder enables contextual AI outputs tied to Salesforce records, exactly matching the requirement.

Reference:
Salesforce Documentation: Prompt Builder Overview

Trailhead Module: AI Prompt Builder Basics

Salesforce Help: Using Prompt Builder for Record Pages

Explanation:

Why C is correct:
Einstein Work Summaries is the Salesforce generative AI feature specifically designed to help service and support teams quickly understand the context of a work item—such as a Case, Lead, or Opportunity—without having to read through every single comment, email, or activity in the feed.

Work Summaries automatically generate a concise, AI-powered summary of the entire case history, including:
* The customer's original issue.
* Key updates from customer interactions.
* Recent comments from support reps.
* Any pending actions or unresolved questions.

This is the exact solution that new support reps need. They can instantly grasp the case details, status, and next steps without spending time scrolling through a long feed of case comments. This accelerates onboarding for new hires and improves overall case resolution efficiency.

Why A is incorrect:
Agent (Agentforce Agent) is the conversational AI assistant that can autonomously handle customer interactions, answer questions, and perform actions. While an Agentforce Service Agent could assist the rep by summarizing a case, the question asks for the specific generative AI solution designed for this purpose within the Salesforce UI. Einstein Work Summaries is the out-of-the-box feature that provides case summaries directly within the Service Console, whereas an Agent is a separate deployment for customer-facing or internal assistant use cases.

Why B is incorrect:
Einstein Sales Summaries is designed for sales teams, specifically to summarize sales records like Opportunities, Accounts, and Leads. It provides insights on deal progress, next steps, and key contacts. It is not designed for service/support cases or for summarizing case comments, making it irrelevant for this scenario.

References:
Salesforce Official Documentation: "Einstein Work Summaries Overview" – defines Einstein Work Summaries as the generative AI feature that creates concise summaries of work records (Cases, Leads, Opportunities) to help users quickly understand context without reading the full history.

Trailhead Module: "Get Started with Einstein for Service" > Unit: "Summarize Work with Einstein" – explicitly demonstrates how service reps use Einstein Work Summaries to get case summaries, improving efficiency and reducing time spent on case reading.

Agentforce Exam Guide (AI-201): Under "Einstein AI Capabilities" – distinguishes between Work Summaries (service/support), Sales Summaries (sales), and Agents (conversational assistants), emphasizing the correct use case for each.

Explanation:

Summary
This question assesses knowledge of Salesforce Prompt Builder's design best practices, specifically focusing on how to structure a prompt to meet clear, complex business requirements for summarizing case notes. The requirements include defining a persona (Role), a specific output (Task), necessary input data (Context), strict output rules (Constraints), and the required layout (Format). The best practice is to be explicit and detailed in all these components to ensure the Large Language Model (LLM) delivers the desired, high-quality, and consistent output, especially regarding length limits and required conditional statements.

Correct Option

🟢 A. Role: You are an experienced support agent. Task: Summarize the case notes. Context: Include customer issue, troubleshooting steps, and next actions. Constraints: Limit to 5 sentences, use plain language, and if no next action is found, state “No next action required.” Format: Use numbered sentences for clarity.

This option adheres to Salesforce's prompt design best practices by being explicit and detailed in every section, directly addressing all stated business requirements:
✔️ Role: Defines the needed persona (experienced support agent), guiding the tone.
✔️ Task: Clearly states the goal (Summarize the case notes).
✔️ Context: Identifies the required input data points (customer issue, troubleshooting steps, and next actions).
✔️ Constraints: Directly enforces the crucial rules: Limit to 5 sentences and use plain language (no technical jargon). Crucially, it includes the required conditional statement ("if no next action is found, state 'No next action required'").
✔️ Format: Specifies the required output layout (numbered sentences).

Incorrect Options

❌ B. Role: You are a support agent writing a case summary. Task: Provide a professional summary of the issue and troubleshooting steps. Contest: Include customer issue, steps taken, and next actions if available. Constraints: No strict sentence limit, but use plain language. If no next action is found, leave it out. Format: Use paragraphs for readability.

This option is incorrect because it fails to enforce the critical business requirements:
🔹 It states "No strict sentence limit," directly violating the requirement for the summary to be "no longer than five sentences."
🔹 It states "If no next action is found, leave it out," which directly contradicts the requirement to "explicitly state 'No next action required'” in that scenario.
🔹 The format is paragraphs, not the specified numbered sentences.

❌ C. Role: You are a case documentation assistant. Task: Write a summary of the support call. Context: Always describe the customer issue, troubleshooting, and resolution details. Constraints: The summary should be comprehensive and professional, but there is no limit on length or language style. Format: Use complete sentences in a narrative style.

This option is incorrect because it is too vague and permissive, directly violating several key requirements:
🔹 It states "no limit on length," which violates the five-sentence limit.
🔹 It states "no limit on... language style," which violates the requirement to use plain language (no technical jargon).
🔹 The constraints ("comprehensive and professional") are too general and do not include the specific conditional statement for when no next action is found.

Reference:
Salesforce Prompt Builder: Prompt Design Best Practices

Explanation:

When setting up a file-based Agentforce Data Library and leveraging Intelligent Context (which uses AI to automatically evaluate document structure and content to determine the optimal chunking/indexing strategy), Salesforce requires an initial small sample batch of documents for this evaluation process. Specifically, the system is designed to analyze up to five PDF files, each 10 MB or less, during the initial setup. This sample allows Intelligent Context to assess the document format, structure, and content patterns, and then recommend or apply the best indexing configuration before the specialist proceeds to upload the full document set.

This size and count limitation (5 files, ≤10 MB each) is a specific, documented constraint for the evaluation/preview phase of Intelligent Context — it is not something the specialist configures arbitrarily, but a defined system behavior for the initial optimization step.

Why the other options are incorrect:

A. Up to five PDFs that are 100 MB or less: The file size threshold for the Intelligent Context evaluation sample is 10 MB, not 100 MB. 100 MB exceeds the supported limit for this initial indexing evaluation step.

C. Manually enable Intelligent Context in Data 360 prior to uploading the PDF files: Intelligent Context is not something manually toggled on in Data Cloud/Data 360 as a prerequisite setup step — it's a built-in, automatic capability of the Agentforce Data Library's document processing pipeline that activates based on the sample upload, not a separate manual configuration step.

Reference:
Salesforce Agentforce documentation — "Create a Data Library" / "Intelligent Context for File-Based Data Libraries" (sample document requirements: up to 5 PDFs, 10 MB or less, for indexing optimization).