Courseiva

CCNA Dataverse Foundations Questions

16 of 91 questions · Page 2/2 · Dataverse Foundations topic · Answers revealed

76
MCQhard

A user has 'User' level access to a table. They create a record. Who is the owner of the record?

A.The Business Unit Manager
B.The record has no owner
C.The user who created the record
D.The System Administrator
AnswerC

Record ownership defaults to the creating user, regardless of their table-level access. Because the user holds only User access, they cannot assign ownership to another user or team; that requires at least the same User access plus share privileges on the record. Creation therefore sets the creator as owner, satisfying the stem's constraint.

Why this answer

In Dataverse, when a user with at least User-level access creates a record, that user is automatically set as the record's owner. Ownership is a core security concept in Dataverse that determines who can access and manage the record, and it is assigned at creation time to the creating user unless explicitly reassigned (e.g., to a team or another user).

Exam trap

AB-410 often tests the assumption that records default to a manager or admin owner, when in fact Dataverse always assigns ownership to the creating user unless explicitly reassigned.

How to eliminate wrong answers

Option A is wrong because the Business Unit Manager is not automatically assigned ownership of records created by users; ownership defaults to the creator, not to a manager. Option B is wrong because every Dataverse record must have an owner — ownership is mandatory and drives row-level security. Option D is wrong because the System Administrator only owns records if they personally create them or if ownership is explicitly reassigned; it is not the default owner for user-created records.

77
MCQmedium

A developer needs to create a relationship between two Dataverse tables: 'Project' and 'Task'. A project can have many tasks, but each task belongs to exactly one project. The developer also wants to ensure that when a project is deleted, all related tasks are automatically deleted. Which type of relationship and configuration should they use?

A.One-to-many relationship with cascade delete set to 'Remove Link'.
B.One-to-many relationship with cascade delete set to 'Restrict'.
C.Many-to-many relationship with cascade delete enabled.
D.One-to-many relationship with cascade delete configured to 'Cascade All'.
AnswerD

A one-to-many relationship allows a single project to be associated with many tasks, and each task to be associated with one project. Configuring cascade delete to 'Cascade All' ensures that when a project is deleted, all related task records are also deleted automatically. This matches the requirement.

Why this answer

The scenario describes a classic one-to-many relationship: one project has many tasks, and each task belongs to one project. To automatically delete tasks when a project is deleted, the cascade delete behavior must be set to 'Cascade All'. This ensures referential integrity and matches the requirement.

Other cascade options like 'Remove Link' or 'Restrict' do not delete the child records.

Exam trap

The trap here is selecting 'Remove Link' thinking it deletes the records, but it only removes the association, leaving orphaned tasks.

78
MCQmedium

You need to create a field that automatically calculates the total revenue of a customer based on related invoices. Which field type should you use?

A.Lookup field
B.Calculated field
C.Rollup field
D.Formula column
AnswerC

A rollup field aggregates values from related child records, so it can sum invoice amounts linked to a customer and display the total automatically. It recalculates as related invoices change, satisfying the stem's requirement for an automatically calculated total revenue value.

Why this answer

A Rollup field aggregates values from related records in a one-to-many relationship — exactly the scenario described, where total revenue is summed from related invoices. Rollup fields support SUM, COUNT, MIN, MAX, and AVG, and they can also apply filters to the related records. This makes them the correct choice for computing a parent record's value from its children.

Exam trap

AB-410 often tests the confusion between Calculated fields (same-record formulas) and Rollup fields (cross-record aggregation) — candidates pick Calculated because it sounds like it 'calculates totals', but only Rollup aggregates related records.

How to eliminate wrong answers

Option A is wrong because a Lookup field simply creates a reference (foreign key) to a single record in another table; it stores a pointer, not an aggregated value. Option B is wrong because a Calculated field computes a value using columns on the same record (and sometimes related records via rollup-like syntax in some platforms), but in Dataverse the classic Calculated field cannot aggregate across a one-to-many relationship — that is precisely the job of a Rollup field. Option D is wrong because 'Formula column' is not a native Dataverse field type; it is terminology from Power Apps formulas or SharePoint, and does not perform cross-record aggregation in Dataverse.

79
MCQeasy

You are a Power Platform developer. You need to create a new custom table in Dataverse to store product information. The table must have a column that can store a monetary value and another column that can store a yes/no choice. Which column data types should you use?

A.Floating Point Number for monetary value and Yes/No for yes/no choice.
B.Currency for monetary value and Two Options for yes/no choice.
C.Money for monetary value and Boolean for yes/no choice.
D.Decimal Number for monetary value and Choice for yes/no choice.
AnswerB

The Currency data type is designed to store monetary values and supports currency symbols and precision. The Two Options data type (also known as Boolean) stores a yes/no choice. These are the correct data types for the specified requirements. Using them ensures proper formatting, calculations, and user interface controls.

Why this answer

The Currency data type is specifically designed for monetary values, providing currency formatting and precision. The Two Options data type stores a yes/no choice. These are the standard Dataverse data types for these requirements.

Other options either use incorrect type names or less appropriate types that do not provide the necessary functionality.

Exam trap

The trap here is using common programming terms like Boolean or Money instead of the exact Dataverse data type names, which can lead to selecting the wrong type in the maker portal.

80
MCQeasy

What is the maximum number of environments a single tenant can create?

A.Dependent on licensing
B.10
C.Fixed at 50
D.Unlimited
AnswerA

Environment limits in a tenant are governed by the assigned licence SKUs and capacity add-ons, not a fixed platform ceiling. The maximum therefore varies with the organisation's licensing, making it dependent on licensing rather than a constant number.

Why this answer

The maximum number of environments a tenant can create in Power Platform is not a fixed number — it depends on the licensing model, specifically the number of licenses purchased and the type of licenses (e.g., per-user vs. per-app, and whether capacity add-ons are present). Microsoft documents environment limits in terms of a base allocation plus additional environments per license, so the correct answer is that it is dependent on licensing.

Exam trap

AB-410 often tests the misconception that environment limits are a fixed technical constant, when in fact they are licensing-dependent and governed by tenant entitlements and admin policies.

How to eliminate wrong answers

Option B is wrong because 10 is not a universal cap — it may reflect a specific licensing tier's default allocation but is not the general answer. Option C is wrong because 50 is not a fixed maximum; environment limits scale with licensing and can exceed or fall below this depending on the tenant's entitlements. Option D is wrong because environments are not unlimited — Microsoft enforces tenant-level limits tied to licensing to prevent resource abuse and ensure capacity planning.

81
MCQmedium

You have a business requirement to categorize 'Project' records by a 'Status' field. You need to ensure users can only select from a predefined list. Which field type is most appropriate?

A.Whole Number column
B.Text column
C.Lookup column
D.Choice column
AnswerD

A Choice column restricts input to a predefined set of options, so users select only valid Status values rather than typing free text. This enforces consistent categorisation of Project records, which a text or lookup column cannot guarantee.

Why this answer

A Choice column stores a predefined set of options (an option set) and restricts user input to those values, which is exactly what is needed to categorize Project records by a Status field with a fixed list. Choice columns can be local (defined per table) or global (shared across tables), and they support single or multi-select.

Exam trap

AB-410 often tests column type selection, and candidates pick Text or Lookup when the requirement is a fixed list, missing that Choice columns are the only type that enforces a predefined option set.

How to eliminate wrong answers

Option A is wrong because a Whole Number column stores numeric values and does not restrict input to a predefined list. Option B is wrong because a Text column allows free-form entry, which would not enforce the predefined list. Option C is wrong because a Lookup column references records in another table, not a static list of options.

82
MCQeasy

A Power Platform developer is creating a new custom table in Dataverse. They need to store a list of predefined options that users can select from, such as 'High', 'Medium', or 'Low' priority. Which type of column should they use?

A.Text
B.Currency
C.Lookup
D.Choice
AnswerD

A Choice column (also known as Option Set) allows users to select from a predefined list of values. It can be a local choice specific to the table or a global choice shared across tables. This is ideal for storing priority levels like High, Medium, Low, as it restricts input to valid options and ensures data consistency.

Why this answer

A Choice column is designed to present a fixed list of options for users to select. It ensures data integrity by restricting input to the defined values. For a priority field with High, Medium, and Low, a Choice column is the correct and most efficient solution.

Exam trap

The trap here is considering a Lookup when a simple Choice column would suffice; Lookups are for relationships to other tables, not for static lists.

83
MCQhard

A developer is building a model-driven app that must display a list of active contacts related to an account, with the ability to quickly filter and sort by multiple columns. The developer needs to add this to the account main form. Which control should be used?

A.Subgrid
B.Editable grid
C.Quick view form
D.Timeline control
AnswerA

A subgrid on a form displays a list of related records from a table, such as contacts related to an account. It provides built-in filtering, sorting, and view selection. This directly meets the need to show active contacts with quick filter and sort capabilities without adding unnecessary editing features.

Why this answer

The requirement is to display a list of related contacts with filtering and sorting. A subgrid is the standard form component for showing related records in a tabular format, and it supports multiple views and sorting. Timeline and quick view forms are for activities and single records respectively, while editable grid is for inline editing.

Exam trap

The trap here is choosing editable grid because it sounds more powerful, but the scenario does not require editing, and subgrid already provides filtering and sorting.

84
MCQmedium

You want to automate the process of sending an email whenever a specific field value changes. What is the best way to achieve this?

A.Business Rule
B.Plugin
C.Workflow
D.Power Automate flow
AnswerD

A Power Automate flow triggers on the Dataverse change event for the specified column, then dispatches the email action. This satisfies the requirement to automate sending an email whenever a specific field value changes, without custom plug-in code.

Why this answer

Power Automate flows are the best tool for automating an email notification triggered by a field value change in Dataverse because they provide a no-code/low-code designer with a native Dataverse trigger ('When a row is added, modified, or deleted') and built-in email actions (Outlook, Office 365 Outlook). This makes the solution maintainable by business users and avoids custom code deployment.

Exam trap

AB-410 often tests the distinction between declarative automation tools (Power Automate, workflows) and code-based extensibility (plugins), so candidates who default to 'developer tools are always better' pick Plugin when the question asks for the best low-code solution.

How to eliminate wrong answers

Option A is wrong because Business Rules in Dataverse are designed to enforce logic at the form/entity level (show/hide fields, set values, validate) and cannot send emails or call external services. Option B is wrong because a Plugin is server-side custom code (C#) that requires a developer, a compiled assembly, and registration in the Plugin Registration Tool — it can send emails but is overkill and harder to maintain for a simple notification. Option C is wrong because classic Workflows (background workflows) can send emails but are a legacy feature being deprecated in favor of Power Automate, and they lack the modern connector ecosystem and cloud-based scalability.

85
MCQhard

A user reports they cannot see a custom table in their app, even though the table is part of the solution. What is the most likely cause?

A.The user is missing Read privileges in their security role
B.The site map has not been updated
C.The table is set to Private
D.The table is not in the default solution
AnswerA

Table visibility depends on the security role's Read privilege at table level; solution membership alone grants nothing. Without Read on the custom table, the user cannot see it in the app, making missing privileges the likely cause.

Why this answer

In Microsoft Power Platform, a user's ability to see a custom table in a model-driven app is governed by their security role. Even if the table is included in the app's components, the user must have at least Read privilege on that table to view it. Without Read access, the table will not appear in the app's navigation or be accessible, leading to the reported issue.

Therefore, missing Read privileges is the most likely cause.

Exam trap

AB-410 often tests the distinction between app component inclusion and security role privileges, causing candidates to overlook that missing Read privileges is the most common reason a user cannot see a table.

How to eliminate wrong answers

Option B is wrong because the site map controls the navigation structure of the app, not the visibility of tables based on security; if the site map were missing the table, it would affect all users, not just one. Option C is wrong because table ownership type (e.g., Private) affects record-level access, not the ability to see the table itself; users with appropriate privileges can still see the table and its records they own. Option D is wrong because the default solution is just a container for components; a table can be in any solution and still be visible in an app as long as it's included and the user has privileges.

86
MCQhard

You are designing a Dataverse solution for a hospital. You need to track patient visits and the medications prescribed during each visit. A visit can have multiple medications, and a medication can be prescribed in multiple visits. You also need to store the dosage and frequency for each medication prescribed in a visit. What is the most appropriate way to model this relationship?

A.Create a many-to-many relationship between Visit and Medication, and add custom columns for dosage and frequency on the Visit table.
B.Create a many-to-many relationship between Visit and Medication, and add custom columns for dosage and frequency on the Medication table.
C.Create a one-to-many relationship from Visit to Medication, and add columns for dosage and frequency on the Visit table.
D.Create a new table called 'Prescription' with a many-to-one relationship to Visit and a many-to-one relationship to Medication. Add columns for dosage and frequency to the Prescription table.
AnswerD

This models a many-to-many relationship with additional attributes using an intersect table. The Prescription table links a Visit and a Medication, and the dosage and frequency columns belong to this specific combination. This accurately represents that a visit can have multiple prescriptions, each with its own dosage and frequency.

Why this answer

The correct solution is to create an intersect table (Prescription) with many-to-one relationships to both Visit and Medication, and place the dosage and frequency columns on that intersect table. This captures the many-to-many relationship and allows unique attributes for each association. The other options either misplace the attributes or use an incorrect relationship type.

Exam trap

The trap here is assuming that a native many-to-many relationship can store additional attributes, but it cannot; you need an intersect table.

87
Multi-Selectmedium

Which TWO actions can be performed in the Power Platform admin center?

Select 2 answers
A.Manage Data Loss Prevention (DLP) policies
B.Design forms
C.Create Business Rules
D.Create new environments
E.Edit records
AnswersA, D

DLP policies are created and edited centrally in the Power Platform admin center, satisfying the requirement for tenant-wide governance of connectors across environments. This administrative surface enforces which connectors can coexist, blocking data movement between business and non-business groups, unlike maker-level or environment-level settings.

Why this answer

Option A is correct because the Power Platform admin center provides a dedicated Data policies (DLP) section where administrators can create, edit, and apply Data Loss Prevention policies that govern which connectors can be used together across environments and tenants. Option D is correct because the admin center includes an Environments page where administrators can create new environments, selecting region, type (Sandbox, Production, Trial, Developer), and assigning a Dataverse database if needed. Options B and C are incorrect because designing forms and creating business rules are authoring tasks performed in Power Apps (model-driven or canvas app designer) or Dynamics 365 customization tools, not in the admin center.

Option E is incorrect because editing records is a data-entry operation done in model-driven apps, canvas apps, or Dataverse tables, not an administrative function of the Power Platform admin center.

Exam trap

AB-410 often tests the boundary between admin-center capabilities and maker-studio capabilities, so candidates confuse governance actions (DLP, environment creation) with authoring actions (forms, business rules, record edits).

88
MCQmedium

You are building a model-driven app for a sales team. The app uses a Dataverse table named Opportunity. You need to ensure that when a user opens an Opportunity record, they see a read-only list of related Contacts that are associated with that Opportunity. The list should appear on the main form and allow users to open a Contact record. What should you add to the form?

A.A quick view form.
B.A lookup column.
C.A subgrid.
D.A timeline control.
AnswerC

A subgrid is a form component that displays a list of related records in a grid. It can be configured to show records from a related table, such as Contacts related to an Opportunity. The subgrid is read-only by default but can allow opening records. It appears directly on the main form and supports sorting, filtering, and viewing multiple records, which matches the requirement.

Why this answer

A subgrid is the correct form component to display a list of related records, such as Contacts associated with an Opportunity. It shows multiple records in a grid, supports read-only mode, and allows users to open individual records. Quick view forms show a single related record, timeline controls show activities, and lookup columns allow selecting a single record, so none of those meet the requirement for a read-only list.

Exam trap

The trap here is confusing a subgrid with a quick view form; a subgrid shows a list, while a quick view form shows a single related record.

89
MCQmedium

You are designing a Dataverse solution for a real estate agency. The agency needs to track properties and the agents who list them. Each property can have only one listing agent, but an agent can list many properties. You create a table named Property and a table named Agent. You need to establish the relationship so that when an agent is deleted, their listed properties remain but the Listing Agent column is cleared. Which relationship type and behavior should you configure?

A.One-to-many relationship with Referential, Remove Link behavior on the Agent side.
B.One-to-many relationship with Referential, Restrict Delete behavior on the Agent side.
C.One-to-many relationship with Parental behavior on the Agent side.
D.Many-to-many relationship with Referential, Restrict Delete behavior.
AnswerA

A one-to-many relationship from Agent to Property matches the business rule that one agent lists many properties. Referential, Remove Link sets the Listing Agent lookup on related Property records to null when the Agent is deleted, preserving the Property records. This is exactly the required deletion behavior.

Why this answer

The scenario requires a one-to-many relationship where deleting the parent (Agent) does not delete the child (Property) but clears the lookup. Referential, Remove Link achieves this by setting the referencing column to null. Other behaviors either restrict deletion or cascade delete, neither of which meets the business requirement.

Exam trap

The trap here is assuming that any one-to-many relationship with Referential behavior automatically clears the lookup; only Referential, Remove Link does that, while Referential, Restrict Delete blocks deletion.

90
MCQhard

You are designing a Dataverse table to store customer orders. You need to ensure that each order is automatically assigned a unique, sequential order number that users can easily reference. The number should be generated when a new record is created and should not be editable by users. What should you use?

A.A calculated column that concatenates the creation date and a random number
B.A text column with a business rule that sets its value
C.An autonumber column
D.A rollup column that counts existing orders
AnswerC

An autonumber column automatically generates a unique, sequential number when a new record is created. It is read-only for users, ensuring the number cannot be edited. Autonumber columns support formats like 'ORD-{SEQNUM:5}' and are ideal for order numbers that need to be easily referenced. This directly meets the requirement.

Why this answer

An autonumber column is designed to automatically generate unique, sequential numbers for new records. It is read-only, ensuring users cannot edit the value. This makes it the perfect choice for order numbers that need to be unique and easily referenced.

Other column types cannot provide sequential numbering without complex workarounds and may not guarantee uniqueness.

Exam trap

The trap here is assuming that calculated or rollup columns can generate sequential numbers, but they lack the ability to maintain a running counter and ensure uniqueness.

91
Multi-Selecthard

Which THREE features are part of Dataverse security?

Select 3 answers
A.Security Roles
B.Form-level scripting
C.Field Security Profiles
D.App-level branding
E.Business Units
AnswersA, C, E

Security roles define the privilege matrix controlling which users can create, read, update, and delete records within Dataverse environments and tables. They are a core component of Dataverse's role-based access model, alongside business units and teams.

Why this answer

Security Roles (A) are a core Dataverse access-control mechanism: they bundle table privileges (Create, Read, Write, Delete, Append, Append To, Assign, Share) at user/team level and are scoped by Business Unit, so they directly govern who can do what in Dataverse. Field Security Profiles (C) are also part of Dataverse security: they are applied to specific columns marked as secured, and combined with a user's security role they restrict read/create/update access to sensitive field values. Business Units (E) form the hierarchical ownership and scoping structure of Dataverse, defining the boundaries (User, Business Unit, Parent: Child Business Unit, Organization) within which security roles grant privileges.

The remaining options are not security features: Form-level scripting (B) is client-side model-driven app behavior implemented with JavaScript, and App-level branding (D) is a model-driven app customization for colors, icons, and theming, neither of which controls Dataverse data access.

Exam trap

AB-410 often tests the misconception that UI-level customization features (form scripts, branding) are part of the security model, when Dataverse security is strictly about roles, field profiles, and business units.

← PreviousPage 2 of 2 · 91 questions total

Ready to test yourself?

Try a timed practice session using only Dataverse Foundations questions.