Microsoft Dataverse: Tables, Data & Power Fx

What is the Common Data Model (CDM) in the context of Microsoft Dataverse?

• AA custom ETL pipeline that transforms data between disconnected systems
• BA standardized schema that defines predefined table definitions shared across Microsoft products✓
• CA visual, no-code designer used to configure business rules on a table
• DA row-level security policy that restricts which records a user can view

Answer: The Common Data Model is a standardized schema that defines how business data is structured and shared across applications. It provides predefined table definitions for concepts such as accounts, contacts, products and cases, so data created in one Microsoft product can be used directly in another. Traditional databases lack this shared schema and typically need custom extract, transform and load pipelines to integrate data between systems. Row-level security and business rule designers are separate Dataverse features unrelated to the CDM.

According to Microsoft Learn, which security capability does Dataverse provide out of the box that traditional databases typically require custom scripting to achieve?

• ARow-level and column-level access restrictions alongside role-based access control✓
• BA drag-and-drop form designer for building data entry screens
• CA formula language for writing spreadsheet-style calculations
• DA relational structure of tables made up of rows and columns

Answer: Dataverse provides advanced security capabilities out of the box, including role-based access control, row-level access restrictions and column-level security. Traditional databases typically require custom scripts, stored procedures and manually configured permissions to achieve equivalent protection. Tables of rows and columns exist in both systems, so that alone is not a security differentiator. Form designers and formula languages address data entry and calculations, not access control.

What did the Dataverse Model Context Protocol (MCP) server, released in 2025, enable for Copilot Studio agents?

• AAutomatic migration of SQL Server schemas into Dataverse tables
• BConversational, interactive querying of structured Dataverse data to ground agent responses✓
• CScheduled backup of Dataverse records to an external data lake
• DEncryption of Dataverse data using a customer-supplied key

Answer: The Dataverse MCP server makes structured Dataverse data interactive, allowing Copilot Studio agents to query it conversationally and use it to drive intelligent workflows instead of requiring custom API integrations. This grounds agent answers in up-to-date business records rather than static training data. Schema migration and scheduled backups are unrelated data-management tasks, and customer-managed keys are an encryption feature, not a conversational data capability.

Which set of tables does Dataverse provide as standard, ready-to-use tables aligned with the Common Data Model?

• AServer, Database, Index and Backup
• BEmployee, Payroll, Timesheet and Benefits
• CAccount, Contact, Opportunity and Case✓
• DInvoice, Ledger, Budget and Asset

Answer: Dataverse includes a library of standard tables aligned with the Common Data Model, covering concepts such as Account, Contact, Opportunity and Case, already integrated with Dynamics 365 applications and Power Platform tools. Payroll and finance-style tables are examples of business-specific data a maker would instead need to build as custom tables. Server and database administration concepts belong to traditional infrastructure management, not the standard Dataverse table library.

How does Dataverse implement a one-to-many relationship, such as one Account having many related Contact records?

• AWith a rollup column that totals values from the parent record
• BWith a business rule that copies the parent record's columns
• CWith an automatically created intersect table that stores each association
• DWith a lookup column on the related table that points back to the parent record✓

Answer: In a one-to-many relationship, a single row in the parent table can be related to multiple rows in a related table, and Dataverse implements this using a lookup column on the related table that points to the parent record. An intersect table is instead how Dataverse manages many-to-many relationships, not one-to-many ones. Rollup columns aggregate values rather than establish relationships, and business rules enforce logic rather than link records.

A maker needs to model that a single Employee can be assigned to many Projects, and a single Project can have many Employees. Which Dataverse relationship type fits this scenario?

• AA business rule that requires a project to have at least one employee
• BA one-to-many relationship, managed through a lookup column on the Project table
• CA many-to-many relationship, managed through an automatically created intersect table✓
• DA formula column that calculates the number of employees on a project

Answer: A many-to-many relationship connects rows in one table to multiple rows in another table and vice versa, and Dataverse manages it through an automatically created intersect table that stores the associations. A lookup column only supports one-to-many relationships, not many-to-many. A formula column would compute a value, not model a relationship, and a business rule enforces a data policy rather than defining how tables connect.

Which Dataverse column data type presents users with a predefined list of options to choose from, such as a Status of Active, Inactive or Pending?

• AChoice✓
• BFile and Image
• CLookup
• DFormula (fx)

Answer: A Choice column is a predefined list of options the user can select, such as a Status of Active, Inactive or Pending. A Lookup column instead references a row in another table to build a relationship, and a Formula (fx) column computes a value automatically from other columns using Power Fx. File and Image columns store binary data such as attachments or photos, not a fixed list of selectable options.

Which of the following is something a Dataverse business rule can do using its visual, no-code designer?

• ADisplay an error message and prevent a record from being saved when conditions are not met✓
• BAggregate values from related records on a scheduled basis
• CQuery Dataverse data conversationally from within a Copilot Studio agent
• DExport a solution from a development environment into a test environment

Answer: Business rules can set column values, make columns required or optional, show or hide columns, and display error or warning messages that prevent a record from being saved when conditions are not met. Conversational querying of Dataverse data is instead a capability of the Dataverse MCP server used by Copilot Studio agents. Aggregating related-record values on a schedule describes a rollup column, and exporting solutions between environments is an application lifecycle management task, not a business rule action.

A maker builds a business rule that hides a column and locks another column when a condition is met. In which type of Power Apps will these particular actions take effect?

• ACanvas apps only
• BBoth canvas apps and model-driven apps equally
• CNeither canvas apps nor model-driven apps
• DModel-driven apps only✓

Answer: Not all business rule actions are available in canvas apps: actions such as showing or hiding columns, locking or unlocking columns, and recommendations apply to model-driven apps only. Business rules defined at the table level otherwise apply across both app types, but this particular subset of actions is a model-driven-only exception. Canvas apps alone would be the reverse of the documented behaviour, and saying neither app type supports them contradicts the fact that model-driven apps do.

A team wants a Power Automate flow to run automatically whenever a Service Request record in Dataverse is created or updated. Which flow type fits this requirement?

• AA scheduled flow, triggered by a time-based schedule
• BAn automated cloud flow, triggered by the Dataverse record event✓
• CAn instant flow, triggered manually from a Power Apps form
• DA business rule, triggered by a column value change

Answer: Automated cloud flows are triggered automatically when a Dataverse record is created, updated or deleted, without any manual intervention. An instant flow instead needs a user to start it manually, such as from a Power Apps form or a Teams message, and a scheduled flow runs on a time-based schedule rather than in response to a record event. A business rule enforces data policy on a table but does not run as a Power Automate flow.

A field technician needs to trigger a Power Automate flow manually by tapping a button inside a Power Apps form. Which flow type supports this?

• AAn automated cloud flow
• BA rollup column
• CA scheduled flow
• DAn instant flow✓

Answer: Instant flows are triggered manually by a user from within a Power Apps form or a Teams message, so they start on demand rather than automatically. Automated cloud flows instead react to a Dataverse record being created, updated or deleted, and scheduled flows run on a time-based schedule such as a nightly sync, neither of which is a manual button trigger. A rollup column aggregates related-record data and is not a Power Automate flow type at all.

Which Dataverse form type lets a user create a new record without leaving their current context, typically opened from a lookup field or a New button?

• AQuick view form
• BCard form
• CQuick create form✓
• DMain form

Answer: A Quick create form is a streamlined form used to create a new record without leaving the current context, typically accessed through a lookup field or the New button in a navigation bar. A Main form is instead the primary, full-featured form for viewing or editing a complete record, and a Quick view form only displays read-only summary information from a related record. A Card form shows a compact set of key column values within views and dashboards, not a record-creation screen.

A service manager wants a Dataverse view that shows only the records currently owned by or assigned to them, without building a custom filter. Which built-in view meets this need?

• AA maker-defined custom view
• BThe Active records view
• CThe My records view✓
• DA quick view form

Answer: The My records view displays only records owned by or assigned to the current user, with no custom filter work needed. The Active records view instead is typically the default view showing all records with an Active status, regardless of who owns them. A maker-defined custom view could be built to replicate this, but the question asks for the built-in option, and a quick view form is a record-detail component, not a list view at all.

A maker wants to create a new Dataverse table by describing it in plain language rather than manually configuring columns. Where in the Power Apps maker portal do they start this process?

• ABy selecting Tables, then choosing Start with Copilot and describing the table✓
• BBy exporting an unmanaged solution and editing its table definitions offline
• CBy opening the Business rules tab under Customizations for an existing table
• DBy navigating to the Power Automate flow designer and adding a Dataverse trigger

Answer: To create a table using Copilot, a maker navigates to Tables in the Power Apps maker portal, selects Start with Copilot, and describes the table they want in everyday language, after which Copilot generates a draft table with suggested columns and sample data. The Business rules tab is instead where an existing table's business logic is configured, not where new tables are created. The Power Automate flow designer builds flows rather than tables, and editing an exported solution offline is a manual approach that bypasses the conversational experience entirely.

How does Microsoft describe Power Fx as a programming language?

• AA scripting language that only runs inside Power Automate desktop flows
• BA general-purpose, strongly typed, declarative and functional language with Excel-like syntax✓
• CA markup language used only to style forms and views in model-driven apps
• DA query language used exclusively to read data from SQL Server databases

Answer: Power Fx is a general-purpose, strongly typed, declarative and functional programming language designed for low-code scenarios, with syntax similar to Microsoft Excel formulas that makes it approachable for business users. It is used across canvas apps, model-driven apps, Dataverse, Power Automate and Copilot Studio, so it is not confined to styling forms or querying a single database product. It is also not limited to desktop flows, since Power Fx expressions appear throughout Power Platform, including cloud flow steps.

What is the current production status of Dataverse Functions, the reusable server-side Power Fx logic blocks formerly known as instant low-code plug-ins?

• AThey require a professional developer licence before they can be used at all
• BThey were retired and fully replaced by business rules
• CThey have been generally available and production-ready since 2023
• DThey are currently in preview and are not intended for production use✓

Answer: Dataverse Functions, formerly known as instant low-code plug-ins, are currently in preview and are not intended for production use, even though they let makers define reusable, parameterised Power Fx logic that runs on the server. They have not been generally available since 2023, since the source material describes them as a preview capability. They also have not been retired in favour of business rules, which remain a separate, simpler no-code mechanism, and no professional developer licence requirement is described for using them.