Subdomain 1.1: Analyze requirements for AI-powered business solutions
1.You are designing a customer support agent using Microsoft Copilot Studio for a global logistics company. The agent must provide real-time shipping status updates to customers. You have access to a nightly data dump of shipping logs and a REST API that provides live status. Which data source strategy should you prioritize to ensure the 'Timeliness' requirement of data grounding is met?
- A.Ingest the nightly data dump into Azure AI Search and schedule an indexer to run every 24 hours.
- B.Create a custom plugin to query the live REST API dynamically during the conversation.
- C.Fine-tune a small language model (SLM) using the historical shipping logs.
- D.Upload the shipping logs as static knowledge documents within Copilot Studio.
Show answer & explanation
Correct answer: B — Create a custom plugin to query the live REST API dynamically during the conversation.
- A. Incorrect. Ingesting a nightly data dump with a 24-hour indexer schedule results in data that is at most 24 hours old. This strategy fails to provide real-time status updates and does not meet the strict 'Timeliness' requirement for a logistics company where status changes occur throughout the day.
- B. Correct. Creating a custom plugin (Action) to query the live REST API dynamically during the conversation allows the agent to fetch current shipment status on demand. This pattern ensures that the grounding data reflects the most recent state of the shipment, satisfying the 'Timeliness' requirement by providing real-time data.
- C. Incorrect. Fine-tuning an SLM on historical shipping logs embeds past information into the model weights, but it cannot provide live, factual updates. This approach is better suited for tone or domain-specific language patterns rather than dynamic real-time status tracking, and it is expensive to update frequently.
- D. Incorrect. Uploading shipping logs as static knowledge documents within Copilot Studio makes the information effectively read-only and stale the moment the source changes. Static documents are appropriate for reference materials like policy manuals, not for live tracking data.