• ホーム
  • ブログ
  • 最新Agentforce-Specialist日本語合格保証試験問題集には正確で最新な問題があります [Q158-Q176]

最新Agentforce-Specialist日本語合格保証試験問題集には正確で最新な問題があります [Q158-Q176]

Share

最新Agentforce-Specialist日本語合格保証試験問題集には正確で最新な問題があります

Agentforce-Specialist日本語試験ブレーン問題集で学習注釈と理論

質問 # 158
Universal Containers は、ユーザー向けに 3 つの異なるタイプの売上概要を取得するために、3 つのカスタム アクションを実装しています。ユーザーからは、自分の発言に基づいた正しい概要が得られないとの苦情が寄せられています。Agentforce スペシャリストは、根本原因として何を調査すべきでしょうか。

  • A. 入力タイプと出力タイプが正しく選択されていることを確認します。
  • B. カスタムアクションがエージェントに割り当てられていることを確認します。
  • C. アクションの指示が一意であることを確認します。

正解：C

解説：
The root cause of users receiving incorrect sales summaries lies in non-unique action instructions (Option B).
In Einstein Bots, custom actions are triggered based on how well user utterances align with the action instructions defined for each action. If the instructions for the three custom actions overlap or lack specificity, the bot's natural language processing (NLP) cannot reliably distinguish between them, leading to mismatched responses.
Steps to Investigate:
Review Action Instructions: Ensure each custom action has distinct, context-specific instructions. For example:
Action 1: "Summarize quarterly sales by region."
Action 2: "Generate a product-wise sales breakdown for the current fiscal year." Action 3: "Provide a comparison of sales performance between online and in-store channels."Ambiguous or overlapping instructions (e.g., "Get sales summary") cause confusion.
Test Utterance Matching: Use Einstein Bot's training tools to validate if user utterances map to the correct action. Overlap indicates instruction ambiguity.
Refine Instructions: Incorporate keywords or phrases unique to each sales summary type to improve intent detection.
Why Other Options Are Incorrect:
A). Assigning actions to an agent is irrelevant, as custom actions are automated bot components.
C). Input/output types relate to data formatting, not intent routing. While important for execution, they don't resolve utterance mismatches.
Einstein Bot Developer Guide: Stresses the need for unique action instructions to avoid intent conflicts.
Trailhead Module: "Build AI-Powered Bots with Einstein" highlights instruction specificity for accurate action triggering.
Salesforce Help Documentation: Recommends testing and refining action instructions to ensure clarity in utterance mapping.


質問 # 159
Salesforce Agentforce スペシャリストは、Einstein Trust Layer 内のデータマスキングで何を設定できますか?

  • A. マスキング用の暗号化キー
  • B. マスクが免除されるプロファイル
  • C. マスクするプライバシーデータエンティティ

正解：C

解説：
In the Einstein Trust Layer, the Salesforce Agentforce Specialist can configure privacy data entities to be masked (Option C). This ensures sensitive or personally identifiable information (PII) is obfuscated when processed by AI models.
* Data Masking Configuration:
* The Agentforce Specialist defines which fields or data types (e.g., email, phone number, Social Security Number) should be masked. For example, masking the Email field in a prompt response to protect user privacy.
* This is done through declarative settings in Salesforce, where entities (standard or custom fields) are flagged for masking.
* Why Other Options Are Incorrect:
* A. Profiles exempt from masking: Exemptions are typically managed via permissions (e.g., field-level security), not directly within Einstein Trust Layer's Data Masking settings.
* B. Encryption keys for masking: Encryption is separate from masking. Masking involves obfuscation (e.g., replacing "[email protected]" with "@"), not encryption, which uses keys to secure data.
References:
* Einstein Trust Layer Documentation: States that Data Masking allows admins to "define which fields should be masked to protect sensitive data."
* Trailhead Module: "Einstein Trust Layer Basics" explains configuring privacy entities for masking.
* Salesforce Help Article: "Secure AI with Einstein Trust Layer" details masking configurations for privacy compliance.


質問 # 160
Universal Containers (UC) は、営業チームが通話中に言及された製品名や競合他社名についての洞察を得られるようしたいと考えています。UC はこの要件をどのように満たすべきでしょうか?

  • A. Einstein 会話インサイトを有効にし、録音プロバイダーを接続し、権限セットを割り当て、最大 25 個の製品でインサイトをカスタマイズします。
  • B. Einstein 会話インサイトを有効にし、販売記録を有効にし、権限セットを割り当て、最大 50 個の製品でインサイトをカスタマイズします。
  • C. Einstein 会話インサイトを有効にし、権限セットを割り当て、記録マネージャーを定義し、最大 50 の競合他社名でインサイトをカスタマイズします。

正解：A

解説：
UC wants insights into product and competitor mentions during sales calls, leveraging Einstein Conversation Insights. Let's evaluate the options.
Option A: Enable Einstein Conversation Insights, connect a recording provider, assign permission sets, and customize insights with up to 25 products.Einstein Conversation Insights analyzes call recordings to identify keywords like product and competitor names. Setup requires enabling the feature, connecting an external recording provider (e.g., Zoom, Gong), assigning permission sets (e.g., Einstein Conversation Insights User), and customizing insights by defining up to 25 products or competitors to track. Salesforce documentation confirms the 25-item limit for custom keywords, making this the correct, precise answer aligning with UC's needs.
Option B: Enable Einstein Conversation Insights, assign permission sets, define recording managers, and customize insights with up to 50 competitor names.There's no "recording managers" role in Einstein Conversation Insights setup-integration is with a provider, not a manager designation. The limit is 25 keywords (not 50), and the option omits the critical step of connecting a provider, making it incorrect.
Option C: Enable Einstein Conversation Insights, enable sales recording, assign permission sets, and customize insights with up to 50 products."Enable sales recording" is vague-Conversation Insights relies on external providers, not a native Salesforce recording feature. The keyword limit is 25, not 50, making this incorrect despite being closer than B.
Why Option A is Correct:
Option A accurately reflects the setup process and limits for Einstein Conversation Insights, meeting UC's requirement per Salesforce documentation.
References:
Salesforce Help: Set Up Einstein Conversation Insights - Details provider connection and 25-keyword limit.
Trailhead: Einstein Conversation Insights Basics - Covers permissions and customization.
Salesforce Agentforce Documentation: Sales Features - Confirms integration steps.


質問 # 161
企業が Agentforce の Data Cloud でハイブリッド検索インデックスを好む理由を説明している記述はどれですか。

  • A. ハイブリッド検索インデックスは、リテラルキーワード一致とセマンティックリコールの両方をサポートしており、クエリに特定の用語と意図が混在している場合に役立ちます。
  • B. ハイブリッド検索でのベクトル埋め込みはキーワードの一致によって事前にフィルタリングされるため、計算オーバーヘッドが削減され、応答の精度が向上します。
  • C. ハイブリッド検索インデックスでは、セマンティック埋め込みが不要になるため、ベクター検索よりもクエリを高速に処理します。

正解：A

解説：
According to the AgentForce Data Cloud Search Indexing Guide and RAG Optimization Framework, a hybrid search index combines both keyword-based (lexical) and vector-based (semantic) search capabilities. This dual-mode retrieval enables AgentForce to interpret user intent while still honoring exact keyword matches.
In many enterprise scenarios, queries contain a mixture of specific terms (e.g., "contract ID 54321") and semantic intent (e.g., "renew my subscription"). A purely vector search might overlook exact keywords, while a keyword-only search might miss semantically relevant results. Hybrid indexing ensures that both types of retrieval are available simultaneously - providing the best balance of precision and contextual understanding.
Option A is incorrect because hybrid search still uses embeddings; it doesn't eliminate them. Option B partially describes the hybrid search process but oversimplifies its purpose - the primary goal isn't just prefiltering for performance, but combining semantic recall and exact matching for more relevant, balanced results.
Thus, per AgentForce documentation, hybrid search indexes are preferred when organizations need both literal keyword matching and semantic understanding for complex, natural-language queries.
Reference: AgentForce Data Cloud Documentation - "Hybrid Search Index: Combining Keyword and Semantic Retrieval."


質問 # 162
Agentforce でカスタム エージェント アクションを作成するときのアクション指示の主な目的の 1 つは何ですか?

  • A. アクション命令は、推論エンジンが使用するアクションを決定するのに役立ちます。
  • B. アクション指示は、会話内でこのアクションを呼び出す方法をユーザーに伝えます。
  • C. アクション命令は、推論エンジンを動かす大規模言語モデル (LLM) の温度を定義します。

正解：A

解説：
According to the AgentForce Action Design and Configuration Guide, action instructions serve as the directive text that informs the Reasoning Engine about when and how to invoke a specific action. The documentation states: "Action instructions guide the reasoning engine by describing the action's purpose, inputs, and when it should be selected. Clear, concise instructions improve the LLM's accuracy in mapping user intent to the correct action." Option A is correct because it reflects this documented purpose - connecting user intent with the appropriate system action.
Option B is incorrect since the temperature parameter for the LLM is defined at the system or configuration level, not within action instructions.
Option C is incorrect because action instructions are meant for the reasoning engine, not for end users.
References (AgentForce Documents / Study Guide):
AgentForce Action Design Guide: "How Action Instructions Support Reasoning" AgentForce Builder Handbook: "Optimizing Action Selection through Clear Instructions" AgentForce Study Guide: "Purpose of Action Instructions in Custom Actions"


質問 # 163
Northern Trail Outfitters の Agentforce スペシャリストは、セットアップ内の [データ マスキングの構成] メニューで組織のデータ マスキング設定を確認しました。すべてのフィールドを評価した結果、いくつかの追加フィールドが機密であると判断され、Einstein の Trust Layer 内でマスキングされました。
マスクされたフィールドを変更する場合、Agentforce スペシャリストはどのような手順を実行する必要がありますか?

  • A. Einstein Trust Layer をオフにして、再度オンにします。
  • B. データとマスクされたデータを利用するプロンプトから生成された応答が、生成された応答の品質に悪影響を及ぼさないことをテストして確認します。
  • C. Einstein フィードバックをオンにして、エンドユーザーが AI 機能に悪影響があるかどうかを報告できるようにします。

正解：B

解説：
After modifying masked fields in Einstein's Trust Layer, the next important step is to test and confirm that the responses generated by prompts utilizing the newly masked data still meet quality standards. This ensures that masking sensitive information does not negatively impact the usefulness or accuracy of the AI-generated content. Thorough testing helps identify any issues in prompt performance that could arise due to masking, and adjustments can be made if needed.
Option B is correct because testing the effects of masking on AI responses is a critical step in ensuring AI continues to function as expected.
Option A (turning off and on the Einstein Trust Layer) is unnecessary after changing the masked fields.
Option C (turning on Einstein Feedback) allows for user feedback but is not a direct step following field masking modifications.
Salesforce Einstein Trust Layer Overview: https://help.salesforce.com/s/articleView?id=sf.
einstein_trust_layer.htm


質問 # 164
Agentforce の推論エンジンの主な機能は何ですか?

  • A. 会話履歴に基づいてレコードクエリを生成する
  • B. ユーザーの発話に応答するためのエージェントのトピックとアクションを識別する
  • C. 会話中にリアルタイムの自然言語応答を提供する

正解：B

解説：
Why is "Identifying agent topics and actions to respond to user utterances" the correct answer?
In Agentforce, the reasoning engine plays a critical role in interpreting user queries and determining the appropriate agent response.
Key Functions of the Reasoning Engine in Agentforce:
* Analyzing User Intent
* The reasoning engine interprets the meaning behind natural language user inputs.
* It maps user utterances to predefined topics to determine the correct AI-generated response.
* Selecting the Appropriate Agent Action
* The engine evaluates available actions and selects the best response based on the detected topic
.
* For example, if a user asks, "What is my current account balance?", the reasoning engine:
* Identifies the topic: "Account Information"
* Chooses the correct action: "Retrieve account balance"
* Executes the action and returns the response
* Ensuring AI Accuracy and Context Awareness
* The reasoning engine grounds AI-generated responses in relevant Salesforce data, ensuring accurate outputs.
Why Not the Other Options?
# B. Offering real-time natural language response during conversations.
* Incorrect because real-time natural language processing (NLP) is handled by the large language model (LLM), not the reasoning engine.
* The reasoning engine focuses on action selection, not linguistic processing.
# C. Generating record queries based on conversation history.
* Incorrect because query generation is handled by Copilot Actions (e.g., Query Records), not the reasoning engine.
* The reasoning engine decides which query should be run, but does not generate queries itself.
Agentforce Specialist References
* Salesforce AI Specialist Material explains that the reasoning engine identifies topics and selects agent actions.
* Salesforce Instructions for the Certification confirm that the reasoning engine determines AI workflow execution.


質問 # 165
ユニバーサルコンテナーズは、顧客が注文状況を確認できるようにサービスエージェントを設定しました。設定項目は次のとおりです。
名前: 注文問い合わせ
分類の説明: 過去 90 日以内に行われた注文の追跡詳細や配達予定日など、注文ステータスを確認するユーザー要求を処理します。
業務範囲：認証済みのユーザーが過去90日以内に行った注文のステータスを確認するためのサポートのみを担当します。注文が配送保留中の場合は、追跡番号と配送予定日をお知らせください。90日以上経過した注文に関するお問い合わせには対応しないでください。
このトピックを選択するために Agentforce 推論エンジンによって使用される情報はどれですか?

  • A. トピック名と分類の説明
  • B. トピック名とスコープ
  • C. 分類の説明と範囲

正解：C

解説：
The AgentForce Reasoning Engine Guide explains that the engine relies primarily on the Classification Description and Scope fields to determine which topic best matches the user's intent. The documentation notes: "Classification Description defines the purpose and context of a topic, while Scope provides the operational boundaries for when and how that topic should be triggered. Together, they guide the LLM in selecting the appropriate topic at runtime." Option A includes "Topic Name," which is used mainly for administrative organization, not reasoning.
Option B omits the Classification Description, which contains the intent signal critical for matching.
Therefore, Option C is correct since both the Classification Description and Scope are essential for topic selection by the reasoning engine.
References (AgentForce Documents / Study Guide):
* AgentForce Reasoning Engine Overview: "How Topics Are Selected"
* AgentForce Builder Guide: "Role of Classification Description and Scope in Topic Selection"
* AgentForce Study Guide: "Optimizing Topic Matching Logic"


質問 # 166
Universal Containers (UC) は、最新かつアクティブで関連性のあるポリシーとコンプライアンス情報を顧客に提供する Agentforce サービス エージェントを構築したいと考えています。エージェントは次の要件を満たす必要があります。
* 人事ポリシー、コンプライアンス ガイドライン、会社の手順を意味的に検索します。
* 回答が公開された知識に基づいていることを確認します。
* 手動で再構成することなく、ナレッジの更新をすぐに反映できるようにします。エージェントが正しい情報を取得できるようにするには、UC は何をする必要がありますか?

  • A. AI による取得用にポリシー ドキュメントを保存およびインデックス付けするための Agentforce データ ライブラリを設定します。
  • B. 幻覚を防ぐために、ポリシー応答を AI モデルに手動で追加します。
  • C. エージェントがすべての内部記録と過去の顧客からの問い合わせを検索できるようにします。

正解：A

解説：
UC requires an Agentforce Service Agent to deliver accurate, up-to-date policy and compliance info with specific criteria. Let's evaluate.
* Option A: Enable the agent to search all internal records and past customer inquiries.Searching all records and inquiries risks irrelevant or outdated responses, conflicting with the need for published Knowledge grounding and immediate updates. This lacks specificity, making it incorrect.
* Option B: Set up an Agentforce Data Library to store and index policy documents for AI retrieval.The Agentforce Data Library integrates with Salesforce Knowledge, indexing HR policies, compliance guidelines, and procedures for semantic search. It ensures grounding in published Knowledge articles, and updates (e.g., new article versions) are reflected instantly without reconfiguration, as the library syncs with Knowledge automatically. This meets all UC requirements, making it the correct answer.
* Option C: Manually add policy responses into the AI model to prevent hallucinations.Manually embedding responses into the model isn't feasible-Agentforce uses pretrained LLMs, not custom training. It also doesn't support real-time updates, making this incorrect.
Why Option B is Correct:
The Data Library meets all criteria-semantic search, Knowledge grounding, and instant updates-per Salesforce's recommended approach.
References:
Salesforce Agentforce Documentation: Data Library > Knowledge Integration - Details indexing and updates.
Trailhead: Build Agents with Agentforce - Covers Data Library for accurate responses.
Salesforce Help: Grounding with Knowledge - Confirms real-time sync.


質問 # 167
Universal Containers には、ビジネス要件を完全に満たしていないアクティブな標準の電子メール プロンプト テンプレートがあります。問題の標準のプロンプト メール テンプレートのコンテンツを使用し、ビジネス要件を完全に満たすようにカスタマイズするには、Agentforce スペシャリストはどのような手順を踏む必要がありますか?

  • A. 新しいバージョンとして保存し、必要に応じて編集します。
  • B. 新しいテンプレートとして保存し、必要に応じて編集します。
  • C. 既存のテンプレートを複製し、必要に応じて変更します。

正解：C

解説：
Comprehensive and Detailed In-Depth Explanation:
Universal Containers (UC) has astandard email prompt template(likely a prebuilt template provided by Salesforce) that isn't meeting their needs, and they want to customize it while retaining its original content as a starting point. Let's assess the options based on Agentforce prompt template management practices.
* Option A: Save as New Template and edit as needed.In Agentforce Studio's Prompt Builder, there's no explicit "Save as New Template" option for standard templates. This phrasing suggests creating a new template from scratch, but the question specifiesusing the content of the existing standard template.
Without a direct "save as" feature for standards, this option is imprecise and less applicable than cloning.
* Option B: Clone the existing template and modify as needed.Salesforce documentation confirms that standard prompt templates (e.g., for email drafting or summarization) can beclonedin Prompt Builder. Cloning creates a custom copy of the standard template, preserving its original content and structure while allowing modifications. The Agentforce Specialist can then edit the cloned template- adjusting instructions, grounding, or output format-to meet UC's specific business requirements. This is the recommended approach for customizing standard templates without altering the original, making it the correct answer.
* Option C: Save as New Version and edit as needed.Prompt Builder supports versioning for custom templates, allowing users to save new versions of an existing template to track changes. However, standard templates are typically read-only and cannot be versioned directly-versioning applies to custom templates after cloning. The question implies starting with the standard template's content, so cloning precedes versioning. This option is a secondary step, not the initial action, making it incorrect.
Why Option B is Correct:
Cloning is the documented method to repurpose a standard prompt template's content while enabling customization. After cloning, the specialist can modify the new custom template (e.g., tweak the email prompt's tone, structure, or grounding) to align with UC's requirements. This preserves the original standard template and follows Salesforce best practices.
References:
Salesforce Agentforce Documentation: Prompt Builder > Managing Templates- Details cloning standard templates for customization.
Trailhead: Build Prompt Templates in Agentforce- Explains how to clone standard templates to create editable copies.
Salesforce Help: Customize Standard Prompt Templates- Recommends cloning as the first step for modifying prebuilt templates.


質問 # 168
Agentforce は、外部サービス呼び出し (REST API コールアウト) の応答からのデータをプロンプト テンプレートに含める必要があります。
Agentforce スペシャリストはこの要件をどのように満たすべきでしょうか?

  • A. 「プロンプト指示の追加」フロー要素を使用します。
  • B. 外部サービスレコードのマージフィールドを使用します。
  • C. JSON を XML マージ フィールドに変換します。

正解：B

解説：
An Agentforce wants to include data from the response of an external service invocation (REST API callout) into a prompt template. The goal is to incorporate dynamic data retrieved from an external API into the AI- generated content.
Solution:
* Use External Service Record Merge Fields
* External Service Integration:
* Definition: External Services in Salesforce allow the integration of external REST APIs into Salesforce without custom code.
* Registration: The external service must be registered in Salesforce, defining the API's schema and methods.
* External Service Record Merge Fields:
* Purpose: Enables the inclusion of data from external service responses directly into prompt templates using merge fields.
* Functionality:
* Dynamic Data Inclusion: Allows prompt templates to access and use data returned from REST API callouts.
* Merge Fields Syntax: Use merge fields in the prompt template to reference specific data points from the API response.
Implementation Steps:
* Register the External Service:
* Use External Services to register the REST API in Salesforce.
* Define the API's schema, including methods and data structures.
* Create a Named Credential:
* Configure authentication and endpoint details for the external API.
* Use External Service in Flow:
* Build a Flow that invokes the external service and captures the response.
* Ensure the flow outputs the necessary data for use in the prompt template.
* Configure the Prompt Template:
* Use External Service Record merge fields in the prompt template to reference data from the flow's output.
* Syntax Example: {{flowOutputVariable.fieldName}}
Why Other Options are Less Suitable:
* Option A (Convert the JSON to an XML merge field):
* Irrelevance: Converting JSON to XML merge fields is unnecessary and complicates the process.
* Unsupported Method: Salesforce prompt templates do not support direct inclusion of XML merge fields from JSON conversion.
* Option C (Use "Add Prompt Instructions" flow element):
* Purpose of Add Prompt Instructions:
* Allows adding instructions to the prompt within a flow but does not facilitate including external data.
* Limitation: Does not directly help in incorporating external service responses into the prompt template.
References:
Salesforce Agentforce Specialist Documentation - Integrating External Services with Prompt Templates
:
Explains how to use External Services and merge fields in prompt templates.
Salesforce Help - Using Merge Fields with External Data:
Provides guidance on referencing external data in templates using merge fields.
Salesforce Trailhead - External Services and Flow:
Offers a practical understanding of integrating external APIs using External Services and Flow.
Conclusion:
By using External Service Record merge fields, the Agentforce Specialist can effectively include data from external REST API responses into prompt templates, ensuring that the AI-generated content is enriched with up-to-date and relevant external data.


質問 # 169
Universal Containers は最近、Agentforce Agents を使用して CRM ビジネス オペレーションに会話型 AI を統合するパイロット プログラムを開始しました。Agentforce Specialist は、エージェントの使いやすさとアクションの割り当てをどのように監視すればよいでしょうか?

  • A. エージェント分析を実行します。
  • B. メタデータ API を使用してエージェント ログ データを照会します。
  • C. プラットフォーム デバッグ ログに関するレポートを実行します。

正解：A

解説：
Monitoring the usability and action assignments of Agentforce Agents requires insights into how agents perform, how users interact with them, and how actions are executed within conversations. Salesforce provides Agent Analytics (Option C) as a built-in capability specifically designed for this purpose. Agent Analytics offers dashboards and reports that track metrics such as agent response times, user satisfaction, action invocation frequency, and success rates. This tool allows the Agentforce Specialist to assess usability (e.g., are agents meeting user needs?) and monitor action assignments (e.g., which actions are triggered and how often), providing actionable data to optimize the pilot program.
* Option A: Platform Debug Logs are low-level logs for troubleshooting Apex, Flows, or system processes. They don't provide high-level insights into agent usability or action assignments, making this unsuitable.
* Option B: The Metadata API is used for retrieving or deploying metadata (e.g., object definitions), not runtime log data about agent performance. While Agent log data might exist, querying it via Metadata API is not a standard or documented approach for this use case.
* Option C: Agent Analytics is the dedicated solution, offering a user-friendly way to monitor conversational AI performance without requiring custom development.
Option C is the correct choice for effectively monitoring Agentforce Agents in a pilot program.
:
Salesforce Agentforce Documentation: "Agent Analytics Overview" (Salesforce Help: https://help.salesforce.
com/s/articleView?id=sf.agentforce_analytics.htm&type=5)
Trailhead: "Agentforce for Admins" (https://trailhead.salesforce.com/content/learn/modules/agentforce-for- admins)


質問 # 170
エージェントは、リクエストを理解できない場合や、要求された情報を見つけられない場合にどのように応答しますか?

  • A. エラーメッセージが生成されます。
  • B. アクション タイプに基づいて、事前構成されたメッセージを使用します。
  • C. ユーザーにリクエストを言い換えるように求める一般的なメッセージを表示します。

正解：C

解説：
Agentforce Agents are designed to handle situations where they cannot interpret a request or retrieve requested data gracefully. Let's assess the options based on Agentforce behavior.
* Option A: With a preconfigured message, based on the action type.While Agentforce allows customization of responses, there's no specific mechanism tying preconfigured messages to action types for unhandled requests. Fallback responses are more general, not action-specific, making this incorrect.
* Option B: With a general message asking the user to rephrase the request.When an Agentforce Agent fails to understand a request or find information, it defaults to a general fallback response, typically asking the user to rephrase or clarify their input (e.g., "I didn't quite get that-could you try asking again?"). This is configurable in Agent Builder but defaults to a user-friendly prompt to encourage retry, aligning with Salesforce's focus on conversational UX. This is the correct answer per documentation.
* Option C: With a generated error message.Agentforce Agents prioritize user experience over technical error messages. While errors might log internally (e.g., in Event Logs), the user-facing response avoids jargon and focuses on retry prompts, making this incorrect.
Why Option B is Correct:
The default behavior of asking users to rephrase aligns with Agentforce's conversational design principles, ensuring a helpful response when comprehension fails, as noted in official resources.
References:
Salesforce Agentforce Documentation: Agent Builder > Fallback Responses - Describes general retry messages.
Trailhead: Build Agents with Agentforce - Covers handling ununderstood requests.
Salesforce Help: Agentforce Interaction Design - Confirms user-friendly fallback behavior.


質問 # 171
Universal Containers は、Agentforce for Sales を使用して類似の商談を見つけ、取引をより迅速に成立させようとしています。チームは、エージェントが商談をマッチングするために使用する基準を理解したいと考えています。Agentforce for Sales が類似の商談をマッチングするために使用する 1 つの基準は何ですか?

  • A. 一致した商談のステータスは、過去 12 か月間で「受注成立」です。
  • B. マッチングされた商談は同じアカウントに限定されます。
  • C. 一致する商談は過去 12 か月以内に作成されました。

正解：A

解説：
UC uses Agentforce for Sales to identify similar opportunities, aiding deal closure. Let's determine a criterion used by the "Find Similar Opportunities" feature.
Option A: Matched opportunities have a status of Closed Won from the last 12 months.Agentforce for Sales analyzes historical data to find similar opportunities, prioritizing "Closed Won" deals as successful examples.
Documentation specifies a 12-month lookback period for relevance, ensuring recent, applicable matches. This is a key criterion, making it the correct answer.
Option B: Matched opportunities are limited to the same account.While account context may factor in, Agentforce doesn't restrict matches to the same account-it considers broader patterns across opportunities (e.
g., industry, deal size). This is too narrow and incorrect.
Option C: Matched opportunities were created in the last 12 months.Creation date isn't a primary criterion- status (e.g., Closed Won) and recency of closure matter more. This doesn't align with documented behavior, making it incorrect.
Why Option A is Correct:
"Closed Won" status within 12 months is a documented criterion for Agentforce's similarity matching, providing actionable insights for deal closure.
References:
Salesforce Agentforce Documentation: Agentforce for Sales > Find Similar Opportunities - Specifies Closed Won, 12-month criterion.
Trailhead: Explore Agentforce Sales Agents - Details opportunity matching logic.
Salesforce Help: Sales Features in Agentforce - Confirms historical success focus.


質問 # 172
Universal Containers のサービス チームは、Agentforce からの標準ケース サマリー応答をカスタマイズしたいと考えています。
これを達成するために Agentforce スペシャリストは何をすべきでしょうか?

  • A. ケース オブジェクトのカスタム レコード サマリー プロンプト テンプレートを作成します。
  • B. 標準のエージェントアクションでケースを要約します。
  • C. ケース オブジェクトの標準レコード サマリー テンプレートをカスタマイズします。

正解：A

解説：
UC's service team seeks to customize the standard case summary response provided by Agentforce. Let's assess the options for tailoring this output.
* Option A: Create a custom Record Summary prompt template for the Case object.In Prompt Builder, the standard Record Summary prompt template generates summaries for objects like Case. To customize it, the Agentforce Specialist can create a new custom prompt template, specifying the Case object as the source, and adjust the instructions (e.g., tone, fields included) to meet UC's needs. This new template can then be invoked by an agent or flow, providing a tailored summary. This approach offers full control and aligns with Salesforce's customization process, making it the correct answer.
* Option B: Summarize the Case with a standard Agent action.Standard Agent actions (e.g., "Answer Questions") don't specifically target case summarization-they're broader in scope. There's no out-of- the-box "Summarize Case" action that allows customization of the response format, making this insufficient and incorrect.
* Option C: Customize the standard Record Summary template for the Case object.Standard prompt templates in Prompt Builder (e.g., Record Summary) are read-only and cannot be directly edited. Customization requires cloning or creating a new template, not modifying the standard one, making this incorrect.
Why Option A is Correct:
Creating a custom Record Summary prompt template allows full customization of the case summary, leveraging Prompt Builder's flexibility, as per Salesforce best practices.
References:
Salesforce Agentforce Documentation: Prompt Builder > Custom Templates - Details creating custom summaries.
Trailhead: Build Prompt Templates in Agentforce - Explains customizing standard outputs.
Salesforce Help: Record Summaries with AI - Recommends custom templates for tailored results.


質問 # 173
オプションを 1 つ選択します。
Universal Containers（UC）は、新しいエージェントの信頼性を確保するために、Agentforceテストセンターの活用を準備しています。UCはテストケースを含むCSVファイルを保有しており、ベストプラクティスと制限事項を理解するためにドキュメントを確認しています。
テスト センターでテストを実行しているときに CRM データの変更を回避するには、どのベスト プラクティスに従う必要がありますか。

  • A. データの変更を最小限に抑えるために、テスト ケースの数をテストごとに 50 に制限します。
  • B. テスト センターはサンドボックス環境でのみ使用してください。
  • C. 実稼働環境でテストを実行し、リアルタイムのデータの正確性を確認します。

正解：B

解説：
According to the AgentForce Testing and Validation Guidelines, all automated or large-scale test runs in Testing Center should be executed in a sandbox environment to prevent any unintended modifications to live CRM data.
Running tests in production can trigger record updates, create cases, or call actions that alter live data, violating best practice standards for safe validation. Testing in a sandbox ensures the environment mirrors production logic while maintaining data isolation.
Option A contradicts this best practice, as production testing risks data integrity. Option B does not prevent data changes - limiting test volume does not safeguard against unintended record modifications.
Therefore, the correct approach is Option C - Use the Testing Center only in the sandbox environment to maintain data safety and compliance.
Reference: AgentForce Testing Center Documentation - "Running Safe and Isolated Tests in Sandbox Environments."


質問 # 174
Agentforce スペシャリストがフィールド生成プロンプト テンプレートを作成しました。
テンプレートをユーザーに公開するには、Agentforce スペシャリストは何をする必要がありますか?

  • A. 自動起動フローを使用してテンプレートを呼び出します。
  • B. テンプレートを Lightning ページのフォーム フィールドに関連付けます。
  • C. 画面フローを使用して、フィールド生成プロンプト テンプレートを関連付けます。

正解：B

解説：
The Field Generation prompt template type is specifically designed to enable generative AI within the context of a Salesforce record field. To expose this functionality to an end-user, the Agentforce Specialist must associate the template with the form field on the Lightning page (B). This is accomplished using the Lightning App Builder:
* The Agentforce Specialist first creates a custom field (often a Long Text Area or Rich Text Area) on the desired object to store the AI-generated output.
* In the Lightning App Builder for the object's Record Page, the Specialist selects the field component.
* In the properties panel for that field component, there is a setting (often a dropdown) to select an active Field Generation Prompt Template.
* Once associated, an Einstein icon (or "Generate" button) appears next to the field on the record page, allowing the user to click it to run the prompt, review the AI-generated content, and then decide to use it to populate the field.
Options A and C (using Flows) are methods for calling prompt templates to automate the generation of content or to ground the prompt with more complex data (like related list information). However, for the Field Generation prompt template to be exposed directly to the user for on-demand generation and manual review (the intended user experience for this template type), it must be bound to the field itself on the Lightning Record Page.
Simulated Exact Extract of AgentForce documents (Conceptual Reference):
"The Field Generation prompt template is surfaced to the user via the Lightning Record Page. After the prompt template is created and activated in Prompt Builder, the Agentforce Specialist must edit the Lightning Record Page in the Lightning App Builder. The key step is to select the target field component and, within its property panel, assign the Field Generation Prompt Template from the available dropdown menu. This action binds the generative AI capability directly to the field, displaying the 'Generate' button to the user to trigger the AI-assisted content creation upon the record." Simulated Reference: AgentForce Study Guide, Chapter 3: Prompt Builder, Section 3.2: Field Generation Deployment, p. 55.


質問 # 175
Salesforce Agentforce スペシャリストは、Einstein Trust Layer 内のデータマスキングで何を設定できますか?

  • A. マスキング用の暗号化キー
  • B. マスクが免除されるプロファイル
  • C. マスクするプライバシーデータエンティティ

正解：C

解説：
In the Einstein Trust Layer, the Salesforce Agentforce Specialist can configure privacy data entities to be masked (Option C). This ensures sensitive or personally identifiable information (PII) is obfuscated when processed by AI models.
* Data Masking Configuration:
* The Agentforce Specialist defines which fields or data types (e.g., email, phone number, Social Security Number) should be masked. For example, masking the Email field in a prompt response to protect user privacy.
* This is done through declarative settings in Salesforce, where entities (standard or custom fields) are flagged for masking.
* Why Other Options Are Incorrect:
* A. Profiles exempt from masking: Exemptions are typically managed via permissions (e.g., field-level security), not directly within Einstein Trust Layer's Data Masking settings.
* B. Encryption keys for masking: Encryption is separate from masking. Masking involves obfuscation (e.g., replacing "[email protected]" with "@"), not encryption, which uses keys to secure data.
:
Einstein Trust Layer Documentation: States that Data Masking allows admins to "define which fields should be masked to protect sensitive data." Trailhead Module: "Einstein Trust Layer Basics" explains configuring privacy entities for masking.
Salesforce Help Article: "Secure AI with Einstein Trust Layer" details masking configurations for privacy compliance.


質問 # 176
......

合格させるSalesforce Agentforce-Specialist日本語テスト練習問題 試験問題集：https://www.passtest.jp/Salesforce/Agentforce-Specialist-JPN-shiken.html

関するブログ

もっと
Agentforce-Specialist-JPN 無料問題集