試験AB-620 トピック1 問題17 スレッド
Microsoft AB-620のリアル試験問題集
問題 #: 17
トピック #: 1
問題 #: 17
トピック #: 1
A company needs an agent in Copilot Studio to complete tasks by interacting with a legacy desktop application that does not use APIs. The builder needs to validate that UI automation can run in the supported execution context and needs a way to inspect how the automation behaves during testing conversations.
To meet the business needs, the solution must meet the following requirements:
- Enable the agent to perform UI automation against the legacy
application.
- Inspect execution details for the automation during conversations.
You need to configure the agent based on the requirements.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
To meet the business needs, the solution must meet the following requirements:
- Enable the agent to perform UI automation against the legacy
application.
- Inspect execution details for the automation during conversations.
You need to configure the agent based on the requirements.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
おすすめの解答：B,E 解答を投票する
[B] Add a Power Platform Desktop flow to control the desktop app
Power Automate for Desktop is Microsoft's dedicated Robotic Process Automation (RPA) solution designed specifically to automate legacy desktop applications without APIs.
Fulfills Requirement 1 (UI Automation): You can easily trigger these desktop flows directly from a Copilot Studio agent as an action. The flow runs in either attended or unattended mode within a supported Windows execution context.
Fulfills Requirement 2 (Inspect Execution): Power Automate provides a visual designer and detailed run logs. When testing your agent conversations, you can inspect the exact desktop flow execution logs, variable inputs/outputs, and step-by-step actions to see how the automation behaves.
[E]
Direct UI Automation without APIs: The query specifically states that the legacy desktop application does not use APIs. The Computer use capability (powered by Computer-Using Agents or CUAs) is designed exactly for this scenario. It allows the AI agent to interact directly with graphical user interfaces (GUIs) by visually interpreting screens, clicking buttons, and entering text just like a human operator.
Incorrect:
[Not A]
Custom Connectors require a target application to expose standard APIs (like REST). Since the legacy desktop application does not use APIs, a custom connector cannot interact with it directly.
[Not C]
You cannot access a live remote session directly within the testing pane to monitor real-time desktop interactions.
[Not D]
Publishing is a final deployment step. You should not publish an untested agent to production simply to validate its behavior; testing and inspection should always happen in the authoring environment before publication.
Reference:
https://techcommunity.microsoft.com/blog/copilot-studio-blog/automate-agent-evaluation-with-the-evaluation-apis/4511653
Power Automate for Desktop is Microsoft's dedicated Robotic Process Automation (RPA) solution designed specifically to automate legacy desktop applications without APIs.
Fulfills Requirement 1 (UI Automation): You can easily trigger these desktop flows directly from a Copilot Studio agent as an action. The flow runs in either attended or unattended mode within a supported Windows execution context.
Fulfills Requirement 2 (Inspect Execution): Power Automate provides a visual designer and detailed run logs. When testing your agent conversations, you can inspect the exact desktop flow execution logs, variable inputs/outputs, and step-by-step actions to see how the automation behaves.
[E]
Direct UI Automation without APIs: The query specifically states that the legacy desktop application does not use APIs. The Computer use capability (powered by Computer-Using Agents or CUAs) is designed exactly for this scenario. It allows the AI agent to interact directly with graphical user interfaces (GUIs) by visually interpreting screens, clicking buttons, and entering text just like a human operator.
Incorrect:
[Not A]
Custom Connectors require a target application to expose standard APIs (like REST). Since the legacy desktop application does not use APIs, a custom connector cannot interact with it directly.
[Not C]
You cannot access a live remote session directly within the testing pane to monitor real-time desktop interactions.
[Not D]
Publishing is a final deployment step. You should not publish an untested agent to production simply to validate its behavior; testing and inspection should always happen in the authoring environment before publication.
Reference:
https://techcommunity.microsoft.com/blog/copilot-studio-blog/automate-agent-evaluation-with-the-evaluation-apis/4511653
Hamasaki 2026-08-20 10:02:54
コメント
他人の解答コメントを賛成するのも、その解答に一票を入れることになります。したがって、すでに同じ意見の投票コメントが存在する場合、新規コメントをする代わりに賛成することもできます。
コメントを通報する
コメント中
今すぐ 新規登録 / ログイン （無料です）。