Microsoft Building Intelligent Applications AB-410 Dumps in PDF

Free Microsoft AB-410 Real Questions (page: 1)


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?

  1. local choice
  2. global choice
  3. status reason
  4. formula

Answer(s): B

Explanation:

The most appropriate column type for storing priorities with these specific values is a global choice (or a local choice if the priority list is completely unique to this table). Between the two choice options, a global choice is generally preferred in Dataverse for standard attributes like priority so that the same definition can be reused consistently across multiple tables (e.g., Tasks, Cases, and Projects).
Scenario: 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.


Reference:

https://learn.microsoft.com/en-us/power-apps/maker/data-platform/formula-columns?tabs=type-or-paste




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.

DRAG DROP (Drag and Drop is not supported)
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.
Select and Place:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Box 1: Referential, Restrict Delete If forced to choose the closest standard behavior that ensures the primary safety rule (preventing deletion if a technician is assigned) is met before any deletion happens, Referential, Restrict Delete
Box 2: Referential, Restrict Delete The correct relationship type to use is Referential, Restrict Delete.'
One-to-Many Structure: A technician can have multiple requests, but each request only links to one technician. This requires a standard lookup field on the Maintenance Request table.
Data Integrity: Restrict Delete prevents a technician record from being deleted if they are still assigned to active maintenance requests. This stops your data from becoming orphaned or broken.
Independent Lifecycles: A maintenance request should not be deleted just because a technician leaves the company (which rules out Parental). Historical Tracking: You want to keep the maintenance history intact rather than clearing the technician link blank (which rules out Remove link).
Scenario: Relationship requirements 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.


Reference:

https://learn.microsoft.com/en-us/power-apps/maker/data-platform/data-platform-entity-lookup




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.

DRAG DROP (Drag and Drop is not supported)
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.
Select and Place:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Box 1: Security roles To restrict a public view to a specific set of users within the table list view selector, you should use Security roles.
Microsoft Dataverse includes a native feature called role-based system views. This capability allows system administrators and makers to manage public view access directly within the view settings.
Scenario: 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.
Box 2: Sharing Sharing is the correct view access configuration to use.
Personal Views: These belong to individual users and cannot be assigned to security roles or business units.
Direct Control: Sharing allows the owner to grant specific permissions to other users or teams without changing record ownership.
Scenario: 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.


Reference:

https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/manage-view-access




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 define the alternate key for the Technicians table by using the TechCheck ref column.
Which setting should you apply to the TechCheck ref column?

  1. Required
  2. Searchable
  3. Column security
  4. Auditing

Answer(s): A

Explanation:

This column is required.
Scenario: Contoso Ltd. requires the following table logic: 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.



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?

  1. Restrict the view by assigning it to the manager security role.
  2. Configure table-level permissions for managers only.
  3. Remove the view from the app navigation.
  4. Set up the quick find view.

Answer(s): A

Explanation:

To achieve this goal, you should restrict the view by assigning it to the manager security role.
Incorrect: [Not B] Table-level permissions (Security Roles) control access to the data rows themselves, not the user interface components like views.


Reference:

https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/manage-view-access



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?

  1. Referential, Restrict Delete
  2. Referential
  3. Restrict
  4. Parental

Answer(s): D

Explanation:

To automatically assign all child records to a new owner when the parent record's owner changes, you must use a Parental relationship behavior type, or a Configurable Cascading relationship behavior type with the Assign action set to Cascade All.


Reference:

https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/create-and-edit-1n-relationships



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.

  1. Formula
  2. Calculated
  3. BigInt
  4. Prompt

Answer(s): A,B

Explanation:

To meet the requirements, you should use Calculated columns or Formula columns.
Formula Columns: This is the modern, recommended approach in Microsoft Power Apps. They use Power Fx to calculate values in real-time when a record is retrieved. They do not store data in the database and work perfectly in both forms and views.
Calculated Columns: This is the legacy feature that performs real-time calculations. Like formula columns, they do not store values in the database for time-dependent calculations (like using NOW() or UTCNOW()) and are supported across views and forms.



DRAG DROP (Drag and Drop is not supported)
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.
Select and Place:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Box 1: Choice column You should use a Choice column (formerly known as an Option Set). This column type allows you to define a static list of predefined classification values (e.g., "Tier 1", "Tier 2", or "VIP") that users can select from a drop-down menu on the Account table/entity reference (Microsoft Dataverse).
Predefined List: A classification value implies choosing from a fixed, standard set of options (e.g., Gold/Silver/ Bronze or VIP/Standard).
Native Feature: Choice columns allow users to select one or more values from a dropdown menu.
Low Overhead: They do not require creating or maintaining separate tables.
Box 2: Customer column
Box 3: Alternate key You should use an Alternate key.
An alternate key in Microsoft Dataverse allows you to define a unique business key made of one or more columns.
When you create an alternate key, the platform automatically generates a database index to enforce uniqueness and significantly optimize lookup performance.


Reference:

https://learn.microsoft.com/en-us/power-apps/developer/data-platform/define-alternate-keys-entity



Share your comments for Microsoft AB-410 exam with other users:

T
test user
9/24/2023 3:15:00 AM

thanks for the questions

D
Draco
7/19/2023 5:34:00 AM

please reopen it now ..its really urgent

M
Megan
4/14/2023 5:08:00 PM

these practice exam questions were exactly what i needed. the variety of questions and the realistic exam-like environment they created helped me assess my strengths and weaknesses. i felt more confident and well-prepared on exam day, and i owe it to this exam dumps!

A
abdo casa
8/9/2023 6:10:00 PM

thank u it very instructuf

D
Danny
1/15/2024 9:10:00 AM

its helpful?

H
hanaa
10/3/2023 6:57:00 PM

is this dump still valid???

G
Georgio
1/19/2024 8:15:00 AM

question 205 answer is b

M
Matthew Dievendorf
5/30/2023 9:37:00 PM

question 39, should be answer b, directions stated is being sudneted from /21 to a /23. a /23 has 512 ips so 510 hosts. and can make 4 subnets out of the /21

A
Adhithya
8/11/2022 12:27:00 AM

beautiful test engine software and very helpful. questions are same as in the real exam. i passed my paper.

S
SuckerPumch88
4/25/2022 10:24:00 AM

the questions are exactly the same in real exam. just make sure not to answer all them correct or else they suspect you are cheating.

S
soheib
7/24/2023 7:05:00 PM

question: 78 the right answer i think is d not a

S
srija
8/14/2023 8:53:00 AM

very helpful

T
Thembelani
5/30/2023 2:17:00 AM

i am writing this exam tomorrow and have dumps

A
Anita
10/1/2023 4:11:00 PM

can i have the icdl excel exam

B
Ben
9/9/2023 7:35:00 AM

please upload it

A
anonymous
9/20/2023 11:27:00 PM

hye when will post again the past year question for this h13-311_v3 part since i have to for my test tommorow…thank you very much

R
Randall
9/28/2023 8:25:00 PM

on question 22, option b-once per session is also valid.

T
Tshegofatso
8/28/2023 11:51:00 AM

this website is very helpful

P
philly
9/18/2023 2:40:00 PM

its my first time exam

B
Beexam
9/4/2023 9:06:00 PM

correct answers are device configuration-enable the automatic installation of webview2 runtime. & policy management- prevent users from submitting feedback.

R
RAWI
7/9/2023 4:54:00 AM

is this dump still valid? today is 9-july-2023

A
Annie
6/7/2023 3:46:00 AM

i need this exam.. please upload these are really helpful

S
Shubhra Rathi
8/26/2023 1:08:00 PM

please upload the oracle 1z0-1059-22 dumps

S
Shiji
10/15/2023 1:34:00 PM

very good questions

R
Rita Rony
11/27/2023 1:36:00 PM

nice, first step to exams

A
Aloke Paul
9/11/2023 6:53:00 AM

is this valid for chfiv9 as well... as i am reker 3rd time...

C
Calbert Francis
1/15/2024 8:19:00 PM

great exam for people taking 220-1101

A
Ayushi Baria
11/7/2023 7:44:00 AM

this is very helpfull for me

A
alma
8/25/2023 1:20:00 PM

just started preparing for the exam

C
CW
7/10/2023 6:46:00 PM

these are the type of questions i need.

N
Nobody
8/30/2023 9:54:00 PM

does this actually work? are they the exam questions and answers word for word?

S
Salah
7/23/2023 9:46:00 AM

thanks for providing these questions

R
Ritu
9/15/2023 5:55:00 AM

interesting

R
Ron
5/30/2023 8:33:00 AM

these dumps are pretty good.

AI Tutor 👋 I’m here to help!