logo
Exam overview and study plan

AB-620 Practice Questions

AI Agent Builder Associate

Read questions, check verified answers and discuss the reasoning. Use reading options to shape your revision, or switch to the simulator for timed practice.

View 66 free questions

66 questions in this view

Page 1 of 11

Question 1

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-functional 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.

Current environment

Channels

  • Public website: Embedded web chat
  • Mobile app: In-app chatbot
  • Microsoft Teams: Internal support agent access

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.

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.

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).

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
    • 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.

Knowledge integration

  • The agent must use scalable methods for knowledge integration and must not rely on manually authored Q&A topics for each document.

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

Technical requirements

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.


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.


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.


Monitoring and maintenance

  • All conversations and actions must be logged for auditing.
  • Weekly reviews of transcripts and metrics must be conducted.
  • Topics, flows, and knowledge sources must be updated as policies or systems evolve.

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.

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.
You need to determine which authentication model should be applied to each Blue Yonder Copilot interaction scenario to comply with the company’s security and governance requirements.

Which authentication requirement should you apply to each scenario? To answer, move the appropriate authentication requirements to the correct user scenarios. You may use each authentication requirement 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.
User scenarioAuthentication requirement
A customer asks, “What is the baggage allowance for international flights?”
A customer asks, “Can I review my upcoming trips?”
An internal support agent accesses the Copilot agent from Microsoft Teams to look up a loyalty member’s profile.

Question 2

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-functional 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.

Current environment

Channels

  • Public website: Embedded web chat
  • Mobile app: In-app chatbot
  • Microsoft Teams: Internal support agent access

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.

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.

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).

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
    • 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.

Knowledge integration

  • The agent must use scalable methods for knowledge integration and must not rely on manually authored Q&A topics for each document.

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

Technical requirements

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.


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.


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.


Monitoring and maintenance

  • All conversations and actions must be logged for auditing.
  • Weekly reviews of transcripts and metrics must be conducted.
  • Topics, flows, and knowledge sources must be updated as policies or systems evolve.

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.

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.
You need to determine an appropriate implementation related to the use of agent flows that is based on Blue Yonder's design and compliance standards.

Which implementation method should you use for each scenario? To answer, move the appropriate implementation methods to the correct scenarios. You may use each implementation method 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.
Scenario
A topic includes a series of steps that replicate logic already defined in another flow.
A topic provides a natural language explanation of a process but does not execute it.
A topic includes a step that triggers a reusable process to update booking details.

Question 3

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-functional 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.

Current environment

Channels

  • Public website: Embedded web chat
  • Mobile app: In-app chatbot
  • Microsoft Teams: Internal support agent access

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.

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.

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).

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
    • 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.

Knowledge integration

  • The agent must use scalable methods for knowledge integration and must not rely on manually authored Q&A topics for each document.

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

Technical requirements

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.


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.


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.


Monitoring and maintenance

  • All conversations and actions must be logged for auditing.
  • Weekly reviews of transcripts and metrics must be conducted.
  • Topics, flows, and knowledge sources must be updated as policies or systems evolve.

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.

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.
You need to ensure that every AI-generated response from the agent in Copilot Studio includes a disclaimer that complies with the company’s security and governance policies.

Which two actions should you perform? Each correct answer presents part of the solution. Choose two.

NOTE: Each correct selection is worth one point.

Select an answer above, then submit your vote. Reading or practicing does not cast a vote.

Question 4

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-functional 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.

Current environment

Channels

  • Public website: Embedded web chat
  • Mobile app: In-app chatbot
  • Microsoft Teams: Internal support agent access

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.

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.

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).

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
    • 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.

Knowledge integration

  • The agent must use scalable methods for knowledge integration and must not rely on manually authored Q&A topics for each document.

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

Technical requirements

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.


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.


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.


Monitoring and maintenance

  • All conversations and actions must be logged for auditing.
  • Weekly reviews of transcripts and metrics must be conducted.
  • Topics, flows, and knowledge sources must be updated as policies or systems evolve.

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.

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.
You need to evaluate whether the current configuration decisions for the Blue Yonder Copilot agent comply with the company’s security and governance policies.

Which compliance status should you assign to each configuration decision? To answer, move the appropriate compliance statuses to the correct configuration decisions. You may use each compliance status 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.
Configuration decisionCompliance status
The agent allows anonymous access general inquiries such as baggage policies.
The agent uses an open web search to answer questions beyond internal knowledge.
The team relies only on default content filters without custom RAI instructions.
The agent uses one shared admin credential for all internal data access.

Question 5

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-functional 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.

Current environment

Channels

  • Public website: Embedded web chat
  • Mobile app: In-app chatbot
  • Microsoft Teams: Internal support agent access

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.

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.

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).

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
    • 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.

Knowledge integration

  • The agent must use scalable methods for knowledge integration and must not rely on manually authored Q&A topics for each document.

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

Technical requirements

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.


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.


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.


Monitoring and maintenance

  • All conversations and actions must be logged for auditing.
  • Weekly reviews of transcripts and metrics must be conducted.
  • Topics, flows, and knowledge sources must be updated as policies or systems evolve.

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.

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.
You need to configure the agent in Copilot Studio to use internal and external partner knowledge sources to answer user questions about the airline services.

Which two actions should you perform? Each correct answer presents part of the solution. Choose two.

NOTE: Each correct selection is worth one point.

Select an answer above, then submit your vote. Reading or practicing does not cast a vote.

Question 6

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-functional 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.

Current environment

Channels

  • Public website: Embedded web chat
  • Mobile app: In-app chatbot
  • Microsoft Teams: Internal support agent access

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.

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.

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).

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
    • 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.

Knowledge integration

  • The agent must use scalable methods for knowledge integration and must not rely on manually authored Q&A topics for each document.

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

Technical requirements

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.


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.


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.


Monitoring and maintenance

  • All conversations and actions must be logged for auditing.
  • Weekly reviews of transcripts and metrics must be conducted.
  • Topics, flows, and knowledge sources must be updated as policies or systems evolve.

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.

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.
You need to configure the agent in Copilot Studio to meet Blue Yonder’s Responsible AI and data protection requirements.

Which three actions should you perform? Each correct answer presents part of the solution. Choose three.


NOTE: Each correct selection is worth one point

Select an answer above, then submit your vote. Reading or practicing does not cast a vote.