A city tax office must post property assessments in a legacy app that offers screens and no API. A person must review each posted assessment. Which design fits?
Select an answer to reveal the explanation.
Short Explanation
When the only door is the same screen a clerk already clicks, you send an agent through that screen and you still have someone initial the posting. Computer Use fits this legacy app because it has no API, and the review stays on the person. A connector cannot call an API the city does not have.
Full Explanation
Computer Use is the Copilot Studio capability for an application that can be operated only through its screens. This assessment app has screens and no API, and the office still wants a person to review each posted assessment, so Computer Use plus that review is the design that matches both facts. A connector is the right extension when a supported API exists, and this app does not publish one, so aiming a connector at a missing API does not post anything. A Model Context Protocol server fits a tool server that already speaks that protocol, which this legacy app does not, and posting with no reviewer drops the control the office required. A topic that explains the tax rate is a knowledge reply, and it does not enter the assessment. Exam caveat: Computer Use is the fallback for the missing API, not a reason to skip the human review the office already named. The person's review is part of the design, not a courtesy added later. Operational check: confirm the app still has no supported API, pilot Computer Use against a test parcel, and show that the assessment stays unposted until a person accepts it.