최신 AB-410 무료덤프 - Microsoft Building Intelligent Applications
Case Study 1 - Contoso, Ltd
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?
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?
정답: C
설명: (DumpTOP 회원만 볼 수 있음)
Case Study 1 - Contoso, Ltd
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 and Drop Question
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.
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 and Drop Question
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.
정답:
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
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?
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?
정답: B
설명: (DumpTOP 회원만 볼 수 있음)
Case Study 2 - Fabrikam Inc
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.
Drag and Drop Question
You need to create the new app based on the requirements.
Which configurations should you use? To answer, move the appropriate configurations to the correct requirements. 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.
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.
Drag and Drop Question
You need to create the new app based on the requirements.
Which configurations should you use? To answer, move the appropriate configurations to the correct requirements. 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.
정답:
Explanation:
Box 1: Context variable
The new app for the field technicians requires the name of the technician to be persisted on the home screen only.
The correct feature for this requirement is a Context variable.
Screen-Level Scope: Context variables in Power Apps are explicitly designed to hold a temporary state or value that only matters on the current screen.
Isolated Data: Because the requirement explicitly states that the technician's name only needs to be persisted on the home screen only, using a local/context variable ensures the data is isolated and does not occupy unnecessary memory across other pages or screens.
Box 2: Collection
Work orders must be displayed within a gallery.
The correct feature useful for this requirement is a Collection.
Tabular Data Storage: A collection is a specialized local variable in Power Apps explicitly designed to store multi-column data tables, arrays, or groups of records locally.
Gallery Integration: The primary purpose of a Gallery control is to display a list or table of multiple records. Setting the Items property of a gallery directly to a Collection (e.g., ClearCollect(colWorkOrders, WorkOrdersDataSource)) allows you to loop through, manipulate, and cleanly render each work order record.
Box 3: Named formula
Define logic statements.
When writing Power Fx logic inside a model-driven app (such as for Dataverse formula columns or modern commanding), the platform heavily relies on declarative, excel-like calculations.
Named formulas allow developers to define logic statements that automatically recalculate based on their dependencies, without needing manual variable management. They improve app efficiency by calculating values only when they are needed.
Scenario:
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.
Reference:
https://chrisworth.dev/posts/power-apps-variables-mastery-guide/
Hotspot Question
A company processes customer orders by using a cloud flow.
The flow must evaluate the following conditions:
- Route orders for approval when the OrderTotal exceeds 1,000.
- Flag orders when the CustomerName identifies the string "VIP".
You need to configure flow conditions.
Which expressions should you use? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
A company processes customer orders by using a cloud flow.
The flow must evaluate the following conditions:
- Route orders for approval when the OrderTotal exceeds 1,000.
- Flag orders when the CustomerName identifies the string "VIP".
You need to configure flow conditions.
Which expressions should you use? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
정답:
Explanation:
Box 1: greater..
To configure the flow condition in Power Automate, you should use the expression greater(outputs('Get_order_details')?['body/OrderTotal'], 1000) (assuming your action is named Get_order_details).
If you are using the standard visual condition builder, select the OrderTotal dynamic content on the left, choose the operator is greater than, and enter 1000 on the right Box 2: contains..
To configure the flow condition to flag orders where the CustomerName contains or equals "VIP", you should use the contains expression or the equals expression depending on the exact matching requirement.
*-> Partial Match: If you want to flag any customer name that includes the letters "VIP" anywhere in the string (e.g., "VIP Logistics", "John VIP Doe"), use the contains operator.
Exact Match: If you only want to flag when the name is exactly "VIP" and nothing else, use the equals operator.
In the Power Automate condition builder, you can write these as advanced expressions or select them from the dynamic content dropdown:
For a Partial Match: contains(triggerBody()?['CustomerName'], 'VIP')
Reference:
https://go.collab365.com/how-to-use-the-condition-control-action-in-power-automate
https://www.reddit.com/r/MicrosoftFlow/comments/mzq0z2/how_to_use_contains_in_a_condition/
A company develops an AI chatbot using Azure OpenAI. Security administrators require that customer data must not be used to train public foundation models. Which statement correctly describes Azure OpenAI data handling?
정답: D
설명: (DumpTOP 회원만 볼 수 있음)
Case Study 2 - Fabrikam Inc
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.
You need to resolve the issues with the canvas apps.
Which two configurations should you use? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
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.
You need to resolve the issues with the canvas apps.
Which two configurations should you use? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
정답: C,D
설명: (DumpTOP 회원만 볼 수 있음)
Drag and Drop Question
An insurance company is implementing a customer service solution in Microsoft Dataverse to track interactions and manage issue resolution. The data model includes tables for customer information, support cases, and agents.
The data model includes the following requirements:
- Link each support case to a customer.
- Provide information on the children of customers.
- Record history of agents assigned to customers.
You need to configure table relationships.
Which relationships should you use? To answer, move the appropriate relationship to the correct requirement. You may use each relationship 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.
An insurance company is implementing a customer service solution in Microsoft Dataverse to track interactions and manage issue resolution. The data model includes tables for customer information, support cases, and agents.
The data model includes the following requirements:
- Link each support case to a customer.
- Provide information on the children of customers.
- Record history of agents assigned to customers.
You need to configure table relationships.
Which relationships should you use? To answer, move the appropriate relationship to the correct requirement. You may use each relationship 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.
정답:
Explanation:
Box 1: One-to-many
To link each support case to a specific customer in Microsoft Dataverse, you should use a One- to-many (1:N) relationship. This allows one customer (Account or Contact) to be associated with multiple support cases over time, while each individual case is linked to exactly one customer.
Box 2: One-to-many
You should use a One-to-many relationship.
Parent to Children: One customer (parent) can have multiple children.
Child to Parent: Each child belongs to only one customer (parent) in this specific structural context.
Note: Both the children parents could be customers, in which case a many-to-many relation could be considered.
Box 3: Connections
To record a history of multiple agents assigned to multiple customers over time, you should use Connections.
Tracks Historical Data: Standard Dataverse relationships (like One-to-Many) only show the current assignment. Connections let you keep a running log of past and present relationships.
Many-to-Many Behavior: An agent can be linked to many customers, and a customer can have many agents over time.
Adds Context: Connections allow you to assign "Connection Roles" (e.g., "Primary Agent,"
"Backup Agent," "Former Agent") and include start/end dates for when the agent was assigned.
Reference:
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-entity-relationships
https://learn.microsoft.com/en-us/power-apps/developer/data-platform/connection-entities
An accounting team is assigned to a model-driven app to manage financial data.
The app is currently visible in the app launcher but inaccessible to the accounting team.
Users must be able to:
- Open the app.
- Access and record financial data.
You need to resolve the access issues.
What should you do?
The app is currently visible in the app launcher but inaccessible to the accounting team.
Users must be able to:
- Open the app.
- Access and record financial data.
You need to resolve the access issues.
What should you do?
정답: D
Case Study 2 - Fabrikam Inc
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.
You need to implement the extensibility requirements.
Which two options should you use? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
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.
You need to implement the extensibility requirements.
Which two options should you use? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
정답: A,C
설명: (DumpTOP 회원만 볼 수 있음)