CertSafari

    Free Practice Questions for Extending Microsoft Power Platform Solutions with Code and AI (AB-400) Certification

    Guide checked for updates:
    20 Sep 2026
    Question bank created:
    20 Sep 2026
    Question bank last updated:
    21 Sep 2026

    Study with 351 exam-style practice questions designed to help you prepare for the Extending Microsoft Power Platform Solutions with Code and AI (AB-400).

    Exam experiencesNew

    Pass and fail outcomes from candidates who prepared here — advice, scores, and prep time.

    View exam experiences

    Start Practicing

    All Domains

    Practice with randomly mixed questions from all topics

    Question MixAll Topics
    FormatRandom Order

    Domain Mode

    Practice questions from a specific topic area

    Quiz History

    Exam Details

    Key information about Extending Microsoft Power Platform Solutions with Code and AI (AB-400)

    Official study guide

    View

    Question formats CertSafari offers
    • Multiple choice
    • Ordering
    • Matching
    • True/False
    renewal:

    Free online renewal assessment on Microsoft Learn

    passing score:

    700 or greater

    target audience:

    Microsoft Power Platform developers

    certification validity:

    Expires annually

    recommended experience:

    Development experience with Microsoft Power Platform services, JavaScript, JSON, TypeScript and Power Fx, C#, Python, HTML and YAML, RESTful Web APIs, Microsoft Azure, Microsoft Foundry and Microsoft Copilot Studio

    Exam Topics & Skills Assessed

    Skills measured (from the official study guide)

    Domain 1: Build Microsoft Power Platform solutions

    Subdomain 1.1: Design the technical architecture

    Analyze the technical architecture to identify solution components and their implementation approach - Design authentication and authorization for solution components - Determine whether requirements can be met with out-of-the-box functionality - Determine where to implement business logic including cloud services, client-side processing, business rules, plug-ins, and automation - Determine when to use standard tables, virtual tables, elastic tables, or connectors - Assess the impact of Microsoft Power Platform security features on solution components, including managed environments, data policies, security roles, teams, business units, and row sharing - Determine when to use deterministic or non-deterministic methods to implement business logic - Determine when to use code apps, generative pages, Power Apps component frameworks (PCFs), web resources, interactive agents, and Model Context Protocol (MCP) app widgets to implement the user experience - Determine when to use Microsoft Foundry or Microsoft Copilot Studio to build agents

    Subdomain 1.2: Design solution components

    Design Power Apps reusable components including generative pages, code components (PCF), and client scripting - Design custom connectors and MCP servers for use with Microsoft Power Platform solutions - Design Dataverse code components, including plug-ins and custom APIs - Design automations, including Power Automate cloud flows and Copilot Studio workflows - Design inbound and outbound integrations using Dataverse and Microsoft Azure - Design custom interfaces by using Power Apps code apps - Design custom agents that integrate with Microsoft Power Platform - Design monitoring and alerting, including Azure Monitor Application Insights and Microsoft Power Platform monitor alerts

    Subdomain 1.3: Implement application lifecycle management (ALM)

    Manage solution dependencies - Create and use environment variables - Manage solution layers - Implement and extend Microsoft Power Platform Pipelines - Create Continuous Integration/Continuous Deployment (CI/CD) automations using Microsoft Power Platform Build Tools

    Domain 2: Extend the user experience

    Subdomain 2.1: Apply business logic in model-driven apps by using client scripting

    Build code that targets the Client API object model - Determine an event handler registration approach - Create client scripting that targets the Dataverse Web API - Configure commands and buttons by using Power Fx and JavaScript - Implement navigation, dialogs, and notifications by using the Client API

    Subdomain 2.2: Create PCF code components

    Demonstrate the use of the different lifecycle events - Configure a code component manifest - Implement component interfaces - Package, deploy, and consume a component - Configure and use Device, Utility, and Web API features in component logic

    Subdomain 2.3: Build Power Apps code apps

    Configure code apps to use Microsoft Power Platform connections - Configure code apps to use Dataverse tables - Perform table and metadata operations on Dataverse data - Perform Dataverse actions and functions - Configure code apps to use Power Automate cloud flows - Configure code apps to use agents built in Copilot Studio - Configure code apps to use environment variables

    Subdomain 2.4: Deploy and manage Power Apps code apps

    Configure Content Security Policy (CSP) settings - Implement monitoring by using Azure Application Insights - Package, deploy, and share code apps - Troubleshoot code apps by using Monitor and other browser-based debugging tools - Optimize code app performance and resource usage

    Domain 3: Extend Microsoft Power Platform

    Subdomain 3.1: Create a Dataverse plug-in

    Demonstrate the use of the different event execution pipeline stages - Develop a plug-in that uses the execution context - Develop a plug-in that implements business logic - Implement images to support plug-in logic - Perform operations in plug-ins by using the Organization service - Optimize plug-in performance - Configure a Dataverse custom API message - Register plug-in components by using the Plug-in Registration Tool - Develop a plug-in that implements a custom API - Configure Dataverse business events - Configure Microsoft Power Platform managed identity for plug-ins

    Subdomain 3.2: Perform operations by using platform APIs

    Perform operations by using the Dataverse Web API - Perform operations by using the Organization service - Implement API limit retry policies - Optimize solution components for performance, concurrency, transactions, and bulk operations - Implement and troubleshoot authentication by using OAuth - Perform asynchronous logic by using background operations - Perform operations by using Dataverse SDKs for .NET and Python

    Subdomain 3.3: Process workloads by using Microsoft Azure Functions

    Process long-running operations by using Azure Functions for Microsoft Power Platform solutions - Implement scheduled and event-driven triggers in Azure Functions for Microsoft Power Platform solutions - Authenticate to Microsoft Power Platform by using managed identities

    Subdomain 3.4: Configure Power Automate cloud flows and Copilot Studio workflows

    Implement complex expressions in flow steps - Implement flow control actions including error handling - Configure trigger filter and retry policies - Develop reuseable logic by using child flows - Implement authentication for the Dataverse connector by using service principals

    Subdomain 3.5: Build Microsoft Foundry agents by using code that integrates with the Microsoft Power Platform

    Integrate custom agents by using Microsoft Power Platform MCP servers - Connect custom agents to Copilot Studio agents - Integrate custom agents with Dataverse data by using Work IQ - Consume Copilot Studio agents by using the Copilot Studio client library

    Domain 4: Develop integrations

    Subdomain 4.1: Publish and consume Dataverse events

    Publish a Dataverse event by using the IServiceEndpointNotificationService - Publish a Dataverse event by using the Plug-in Registration Tool - Register service endpoints including webhooks, Azure Service Bus, and Azure Event Hub - Recommend options for listening to Dataverse events

    Subdomain 4.2: Implement synchronization for Dataverse data

    Perform data synchronization by using change tracking - Develop code that uses alternate keys - Synchronize data by using the UpsertRequest message

    Subdomain 4.3: Create custom connectors

    Implement authentication for custom connectors - Configure policy templates to modify connector behavior at runtime - Import definitions from existing APIs including Open API definitions, Azure services, and GitHub - Create a custom connector for an Azure service - Develop an Azure Function to be used in a custom connector - Extend the Open API definition for a custom connector - Develop code for a custom connector to transform data

    Techniques & products

    Microsoft Power Platform
    Microsoft Dataverse
    Dataverse Web API
    Dataverse Organization service
    Dataverse SDKs for .NET and Python
    Dataverse plug-ins
    Dataverse custom APIs
    Dataverse business events
    Plug-in Registration Tool
    Change tracking
    Alternate keys
    UpsertRequest
    Standard, virtual and elastic tables
    Power Apps
    Power Apps code apps
    Power Apps component framework (PCF)
    Generative pages
    Model-driven apps
    Client API object model
    Power Fx
    JavaScript
    TypeScript
    JSON
    C#
    Python
    HTML
    YAML
    Web resources
    Power Automate cloud flows
    Child flows
    Microsoft Copilot Studio
    Copilot Studio client library
    Microsoft Foundry
    Model Context Protocol (MCP) servers
    MCP app widgets
    Work IQ
    Custom connectors
    Open API definitions
    Policy templates
    Microsoft Azure
    Azure Functions
    Azure Service Bus
    Azure Event Hub
    Webhooks
    Azure Monitor Application Insights
    Power Platform monitor
    Managed identities
    OAuth
    Service principals
    Content Security Policy (CSP)
    Environment variables
    Solution layers and dependencies
    Microsoft Power Platform Pipelines
    Power Platform Build Tools
    CI/CD automation
    Managed environments
    Data policies
    Security roles, teams and business units
    Microsoft Power Platform CLI
    Visual Studio and Visual Studio Code
    RESTful Web APIs

    CertSafari is not affiliated with, endorsed by, or officially connected to Microsoft Corporation. Full disclaimer