A company uses an agent in Copilot Studio that produces structured responses using a reusable instruction template. The responses follow the required tone and format. During a compliance review, the team discovers that the responses were generated using a model that is not on the approved list.
The company requires that the reusable instruction template continues to be used and the model used for prompt-driven responses meets governance requirements.
The solution must ensure that prompt-driven responses are generated using an approved model.
You need to configure the solution that meets the requirements.
Which two actions should you perform? Each correct answer presents part of the solution. Choose two.
NOTE: Each correct selection is worth one point.

• A.Ensure the reusable instruction template is the one applied to the agent that generates the structured response.
• B.Select an approved model from the Microsoft Foundry model catalog in the configuration that is used for prompt-driven response generation.
• C.Enable citations so generated responses can be traced and comply with governance requirements.
• D.Configure Azure AI Search as the grounding source so the approved model requirement is enforced during response generation.
• E.Publish the agent so that the model used by prompt-driven responses is updated automatically.
• F.Add a line to the instruction template that requires the agent to use only approved models when generating responses.

Comment: *

Name: *

Email: *

Verification: *

You need to connect Operations Concierge to Fabrikam Inc.'s Azure AI Search knowledge index while complying with security requirements.
Which configuration should you use for each requirement? To answer, move the appropriate configurations to the correct requirements You may use each configuration once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point

Correct Answer:

Topic 2, Blue Yonder Airlines
Background
Blue Yonder Airlines is a global carrier headquartered in Los Angeles, California, operating domestic and international flights. The company serves millions of passengers annually through its website, mobile app, and call centers. To improve customer service efficiency and reduce call center volume, Blue Yonder is deploying an AI agent in Microsoft Copilot Studio.
The agent will handle customer inquiries across multiple channels - web chat, mobile app, and Microsoft Teams (for internal support staff). It will answer questions, retrieve data from enterprise systems, and escalate to human agents when needed.
The project is led by a cross-function team:
Product manager: Defines requirements and success metrics.
Lead agent author: Designs topics, intents, and generative behavior.
Flow designers: Build agent flows and integrations.
IT/security and compliance: Oversees identity, data protection, and Responsible AI (RAI) compliance.
Segment
Current environment
Channels -
Public website: Embedded web chat
Mobile app: In-app chatbot -
Microsoft Teams: Internal support agent access
Segment
Identity and access
Customers: Anonymous access for general inquiries (e.g., flight status, baggage policy).
Authentication is required for personal data access (e.g., bookings, loyalty points).
Internal staff: Authenticate via Microsoft Entra ID.
Segment
Data sources
Reservation and Ticketing System (internal): REST API, no prebuilt connector with custom enterprise database.
Flight Status and Weather APIs (external): REST APIs with API keys.
Customer Support Knowledge Base: SharePoint library with PDFs and policy documents.
Loyalty Program Data: Stored in Dynamics 365 and Dataverse.
Travel Advisory Content: Uses REST API with partner services.
Segment
Integration mechanisms
Custom connectors must be used for internal APIs that lack prebuilt connectors.
HTTP request nodes may be used for lightweight external APIs.
Knowledge sources must be used for unstructured content.
Agent flows must be used to encapsulate reusable logic (e.g., rebooking).
Segment
Business requirements
Omnichannel support -
Deploy the agent across web, mobile, and Teams with a consistent user experience. The Teams deployment must also support internal staff.
Self-service capabilities -
The agent must handle common inquiries such as:
Flight status -
Segment
Booking and rebooking
Loyalty program questions -
Travel policies and baggage rules
Human escalation
If the agent cannot resolve an issue or the user requests help, it must:
Escalate to a human agent.
Transfer the conversation transcript and relevant context.
Redact any sensitive personal data before escalation.
Segment
Knowledge integration
The agent must use scalable methods for knowledge integration and must not rely on manually authored Q&A topics for each document.
Segment
Performance metrics
First-contact resolution: +25%
Tier-1 call deflection: ≥20%
Response time: 90% of queries answered within 30 seconds
Accuracy: ≥95% for known FAQs -
CSAT: ≥85% for AI-handled interactions
Segment
Technical requirements
Title
Platform constraints
No custom code is permitted; only Copilot Studio's built-in tools may be used.
All backend logic must be implemented using agent flows.
Markdown must be used for formatting (e.g., bold, bullet points); HTML is not supported.
Title
Authentication
Sign-in is required for personal data access.
Anonymous access is allowed for general inquiries.
User identity must be used for data access; shared or builder credentials must not be used.
Title
Compliance and security
Power Platform DLP policies must be enforced to block unauthorized data flows.
Responsible AI content moderation filters must be enabled.
Prompt modifications must be added to enforce tone, disclaimers, and refusal behavior.
Disclaimers must be applied consistently across all generative responses. Manual edits to individual topics must be avoided.
Title
Monitoring and maintenance
All conversations and actions must be logged for auditing.
Weekly reviews of transcripts and metrics must be conducted.
Title
Issues and constraints
API rate limits: External APIs (e.g., flight status) have usage limits. Agent flows must handle retries and caching to avoid exceeding quotas.
Knowledge base limits: Copilot Studio has limits on the number and size of indexed documents. Large files must be split or summarized.
Generative answer risks: Generative responses must be constrained to avoid policy violations. Prompt modifications and filters must be used to enforce tone, safety, and compliance.
User input variability: Users phrase questions in diverse ways. Topics must include varied trigger phrases and fallback handling.
Authentication UX: The agent must clearly explain when sign-in is required and handle transitions smoothly across channels.
Title
Problem statement
Blue Yonder Airlines must deploy a secure, scalable, and policy-compliant AI agent using Microsoft Copilot Studio. The agent must deliver accurate, helpful, and safe responses across multiple channels, integrate with enterprise systems, and support both anonymous and authenticated users. It must adhere to strict data protection and Responsible AI standards while improving customer service efficiency and satisfaction.

Comment: *

Name: *

Email: *

Verification: *

A team has an existing agent in Copilot Studio and must move it to a different target location without rebuilding the agent. Some builders use Copilot Studio in the web app, while others use Copilot Studio in Microsoft Teams.
You need a supported approach to move the existing agent to the target location by using ALM practices. The solution must avoid rebuilding the agent.
What should you do?

• A.Configure pipeline settings first and rely on pipelines to discover and package the agent automatically without adding it to a solution.
• B.Create a custom solution, add the existing agent to the solution, export the solution containing the agent, and import the solution into the target environment.
• C.Duplicate the agent in the source and manually recreate the changes in the target to avoid solution dependencies.
• D.Remove agent components directly from the solution so that export and import will succeed.

Comment: *

Name: *

Email: *

Verification: *

A company uses an agent in Copilot Studio that produces structured responses using a reusable instruction template. The responses follow the required tone and format. During a compliance review, the team discovers that the responses were generated using a model that is not on the approved list.
The company requires that the reusable instruction template continues to be used and the model used for prompt-driven responses meets governance requirements.
The solution must ensure that prompt-driven responses are generated using an approved model.
You need to configure the solution that meets the requirements.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.

• A.Select an approved model from the Microsoft Foundry model catalog in the configuration that is used for prompt-driven response generation.
• B.Configure Azure AI Search as the grounding source so the approved model requirement is enforced during response generation.
• C.Ensure the reusable instruction template is the one applied to the agent that generates the structured response.
• D.Publish the agent so that the model used by prompt-driven responses is updated automatically.
• E.Enable citations so generated responses can be traced and comply with governance requirements.
• F.Add a line to the instruction template that requires the agent to use only approved models when generating responses.

Comment: *

Name: *

Email: *

Verification: *

An agent calls a flow to a database. The agent requires structured output values to be returned. The agent receives unexpected or empty values.
You need to configure the agent so that data is exchanged correctly between the agent and the flow. What should you do?

• A.Validate parameter definitions.
• B.Review the flow run history.
• C.Change the trigger schema.
• D.Add a Parse JSON inside the flow.
• E.Republish the agent.

Comment: *

Name: *

Email: *

Verification: *