📘 Free AB-410 Sample Questions
This is a case study. Case studies are not timed separately from other exam sections. You can use as much exam
time as you would like to complete each case study. However, there might be additional case studies or other
exam sections. Manage your time to ensure that you can complete all the exam sections in the time provided. Pay
attention to the Exam Progress at the top of the screen so you have sufficient time to complete any exam sections
that follow this case study.
To answer the case study questions, you will need to reference information that is provided in the case. Case
studies and associated questions might contain exhibits or other resources that provide more information about
the scenario described in the case. Information provided in an individual question does not apply to the other
questions in the case study.
A Review Screen will appear at the end of this case study. From the Review Screen, you can review and change
your answers before you move to the next exam section. After you leave this case study, you will NOT be able to
return to it.
To start the case study -
To display the first question in this case study, select the “Next” button. To the left of the question, a menu
provides links to information such as business requirements, the existing environment, and problem statements.
Please read through all this information before answering any questions. When you are ready to answer a question,
select the “Question” button to return to the question.
Background -
Contoso Ltd. is a global renewable energy provider that operates wind farms and solar installations. The company
is modernizing its maintenance and operations platform. The company plans to implement a Microsoft Power
Platform solution for the operations team. The implementation will include Microsoft Dataverse, a model-driven
app, and Power Automate cloud flows.
The company is building and testing a new model-driven app named Operations. The solution will support
operations managers, regional coordinators, and field technicians. The app must integrate with an external cloud
based system that manages onboarding of field technicians.
Contoso Ltd. plans to improve data quality and enforce consistent business logic across the app and automation
processes.
Technical environment -
Contoso Ltd. has an Identity and Access Management (IDAM) department that manages security. The company has
one Power Platform environment named Production, where all building and configuration take place. Auditing is
disabled.
The Production environment has the following security configurations:
IDAM has a Microsoft Entra security group named Contoso Ltd. QA. This security group will assign all members a
Power Apps license.
IDAM created a Quality Assurance security role that grants read and write access to all custom tables.
IDAM also created a team named Testers in Dataverse, of a Microsoft Entra group team type. The team is
configured for the Contoso Ltd. QA security group. The Testers team is assigned the Quality Assurance security
role.
Microsoft 365 environment -
All Contoso Ltd. managers are included in a Microsoft 365 group named Managers. The group is NOT enabled for
email.
The company shares a SharePoint list with a key customer: Alpine Ski House. Alpine Ski House staff members can
add new maintenance requests, which are then checked and marked as reviewed by Contoso Ltd.
Current issue:
A new QA tester joins Contoso Ltd. The IDAM department adds the new tester to the Contoso Ltd. QA security
group. However, the new tester is not listed in the Testers team as a member.
Other applications:
A separate software-as a-service (SaaS) solution named TechCheck manages technician onboarding. The
TechCheck solution is set up as follows:
TechCheck assigns a unique number named Ref to all technicians.
Users cannot make changes to the TechCheck data model.
Users cannot use the same TechCheck ref on more than one Technician row.
Automation requirements -
Contoso plans to use Power Automate to develop a Maintenance Request Approval flow. The flow must meet the
following requirements:
Create a Maintenance Request row in Dataverse when either of the following occurs:
An item is added to the SharePoint list by the customer with the Priority property set to High.
Any item is checked and marked as reviewed by a Contoso Ltd. representative.
Seek maintenance request approvals from managers through both email and a Microsoft Teams message after
they have been reviewed:
Requests require approval from all managers.
If one manager rejects the request, approval must not be granted.
The result of the approval request must be sent to the initial reviewer in an email. The subject line must set the
response as either Approve or Reject.
Contoso Ltd. requires the following table logic:
If a user tries to enter a price greater than the cost on a new Asset row, the row must display an inline error
message.
If a user tries to save changes to a Technician row where the TechCheck ref column is empty, the action must be
prevented and a message explaining the action must be displayed.
Any updates made to Technician profiles in TechCheck must be mirrored in Dataverse by using a custom
integration. The developers building the integration require an index for performant searches on the Technician
table.
Data model and app design -
Contoso Ltd. plans to use Dataverse as its central data platform. Log storage must be minimized.
Tables -
The following tables are required for data modeling and the app design:
Assets: Stores information about solar panels and wind turbines
Maintenance Requests: Tracks issues and maintenance activities. The table must include the following columns:
Request ID (auto-number)
External Request Code (text)
Assigned -
Technician (lookup to Technicians)
Report (lookup to Maintenance Reports)
Technician updated (Yes/No)
Maintenance Reports: Tracks the results of maintenance reports
Technicians: Stores technician assignment data. The table must include the following columns:
Full Name (Text)
Mobile phone number (Text)
Email (Text)
Seniority (Choice)
TechCheck ref (Text)
Data modeling -
The data model must provide the following functionality:
Maintenance Requests must:
be uniquely identifiable across systems.
have two inactive statuses, Cancelled and Duplicate.
If a new option is added to an existing set of options, it must be made available automatically for selection on all
columns that use the set.
A new column named Priority must be added to multiple tables. Users must be able to select only one option from
the following set per row:
Low -
Medium -
High -
Critical -
Changes to the Technician column on Maintenance Requests must be tracked for compliance purposes. Rows
must include the names of previous and current technicians and the time of the change.
Relationship requirements -
One asset can be related to many maintenance requests. A maintenance request can have many assets.
A maintenance request can have only zero or one maintenance report.
Only one Technician can be related to a Maintenance Request at a time.
When a Maintenance Request is deleted, any Maintenance Reports associated with it must also be deleted, but
this action should be prevented if there is value in the Technician lookup.
When a Maintenance Request is assigned to a different owner, the Maintenance Report associated with it must be
reassigned to the new owner as well, but the associated Technician should stay with the current owner.
App design -
The Technicians table contains the following public views:
Senior Technicians -
Junior Technicians -
The Senior Technician view must be available through the table list view selector to a set of specific users only.
A tester creates a personal view named Hot Assets on the Assets table. The tester recognizes that the view is
useful for the entire testing team. The view must be made accessible to the team.
You need to add the Priority column to the Maintenance Request table.
Which column type should you use?
A
local choice
B
global choice
C
status reason
D
formula
Correct Answer:
B. global choice
Explanation:
B. global choice.
This type lets you create a dropdown list centrally and reuse it across multiple tables. Since "Priority" is a
standard data field needed across different maintenance tracking elements, a global choice ensures
consistent options and simplifies updates.
Why the other answer are incorrect:
another table needs the exact same priority options.
A. local choice: This type restricts the dropdown list to a single table. It cannot be easily shared or reused if
C. status reason: This column type is tied specifically to the state of a record (like Active/Inactive). It manages
state transitions rather than general categorization like priority.
D. formula: This column calculates values automatically based on other fields. It does not allow users to
manually select a choice from a predefined list.
DRAG DROP -
This is a case study. Case studies are not timed separately from other exam sections. You can use as much exam
time as you would like to complete each case study. However, there might be additional case studies or other
exam sections. Manage your time to ensure that you can complete all the exam sections in the time provided. Pay
attention to the Exam Progress at the top of the screen so you have sufficient time to complete any exam sections
that follow this case study.
To answer the case study questions, you will need to reference information that is provided in the case. Case
studies and associated questions might contain exhibits or other resources that provide more information about
the scenario described in the case. Information provided in an individual question does not apply to the other
questions in the case study.
A Review Screen will appear at the end of this case study. From the Review Screen, you can review and change
your answers before you move to the next exam section. After you leave this case study, you will NOT be able to
return to it.
To start the case study -
To display the first question in this case study, select the “Next” button. To the left of the question, a menu
select the “Question” button to return to the question.
Background -
app, and Power Automate cloud flows.
processes.
Technical environment -
provides links to information such as business requirements, the existing environment, and problem statements.
Please read through all this information before answering any questions. When you are ready to answer a question,
Contoso Ltd. is a global renewable energy provider that operates wind farms and solar installations. The company
is modernizing its maintenance and operations platform. The company plans to implement a Microsoft Power
Platform solution for the operations team. The implementation will include Microsoft Dataverse, a model-driven
The company is building and testing a new model-driven app named Operations. The solution will support
operations managers, regional coordinators, and field technicians. The app must integrate with an external cloud
based system that manages onboarding of field technicians.
Contoso Ltd. plans to improve data quality and enforce consistent business logic across the app and automation
Contoso Ltd. has an Identity and Access Management (IDAM) department that manages security. The company has
one Power Platform environment named Production, where all building and configuration take place. Auditing is
disabled.
The Production environment has the following security configurations:
IDAM has a Microsoft Entra security group named Contoso Ltd. QA. This security group will assign all members a
Power Apps license.
IDAM created a Quality Assurance security role that grants read and write access to all custom tables.
IDAM also created a team named Testers in Dataverse, of a Microsoft Entra group team type. The team is
configured for the Contoso Ltd. QA security group. The Testers team is assigned the Quality Assurance security
role.
Microsoft 365 environment -
All Contoso Ltd. managers are included in a Microsoft 365 group named Managers. The group is NOT enabled for
email.
The company shares a SharePoint list with a key customer: Alpine Ski House. Alpine Ski House staff members can
add new maintenance requests, which are then checked and marked as reviewed by Contoso Ltd.
Current issue:
A new QA tester joins Contoso Ltd. The IDAM department adds the new tester to the Contoso Ltd. QA security
group. However, the new tester is not listed in the Testers team as a member.
Other applications:
A separate software-as a-service (SaaS) solution named TechCheck manages technician onboarding. The
TechCheck solution is set up as follows:
TechCheck assigns a unique number named Ref to all technicians.
Users cannot make changes to the TechCheck data model.
Users cannot use the same TechCheck ref on more than one Technician row.
Automation requirements -
Contoso plans to use Power Automate to develop a Maintenance Request Approval flow. The flow must meet the
following requirements:
Create a Maintenance Request row in Dataverse when either of the following occurs:
An item is added to the SharePoint list by the customer with the Priority property set to High.
Any item is checked and marked as reviewed by a Contoso Ltd. representative.
Seek maintenance request approvals from managers through both email and a Microsoft Teams message after
they have been reviewed:
Requests require approval from all managers.
If one manager rejects the request, approval must not be granted.
The result of the approval request must be sent to the initial reviewer in an email. The subject line must set the
response as either Approve or Reject.
Contoso Ltd. requires the following table logic:
If a user tries to enter a price greater than the cost on a new Asset row, the row must display an inline error
message.
If a user tries to save changes to a Technician row where the TechCheck ref column is empty, the action must be
prevented and a message explaining the action must be displayed.
Any updates made to Technician profiles in TechCheck must be mirrored in Dataverse by using a custom
integration. The developers building the integration require an index for performant searches on the Technician
table.
Data model and app design -
Contoso Ltd. plans to use Dataverse as its central data platform. Log storage must be minimized.
Tables -
The following tables are required for data modeling and the app design:
Assets: Stores information about solar panels and wind turbines
Maintenance Requests: Tracks issues and maintenance activities. The table must include the following columns:
Request ID (auto-number)
External Request Code (text)
Assigned -
Technician (lookup to Technicians)
Report (lookup to Maintenance Reports)
Technician updated (Yes/No)
Maintenance Reports: Tracks the results of maintenance reports
Technicians: Stores technician assignment data. The table must include the following columns:
Full Name (Text)
Mobile phone number (Text)
Email (Text)
Seniority (Choice)
TechCheck ref (Text)
Data modeling -
The data model must provide the following functionality:
Maintenance Requests must:
be uniquely identifiable across systems.
have two inactive statuses, Cancelled and Duplicate.
If a new option is added to an existing set of options, it must be made available automatically for selection on all
columns that use the set.
A new column named Priority must be added to multiple tables. Users must be able to select only one option from
the following set per row:
Low -
Medium -
High -
Critical -
Changes to the Technician column on Maintenance Requests must be tracked for compliance purposes. Rows
must include the names of previous and current technicians and the time of the change.
Relationship requirements -
One asset can be related to many maintenance requests. A maintenance request can have many assets.
A maintenance request can have only zero or one maintenance report.
Only one Technician can be related to a Maintenance Request at a time.
When a Maintenance Request is deleted, any Maintenance Reports associated with it must also be deleted, but
this action should be prevented if there is value in the Technician lookup.
When a Maintenance Request is assigned to a different owner, the Maintenance Report associated with it must be
reassigned to the new owner as well, but the associated Technician should stay with the current owner.
App design -
The Technicians table contains the following public views:
Senior Technicians -
Junior Technicians -
The Senior Technician view must be available through the table list view selector to a set of specific users only.
A tester creates a personal view named Hot Assets on the Assets table. The tester recognizes that the view is
useful for the entire testing team. The view must be made accessible to the team.
You need to configure the Maintenance Request relationships to the other tables.
Which type of relationship behavior should you set? To answer, move the appropriate behavior types to the correct
tables. You may use each behavior type 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.
A
Correct Answer:
A.
Explanation:
Maintenance Report: Parental
Technician: Referential, Restrict Delete
Maintenance Report: A parental relationship ensures that operations performed on the primary record (such
as assigning or deleting a main record) automatically cascade to all associated maintenance reports.
Technician: A referential, restrict delete behavior prevents a technician's record from being deleted if they
are currently linked to any active records, protecting data integrity.
Incorrect answers:
Referential, Remove Link: Incorrect because if a master record is removed, it clears the lookup field, masking
which technician was originally associated with the work and breaking accountability.
This is a case study. Case studies are not timed separately from other exam sections. You can use as much exam
time as you would like to complete each case study. However, there might be additional case studies or other
exam sections. Manage your time to ensure that you can complete all the exam sections in the time provided. Pay
attention to the Exam Progress at the top of the screen so you have sufficient time to complete any exam sections
that follow this case study.
To answer the case study questions, you will need to reference information that is provided in the case. Case
studies and associated questions might contain exhibits or other resources that provide more information about
the scenario described in the case. Information provided in an individual question does not apply to the other
questions in the case study.
A Review Screen will appear at the end of this case study. From the Review Screen, you can review and change
your answers before you move to the next exam section. After you leave this case study, you will NOT be able to
return to it.
To start the case study -
To display the first question in this case study, select the “Next” button. To the left of the question, a menu
provides links to information such as business requirements, the existing environment, and problem statements.
Please read through all this information before answering any questions. When you are ready to answer a question,
select the “Question” button to return to the question.
Background -
Contoso Ltd. is a global renewable energy provider that operates wind farms and solar installations. The company
is modernizing its maintenance and operations platform. The company plans to implement a Microsoft Power
Platform solution for the operations team. The implementation will include Microsoft Dataverse, a model-driven
app, and Power Automate cloud flows.
based system that manages onboarding of field technicians.
processes.
Technical environment -
The Production environment has the following security configurations:
Current issue:
The company is building and testing a new model-driven app named Operations. The solution will support
operations managers, regional coordinators, and field technicians. The app must integrate with an external cloud
Contoso Ltd. plans to improve data quality and enforce consistent business logic across the app and automation
Contoso Ltd. has an Identity and Access Management (IDAM) department that manages security. The company has
one Power Platform environment named Production, where all building and configuration take place. Auditing is
disabled.
IDAM has a Microsoft Entra security group named Contoso Ltd. QA. This security group will assign all members a
Power Apps license.
IDAM created a Quality Assurance security role that grants read and write access to all custom tables.
IDAM also created a team named Testers in Dataverse, of a Microsoft Entra group team type. The team is
configured for the Contoso Ltd. QA security group. The Testers team is assigned the Quality Assurance security
role.
Microsoft 365 environment -
All Contoso Ltd. managers are included in a Microsoft 365 group named Managers. The group is NOT enabled for
email.
The company shares a SharePoint list with a key customer: Alpine Ski House. Alpine Ski House staff members can
add new maintenance requests, which are then checked and marked as reviewed by Contoso Ltd.
A new QA tester joins Contoso Ltd. The IDAM department adds the new tester to the Contoso Ltd. QA security
group. However, the new tester is not listed in the Testers team as a member.
Other applications:
A separate software-as a-service (SaaS) solution named TechCheck manages technician onboarding. The
TechCheck solution is set up as follows:
TechCheck assigns a unique number named Ref to all technicians.
Users cannot make changes to the TechCheck data model.
Users cannot use the same TechCheck ref on more than one Technician row.
Automation requirements -
Contoso plans to use Power Automate to develop a Maintenance Request Approval flow. The flow must meet the
following requirements:
Create a Maintenance Request row in Dataverse when either of the following occurs:
An item is added to the SharePoint list by the customer with the Priority property set to High.
Any item is checked and marked as reviewed by a Contoso Ltd. representative.
Seek maintenance request approvals from managers through both email and a Microsoft Teams message after
they have been reviewed:
Requests require approval from all managers.
If one manager rejects the request, approval must not be granted.
The result of the approval request must be sent to the initial reviewer in an email. The subject line must set the
response as either Approve or Reject.
Contoso Ltd. requires the following table logic:
If a user tries to enter a price greater than the cost on a new Asset row, the row must display an inline error
message.
If a user tries to save changes to a Technician row where the TechCheck ref column is empty, the action must be
prevented and a message explaining the action must be displayed.
Any updates made to Technician profiles in TechCheck must be mirrored in Dataverse by using a custom
integration. The developers building the integration require an index for performant searches on the Technician
table.
Data model and app design -
Contoso Ltd. plans to use Dataverse as its central data platform. Log storage must be minimized.
Tables -
The following tables are required for data modeling and the app design:
Assets: Stores information about solar panels and wind turbines
Maintenance Requests: Tracks issues and maintenance activities. The table must include the following columns:
Request ID (auto-number)
External Request Code (text)
Assigned -
Technician (lookup to Technicians)
Report (lookup to Maintenance Reports)
Technician updated (Yes/No)
Maintenance Reports: Tracks the results of maintenance reports
Technicians: Stores technician assignment data. The table must include the following columns:
Full Name (Text)
Mobile phone number (Text)
Email (Text)
Seniority (Choice)
TechCheck ref (Text)
Data modeling -
The data model must provide the following functionality:
Maintenance Requests must:
be uniquely identifiable across systems.
have two inactive statuses, Cancelled and Duplicate.
If a new option is added to an existing set of options, it must be made available automatically for selection on all
columns that use the set.
A new column named Priority must be added to multiple tables. Users must be able to select only one option from
the following set per row:
Low -
Medium -
High -
Critical -
Changes to the Technician column on Maintenance Requests must be tracked for compliance purposes. Rows
must include the names of previous and current technicians and the time of the change.
Relationship requirements -
One asset can be related to many maintenance requests. A maintenance request can have many assets.
A maintenance request can have only zero or one maintenance report.
Only one Technician can be related to a Maintenance Request at a time.
When a Maintenance Request is deleted, any Maintenance Reports associated with it must also be deleted, but
this action should be prevented if there is value in the Technician lookup.
When a Maintenance Request is assigned to a different owner, the Maintenance Report associated with it must be
reassigned to the new owner as well, but the associated Technician should stay with the current owner.
App design -
The Technicians table contains the following public views:
Senior Technicians -
Junior Technicians -
The Senior Technician view must be available through the table list view selector to a set of specific users only.
A tester creates a personal view named Hot Assets on the Assets table. The tester recognizes that the view is
useful for the entire testing team. The view must be made accessible to the team.
You need to configure the access requirements to the views.
Which configurations should you use? To answer, move the appropriate configurations to the correct views. 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.
A
Correct Answer:
A.
Explanation:
Senior technicians: Security roles
Hot Assets: Sharing
Why this is correct:
Senior technicians: System views can be restricted using Security roles via model-driven app settings to
ensure they are available through the view selector only to a specific set of users.
Hot Assets: A tester's personal view is made accessible to the entire testing team using the build-in Sharing
functionality for personal views.
Incorrect Options:
Owner teams and Business units manage data record ownership and security access, but they cannot directly
filter or restrict individual system or personal view availability within the table list selector.
This is a case study. Case studies are not timed separately from other exam sections. You can use as much exam
time as you would like to complete each case study. However, there might be additional case studies or other
exam sections. Manage your time to ensure that you can complete all the exam sections in the time provided. Pay
attention to the Exam Progress at the top of the screen so you have sufficient time to complete any exam sections
that follow this case study.
To answer the case study questions, you will need to reference information that is provided in the case. Case
studies and associated questions might contain exhibits or other resources that provide more information about
the scenario described in the case. Information provided in an individual question does not apply to the other
questions in the case study.
A Review Screen will appear at the end of this case study. From the Review Screen, you can review and change
your answers before you move to the next exam section. After you leave this case study, you will NOT be able to
return to it.
To start the case study -
To display the first question in this case study, select the “Next” button. To the left of the question, a menu
provides links to information such as business requirements, the existing environment, and problem statements.
Please read through all this information before answering any questions. When you are ready to answer a question,
select the “Question” button to return to the question.
Background -
Contoso Ltd. is a global renewable energy provider that operates wind farms and solar installations. The company
is modernizing its maintenance and operations platform. The company plans to implement a Microsoft Power
Platform solution for the operations team. The implementation will include Microsoft Dataverse, a model-driven
app, and Power Automate cloud flows.
The company is building and testing a new model-driven app named Operations. The solution will support
operations managers, regional coordinators, and field technicians. The app must integrate with an external cloud
based system that manages onboarding of field technicians.
processes.
Technical environment -
The Production environment has the following security configurations:
Current issue:
Contoso Ltd. plans to improve data quality and enforce consistent business logic across the app and automation
Contoso Ltd. has an Identity and Access Management (IDAM) department that manages security. The company has
one Power Platform environment named Production, where all building and configuration take place. Auditing is
disabled.
IDAM has a Microsoft Entra security group named Contoso Ltd. QA. This security group will assign all members a
Power Apps license.
IDAM created a Quality Assurance security role that grants read and write access to all custom tables.
IDAM also created a team named Testers in Dataverse, of a Microsoft Entra group team type. The team is
configured for the Contoso Ltd. QA security group. The Testers team is assigned the Quality Assurance security
role.
Microsoft 365 environment -
All Contoso Ltd. managers are included in a Microsoft 365 group named Managers. The group is NOT enabled for
email.
The company shares a SharePoint list with a key customer: Alpine Ski House. Alpine Ski House staff members can
add new maintenance requests, which are then checked and marked as reviewed by Contoso Ltd.
A new QA tester joins Contoso Ltd. The IDAM department adds the new tester to the Contoso Ltd. QA security
group. However, the new tester is not listed in the Testers team as a member.
Other applications:
A separate software-as a-service (SaaS) solution named TechCheck manages technician onboarding. The
TechCheck solution is set up as follows:
TechCheck assigns a unique number named Ref to all technicians.
Users cannot make changes to the TechCheck data model.
Users cannot use the same TechCheck ref on more than one Technician row.
Automation requirements -
Contoso plans to use Power Automate to develop a Maintenance Request Approval flow. The flow must meet the
following requirements:
Create a Maintenance Request row in Dataverse when either of the following occurs:
An item is added to the SharePoint list by the customer with the Priority property set to High.
Any item is checked and marked as reviewed by a Contoso Ltd. representative.
Seek maintenance request approvals from managers through both email and a Microsoft Teams message after
they have been reviewed:
Requests require approval from all managers.
If one manager rejects the request, approval must not be granted.
The result of the approval request must be sent to the initial reviewer in an email. The subject line must set the
response as either Approve or Reject.
Contoso Ltd. requires the following table logic:
If a user tries to enter a price greater than the cost on a new Asset row, the row must display an inline error
message.
If a user tries to save changes to a Technician row where the TechCheck ref column is empty, the action must be
prevented and a message explaining the action must be displayed.
Any updates made to Technician profiles in TechCheck must be mirrored in Dataverse by using a custom
integration. The developers building the integration require an index for performant searches on the Technician
table.
Data model and app design -
Contoso Ltd. plans to use Dataverse as its central data platform. Log storage must be minimized.
Tables -
The following tables are required for data modeling and the app design:
Assets: Stores information about solar panels and wind turbines
Maintenance Requests: Tracks issues and maintenance activities. The table must include the following columns:
Request ID (auto-number)
External Request Code (text)
Assigned -
Technician (lookup to Technicians)
Report (lookup to Maintenance Reports)
Technician updated (Yes/No)
Maintenance Reports: Tracks the results of maintenance reports
Technicians: Stores technician assignment data. The table must include the following columns:
Full Name (Text)
Mobile phone number (Text)
Email (Text)
Seniority (Choice)
TechCheck ref (Text)
Data modeling -
The data model must provide the following functionality:
Maintenance Requests must:
be uniquely identifiable across systems.
have two inactive statuses, Cancelled and Duplicate.
If a new option is added to an existing set of options, it must be made available automatically for selection on all
columns that use the set.
A new column named Priority must be added to multiple tables. Users must be able to select only one option from
the following set per row:
Low -
Medium -
High -
Critical -
Changes to the Technician column on Maintenance Requests must be tracked for compliance purposes. Rows
must include the names of previous and current technicians and the time of the change.
Relationship requirements -
One asset can be related to many maintenance requests. A maintenance request can have many assets.
A maintenance request can have only zero or one maintenance report.
Only one Technician can be related to a Maintenance Request at a time.
When a Maintenance Request is deleted, any Maintenance Reports associated with it must also be deleted, but
this action should be prevented if there is value in the Technician lookup.
When a Maintenance Request is assigned to a different owner, the Maintenance Report associated with it must be
reassigned to the new owner as well, but the associated Technician should stay with the current owner.
App design -
The Technicians table contains the following public views:
Senior Technicians -
Junior Technicians -
The Senior Technician view must be available through the table list view selector to a set of specific users only.
A tester creates a personal view named Hot Assets on the Assets table. The tester recognizes that the view is
useful for the entire testing team. The view must be made accessible to the team.
You need to define the alternate key for the Technicians table by using the TechCheck ref column.
Which setting should you apply to the TechCheck ref column?
A
Required
B
Searchable
C
Column security
D
Auditing
Correct Answer:
A. Required
Explanation:
A. Required.
To define an alternate key on a Microsoft Dataverse table, any column included in the key definition must be
configured as Required (Business Required). This ensures that the column will never contain null values,
preserving its function as a unique identifier for data tracking and synchronization.
Why the other answer are incorrect:
B. Searchable: This setting only controls whether the column is available in Advanced Find or filters. It has no
impact on data uniqueness or the technical requirements needed to establish a database key index.
C. Column security: This field-level security feature restricts read, update, or create access to specific users.
It does not enforce data integrity or mandatory entry fields required for keys.
D. Auditing: This mechanism tracks historical changes and modifications to a row's data over time. It has no
bearing on row validation or configuring database constraints.
A company uses a model-driven app across multiple departments.
A public view intended only for managers currently exposes sensitive columns and filters to all users.
The view must meet the following requirements:
Restrict access to the specific public view to managers.
Display only context-relevant views for other users.
You need to configure view access.
What should you do?
A
Restrict the view by assigning it to the manager security role.
B
Configure table-level permissions for managers only.
C
Remove the view from the app navigation.
D
D. Set up the quick find view.
Correct Answer:
A. Restrict the view by assigning it to the manager security role.
Explanation:
A. Restrict the view by assigning it to the manager security role.
Power Apps allows administrators to manage access to public views. Assigning the view to the manager
security role ensures it is only visible to managers. Other users will only see the views relevant to their
assigned roles.
Incorrect Answers
B. Configure table-level permissions for managers only.
Table-level permissions (security roles) control access to entire rows of data, not specific UI views. Restricting
the table would completely block non-managers from seeing any data in that table, which prevents them from seeing
their own context-relevant views.
C. Remove the view from the app navigation.
D. Set up the quick find view.
App navigation (the site map) controls links to main tables or dashboards, not individual grid views. Removing
the view here does not stop users from selecting it via the view dropdown menu on the table grid.
The Quick Find view determines which columns are searched when a user utilizes the grid search box. It
cannot restrict view visibility or hide sensitive columns from unauthorized users.
You create a parent entity and a child entity. The parent entity has a 1:N relationship with the child entity.
You need to ensure that when the owner changes on the parent record that all child records are assigned to the
new owner.
You need to configure the relationship behavior type.
What should you use?
A
Referential, Restrict Delete
B
Referential
C
Restrict
D
Parental
Correct Answer:
Explanation:
D. Parental.
The Parental relationship behavior type automatically cascades actions performed on a parent record—such
as changes in ownership, sharing, or deletion—down to all associated child records. Setting the relationship
Why the other answer are incorrect:
behavior to Parental ensures that changing the owner on the parent record triggers an automatic re
assignment of all child records to the new owner.
A. Referential, Restrict Delete: This behavior type keeps the records linked but isolates actions. Setting this
means changing the parent owner has no effect on the child owner; it only stops the parent record from being
deleted if child records exist
B. Referential: In a standard Referential relationship, actions do not cascade. Changing the owner of the
parent record leaves the child record owners completely unchanged, failing the requirement.
C. Restrict: "Restrict" is not a standalone relationship behavior type in Microsoft Dataverse. It is an option
specifically configured for the Delete action (Restrict Delete) to prevent parent deletion when child records
exist.
A company tracks order processing duration using a model-driven app.
The company requires a system that provides the following functionality:
The age of the order, based on the created date, must be displayed on forms and views.
The value must update dynamically when viewed without storing the result.
The value must NOT be stored in the database.
You need to configure the column types.
Which two column types should you use? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
A
Formula
B
Calculated
C
BigInt
D
Prompt
Correct Answer:
A. Formula
Explanation:
A. Formula
B. Calculated.
age of the order updates automatically without storing data in the database.
Why the Options are Correct
Why the Options are Incorrect
Both column types compute values dynamically at runtime when a record is opened or viewed, ensuring the
store data in the SQL database, making them ideal for real-time age calculations.
persist the calculated value in the database.
A. Formula: Dataverse formula columns use Power Fx to calculate values dynamically on-the-fly. They do not
B. Calculated: Calculated columns execute calculations dynamically when a form or view loads. They do not
C. BigInt: This is a static data type used to store extremely large whole numbers. It does not perform dynamic
calculations or update automatically over time.
D. Prompt: This is not a valid Dataverse column type for calculating durations or date differences.
You are designing a data model for a company. The model uses only standard Microsoft Dataverse tables.
You must extend the existing Accounts and Contacts tables to support the following business requirements:
Store an additional classification value on the Accounts table.
Add a field that indicates a customer's engagement tier on the Contacts table.
Create a mechanism to improve lookup performance and ensure uniqueness across selected fields.
You need to modify the tables to support the business requirements.
Which components should you use? To answer, move the appropriate components to the correct requirements. You
may use each component 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.
A
Correct Answer:
A.
Explanation:
Add a classification value to the Accounts table. ? Choice column
Why it's correct: A classification value implies a set of pre-defined options (e.g., "Public," "Private,"
"Subsidiary"). A Choice column provides a dropdown list to store these specific values.
Add a customer engagement tier to the Contacts table. ? Choice column
Why it's correct: Engagement tiers consist of distinct categories (e.g., "Tier 1," "Tier 2," "Tier 3" or "Gold,"
"Silver," "Bronze"). A Choice column is the standard way to capture restricted, fixed list parameters.
Improve lookup performance and enforce uniqueness. ? Alternate key
Why it's correct: Alternate keys create a database index that speeds up query performance and enforces a
strict uniqueness constraint across records, preventing duplicate values in the indexed column.
Incorrect Answers:
Lookup column
Why it's incorrect: A Lookup column creates a 1:N relationship linking the current record to a row in an
entirely different table. It does not store static classification lists, nor does it inherently enforce data
uniqueness.
Customer column
Why it's incorrect: A Customer column is a special polymorphic lookup column in Dataverse that links
explicitly to either an Account or a Contact record. It is not used for classifying rows or establishing
uniqueness parameters.
A company maintains a Power Platform solution that includes prompts, cloud flows, and Dataverse components.
Multiple development teams are responsible for different features within the solution.
The development teams have the following requirements:
Teams must develop and update the same features independently.
Updates must not overwrite changes made by other teams.
Production deployments must remain controlled and predictable.
You need to recommend an ALM approach that supports independent development and controlled deployment in
line with Microsoft best practices.
What should you recommend?
A
Create and maintain separate solutions in a single development environment. Deploy independently as
managed solutions.
B
Make changes in a single solution. Deploy updates directly to production.
C
Create and maintain separate solutions in a separate development environment. Deploy independently as managed solutions.
D
Create unmanaged solutions in production. Merge changes during deployment.
Correct Answer:
C. Create and maintain separate solutions in a separate development environment. Deploy independently as managed solutions.
Explanation:
C. Create and maintain separate solutions in a separate development environment. Deploy independently
as managed solutions.
Microsoft ALM best practices dictate that development should always occur outside of production in
dedicated environments. Giving teams or features their own isolated development environment prevents
concurrent changes from overwriting each other. Deploying these feature-specific components as managed
solutions into downstream environments ensures controlled, predictable deployment footprints without risk
of accidental source manipulation.
Why the other options are incorrect
A. Create and maintain separate solutions in a single development environment ... Sharing a single
development environment leads to a "last writer wins" conflict. Because Dataverse components are shared
globally across the environment, one team's changes can instantly overwrite or break another team's
configuration before deployment.
B. Make changes in a single solution. Deploy updates directly to production. Developing out of a single
solution lacks segregation of duties, risking unintended overwrites. Furthermore, deploying updates directly
to production circumvents testing phases (such as QA or UAT), creating high risk.
D. Create unmanaged solutions in production ... Modifying or deploying unmanaged solutions directly in
production creates severe configuration drift. It removes the ability to properly track, roll back, or control
code, defying standard ALM guidelines
A company is designing a Power Platform solution that includes a model-driven app used by customer service
representatives to manage support cases.
The company is evaluating which solution component to include in the app. The solution must meet the following
requirements:
Users must interact with system-generated responses while working within forms and views.
Responses must reflect the current data and context in the app.
Users must remain within the app while interacting with the solution.
You need to recommend solution components for the app.
Which two components should you recommend? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
A
Business rules
B
Copilot Studio agent
C
Smart assist
D
App assistant agent
Correct Answer:
B. Copilot Studio agent
Explanation:
B. Copilot Studio agent
D. App assistant agent.
B. Copilot Studio agent: Copilot Studio agents let you build customizable, intelligent assistants that natively
anchor to data inside your business applications. They dynamically generate responses using real-time data
context while keeping the user embedded entirely within the user interface.
D. App assistant agent: Previously known as the interactive agent, the app assistant agent is designed
explicitly to add tailored topics, knowledge sources, and natural language logic right within the side pane of a
model-driven app. This allows service representatives to view and interact with system responses without
navigating away from active forms and views.
Why the other options are incorrect:
A. Business rules: Business rules are primarily used to automate form behavior, such as hiding/showing
columns, enforcing validation logic, or setting field values. They do not generate conversational or dynamic
system responses that a user "interacts" with. [1, 2, 3]
C. Smart assist: Smart assist is a feature confined primarily to pre-built Dynamics 365 Customer Service
workloads (like suggesting similar knowledge base articles or historical cases on the productivity pane). It is
not a broad, custom solution component configured to provide interactive, contextual conversations in a
general model-driven app. [1]
Questions: 1-10 out of 69
Continue Full Practice..
GET ALL 69 QUESTIONS