Microsoft Building Intelligent Applications AB-410 Dumps in PDF

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.
Hide Case Study

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.
Hide Case Study

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.
Hide Case Study

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.
Hide Case Study

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.
Hide Case Study

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
Fabrikam Inc. is an energy provider that operates wind and solar farms across multiple countries and regions. The company uses Microsoft Power Platform to manage asset maintenance, technician workflows, and predictive analytics.
Field technicians use canvas apps on mobile devices to capture inspection and repair data. Operations managers use model-driven apps to monitor asset performance and maintenance history.
The company plans to enhance its platform by introducing AI-driven insights, improving reuse across applications, and establishing a formal application lifecycle management (ALM) strategy.
Current environment
Applications
-Field technicians use an outdated mobile app to log maintenance activities and capture asset readings in SharePoint Online.
-Operations managers use a model-driven app to review maintenance records and asset performance trends.
Development practices
-Developers build and modify applications directly in the production environment.
-There is NO structured ALM process.
-Solutions are NOT consistently used to package or deploy application components.
-Reusable components are inconsistently implemented across apps, leading to duplication.
AI integration
-Fabrikam Inc. plans to actively explore generative AI usage as part of the next phase of work.
Business requirement
Application development
-The outdated mobile app must be replaced with a new app that supports responsive design principles, provides full control over the UI, and allows technicians to take and upload photos directly from their mobile devices.
-The new app for the field technicians requires the name of the technician to be persisted on the home screen only. In addition, work orders must be displayed within a gallery.
-All new apps must connect to a scalable, cloud-based relational data store.
-Apps must support efficient data entry for technicians in the field.
-Reusable UI elements must be implemented to reduce duplication.
AI capabilities
-The company requires a generative AI solution to manage customer complaint responses and create custom inspection reports that align to an existing template.
-Customer complaint responses must be generated in applications and based on emails being sent to a mailbox.
-Custom AI development must be minimized.
Generative AI reusability
-Generative AI solutions must accept dynamic inputs to adapt to different scenarios.
-Generative AI solutions must be reusable across different Power Platform services.
Extensibility
-Custom UI form components must be reusable across applications.
-Use of server-side custom code must be minimized where possible.
Technical requirements
Application lifecycle management (ALM)
-Separate environments must be used for development, testing, and production.
-Solutions must be used to package application components, segmented based on functional areas.
-Managed solutions must be deployed to the production environment.
-Validation must occur before deployment to production.
Data processing
-Aggregated values across related rows must be displayed for reporting.
-Calculations must update automatically as new data is entered. Calculation data must be limited to a maximum length of 10.
Issues
-Duplicate logic exists across multiple canvas apps.
-Developers frequently overwrite changes in production.
-Generative AI solutions produce inconsistent outputs due to missing or inconsistent inputs.
-Maintenance metrics are not consistently calculated across related rows.
-
Hide Case Study

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
Fabrikam Inc. is an energy provider that operates wind and solar farms across multiple countries and regions. The company uses Microsoft Power Platform to manage asset maintenance, technician workflows, and predictive analytics.
Field technicians use canvas apps on mobile devices to capture inspection and repair data. Operations managers use model-driven apps to monitor asset performance and maintenance history.
The company plans to enhance its platform by introducing AI-driven insights, improving reuse across applications, and establishing a formal application lifecycle management (ALM) strategy.
Current environment
Applications
-Field technicians use an outdated mobile app to log maintenance activities and capture asset readings in SharePoint Online.
-Operations managers use a model-driven app to review maintenance records and asset performance trends.
Development practices
-Developers build and modify applications directly in the production environment.
-There is NO structured ALM process.
-Solutions are NOT consistently used to package or deploy application components.
-Reusable components are inconsistently implemented across apps, leading to duplication.
AI integration
-Fabrikam Inc. plans to actively explore generative AI usage as part of the next phase of work.
Business requirement
Application development
-The outdated mobile app must be replaced with a new app that supports responsive design principles, provides full control over the UI, and allows technicians to take and upload photos directly from their mobile devices.
-The new app for the field technicians requires the name of the technician to be persisted on the home screen only. In addition, work orders must be displayed within a gallery.
-All new apps must connect to a scalable, cloud-based relational data store.
-Apps must support efficient data entry for technicians in the field.
-Reusable UI elements must be implemented to reduce duplication.
AI capabilities
-The company requires a generative AI solution to manage customer complaint responses and create custom inspection reports that align to an existing template.
-Customer complaint responses must be generated in applications and based on emails being sent to a mailbox.
-Custom AI development must be minimized.
Generative AI reusability
-Generative AI solutions must accept dynamic inputs to adapt to different scenarios.
-Generative AI solutions must be reusable across different Power Platform services.
Extensibility
-Custom UI form components must be reusable across applications.
-Use of server-side custom code must be minimized where possible.
Technical requirements
Application lifecycle management (ALM)
-Separate environments must be used for development, testing, and production.
-Solutions must be used to package application components, segmented based on functional areas.
-Managed solutions must be deployed to the production environment.
-Validation must occur before deployment to production.
Data processing
-Aggregated values across related rows must be displayed for reporting.
-Calculations must update automatically as new data is entered. Calculation data must be limited to a maximum length of 10.
Issues
-Duplicate logic exists across multiple canvas apps.
-Developers frequently overwrite changes in production.
-Generative AI solutions produce inconsistent outputs due to missing or inconsistent inputs.
-Maintenance metrics are not consistently calculated across related rows.
-
Hide Case Study

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
ADatum Corporation provides verification and investigation services that are used by insurance companies, law firms, and other organizations in the public sector. Services include verifying an individual’s background, qualifications, and specific scenarios that require onsite visits.
The thorough work ADatum Corporation performs results in highly accurate cases with minimal critical information missing. Because of these high-quality results, ADatum Corporation is quickly proving itself as one of the best in the industry. In recent months, business has significantly increased, with most new business coming from high-profile companies and individuals.
Management has decided to create a new qualification verification (QV) role to help ensure that clients get the most accurate results. This role examines completed work to ensure that nothing is missed.
Current environment
Data storage and retention
-All information sent by clients for services is stored in Microsoft Dataverse with a model-driven app as the interface.
-Clients enter their data in a website, which then uses a service account to create the records in the Dataverse database.
-Team members currently have full access to all Service Request records.
Service requests
-The Service Request table includes header information about the individual or organization that is the subject of verification.
-New Service Request records are assigned to a queue. All potential users who will be performing the verifications have access to these records.
-A service request is assigned to a single user who will ensure that all qualifications are verified. This single user is the only one able to process Qualification records related to their own service requests.
-Many required tasks when performing verification services are currently done by using manual processes.
-To keep up with demand, ADatum Corporation identifies several processes that can be replaced by using Power flows to hire fewer new staff and keep costs down.
Qualification verification
-The qualification table contains details about an individual school degree, professional qualifications, and other qualifications that must be verified.
-A service request can have one or more Qualification records associated with it.
-Record status is pending verification until the initial team member finishes, at which point the member changes the status to Complete.
-When all qualification records related to a service request are verified either by manual or automated processes, the results are made available to ADatum Corporation’s client.
-In the rare event that results are questioned, a new service request is created and verified independently of the previous work that took place.
-To complete a service request, users perform the following actions:
- Send a templated email by using Microsoft Outlook to the client after all qualifications for a service request are checked.
- Change the service request status to Completed. Currently, service requests do not indicate when all Qualification records are addressed.
Microsoft Power Platform environment
-The following environments exist: development, testing, user acceptance testing (UAT), and production.
-Managed solutions are used to move customizations from the development environment to other higher-level environments. These solutions are created and maintained by the power users and provided to internal IT for deployment when they are ready.
-Two managed solutions, Verification Process Automation and Onsite Visit, share several components.
-All customizations to Power Platform components are performed by several power users who have received training and are certified as subject matter experts.
-Power users have been granted the System Administrator security role in the development environment.
-Corporate policy prohibits power users from writing code due to lack of a formal code review process.
-Internal IT will not be able to supply any development resources for this project due to a lack of staff. This means that any customizations and automation created for this project must be low-code/no-code for the power users to implement them.
-Customizations created by power users are deployed by internal IT.
Requirements
Process automation
ADatum Corporation plans to establish a new QV department to verify completed work so that the quality of work is maintained. The new process for verifying professional qualifications must automate the following:
-Enter data and navigate the authority’s website. The authority website UI changes frequently because the company constantly improves the user experience.
-Search page contents for a specified value to determine validity.
-Update the corresponding Qualification record in Dataverse.
The new process for completing a service request must automate the following:
-Set the Service Request record status to Complete when work on all Qualification records is finished.
-Send an email to the client with the results when the service request is completed. The email must list each qualification as either Valid or Not Valid, depending on the verification.
Qualification verification
-Service request results will not be released to clients until all related Qualification records are set to a Complete status.
-To check work done by a wide array of users, 10 percent of Qualification records must be double checked.
-Qualification records must be automatically assigned to a queue.
-Qualification records must be flagged with a new status field named Assigned to ensure that records are rechecked.
-Ensure that only QV team members can change the status from Assigned to In Progress to Complete.
-Record the name of the QV team member who performed the work and the date completed.
Governance and security
-All components required for the verification process must be included in a new solution.
-Corporate security requires that deployments to non-development environments must be automated using service accounts.
-User security and data access must also be consistent across environments, except for the elevated access of the power users in the development environment.
-The Onsite Visit managed solution has a table that is not in the Verification Process Automation managed solution. This table must be upgraded prior to the go-live date without the other shared components.
-A VP of sales requires a test environment to demonstrate to potential clients the security policies that are included in their initial offering.
Issues
-More employees than are required can access individual client information and continue to have access after a service request is completed.
-When users go on vacation, all their outstanding Service Request records are assigned to a substitute employee. The substitute employees are unable to see all the qualifications related to their service requests.
-Currently, testing the new QV functionality outside the development environment is not possible due to corporate security policies requiring the same security role across all environments.
-Internal IT reports that the solution import to the test environment failed because of missing dependencies related to the flow for completing service requests.
-
Hide Case Study