試験UiPath-AAAv1 トピック1 問題26 スレッド
UiPath UiPath-AAAv1のリアル試験問題集
問題 #: 26
トピック #: 1
問題 #: 26
トピック #: 1
An agent uses Web Search, Slack integration, and a custom process to resolve IT support tickets. The agent must:
* Retrieve relevant troubleshooting steps from the web.
* Notify the user via Slack if a solution is found.
* Escalate unresolved tickets via a custom process.
Which evaluation strategy ensures comprehensive coverage while avoiding redundancy?
* Retrieve relevant troubleshooting steps from the web.
* Notify the user via Slack if a solution is found.
* Escalate unresolved tickets via a custom process.
Which evaluation strategy ensures comprehensive coverage while avoiding redundancy?
おすすめの解答：C 解答を投票する
Cis correct - UiPath recommends structuringagent evaluationsaroundfunctional setsthat align with expected behavior and edge conditions. This strategy:
* Validatesend-to-end logic, not just isolated tool usage
* Helps assess whethertool combinationswork as designed
* Supportstraceable diagnosisof failures or regressions
In this scenario:
* Set 1: Valid Web Search results#Slack notification (success path)
* Set 2: Failed/irrelevant Web Search#Escalation (fallback path)
* Set 3: Edge cases (e.g., ambiguous input, multiple valid matches)
This avoids theredundancyandvolume bloatseen in options B and D.
Option A is too loose - relying solely on random inputs and "LLM-as-a-Judge" introduces risk ofincomplete testing.
Grouping byreal-world interaction patternsmirrors how agents behave in production. It ensures high coverage while keeping evaluation efficient, consistent, andtightly aligned with business logic.
* Validatesend-to-end logic, not just isolated tool usage
* Helps assess whethertool combinationswork as designed
* Supportstraceable diagnosisof failures or regressions
In this scenario:
* Set 1: Valid Web Search results#Slack notification (success path)
* Set 2: Failed/irrelevant Web Search#Escalation (fallback path)
* Set 3: Edge cases (e.g., ambiguous input, multiple valid matches)
This avoids theredundancyandvolume bloatseen in options B and D.
Option A is too loose - relying solely on random inputs and "LLM-as-a-Judge" introduces risk ofincomplete testing.
Grouping byreal-world interaction patternsmirrors how agents behave in production. It ensures high coverage while keeping evaluation efficient, consistent, andtightly aligned with business logic.
中里** 2026-06-26 10:29:52
コメント
他人の解答コメントを賛成するのも、その解答に一票を入れることになります。したがって、すでに同じ意見の投票コメントが存在する場合、新規コメントをする代わりに賛成することもできます。
コメントを通報する
コメント中
今すぐ 新規登録 / ログイン （無料です）。