Microsoft Building Intelligent Applications AB-410 Dumps in PDF

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

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

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 Suites is an animal shelter that specializes in finding homes for dogs that have been given up by their owners. The shelter can house up to 20 dogs.
The shelter is implementing one model-driven Power Apps app to track the dogs and schedule meetings with potential adopters. No other apps will be created.
The model-driven app uses Dataverse with out-of-the-box functionality when possible. Dataverse is set up with the following configuration:
-The solution prefix “cs” is used for all new components.
-Only the root business unit is used.
-All tables are stored in Dataverse and do not require rapid scaling.
-Exchange server-side sync is not configured.
Adopters
-Adopter information is stored in a Contact table.
-Contacts are considered to be duplicates if they have the same email address and last name.
-Adopters are often late to meetings, so a reminder email is sent to them two hours before their meeting.
-The email reminders must not be tracked in the system.
Dogs
-Dog information is stored in a Dog table, which is organization owned.
-Breed, size, and weight are fields in the table.
Dog residency
-A Resident table tracks the stay of each dog.
-Each resident record has a lookup for the dog and its food.
-The food type and amount are logged on each resident record. Auto-posting is not configured for changes to food type and amount.
-A fee of $120 is in a currency column named Adoption Fee. This fee can be changed depending on the adoption circumstances.
-A formula column named Deposit is automatically populated with 20% of the adoption fee.
-A resident record is generated automatically when a dog record is created. This is the only way a resident record can be created.
Exercise and feedings
-Exercise for the dogs is tracked in an Exercise table.
-Feedings are tracked in a Feeding table.
-Exercise and feeding records appear in a resident record timeline.
Care staff
-The care staff must be able to view who changed the food type and the amount that was given, for up to three months ago.
-The staff must be able to update the weight of a dog on the resident record.
-The staff report that the buttons are too small on the touch screen they use to log exercise and feeding.
-The staff must be able to view who the adopters are for upcoming meetings. The staff must not be able to update adopter information.
Administrative staff
-Administrative staff must receive a weekly list of duplicate contacts. Duplicate alerts must not appear when a staff member saves a new contact.
-When an adopter wants to adopt a dog, the staff must perform a series of adoption duties in order. The following duty list must be displayed on the screen:
- Commitment:
o Obtain adopter signature in a commitment document.
o Collect deposit.
- Pre-pickup:
o Document spay or neutering date.
o Perform spay or neutering.
o Document pickup date.
- Pickup:
o Collect full payment.
o Verify dog is picked up.
- A dog must be picked up no sooner than two days after spaying or neutering.
- A pop-up window must appear with an error message if the Pickup date is too soon.
- Only administrative staff must be able to add new adopters and dogs.
Hide Case Study

This is a case study. Case studies are not timed separately from other exam sections. You can use as much exam time as you would like to complete each case study. However, there might be additional case studies or other exam sections. Manage your time to ensure that you can complete all the exam sections in the time provided. Pay attention to the Exam Progress at the top of the screen so you have sufficient time to complete any exam sections that follow this case study.
To answer the case study questions, you will need to reference information that is provided in the case. Case studies and associated questions might contain exhibits or other resources that provide more information about the scenario described in the case. Information provided in an individual question does not apply to the other questions in the case study.
A Review Screen will appear at the end of this case study. From the Review Screen, you can review and change your answers before you move to the next exam section. After you leave this case study, you will NOT be able to return to it.
To start the case study
To display the first question in this case study, select the “Next” button. To the left of the question, a menu provides links to information such as business requirements, the existing environment, and problem statements. Please read through all this information before answering any questions.
When you are ready to answer a question, select the “Question” button to return to the question.
Background
Contoso Suites is an animal shelter that specializes in finding homes for dogs that have been given up by their owners. The shelter can house up to 20 dogs.
The shelter is implementing one model-driven Power Apps app to track the dogs and schedule meetings with potential adopters. No other apps will be created.
The model-driven app uses Dataverse with out-of-the-box functionality when possible. Dataverse is set up with the following configuration:
-The solution prefix “cs” is used for all new components.
-Only the root business unit is used.
-All tables are stored in Dataverse and do not require rapid scaling.
-Exchange server-side sync is not configured.
Adopters
-Adopter information is stored in a Contact table.
-Contacts are considered to be duplicates if they have the same email address and last name.
-Adopters are often late to meetings, so a reminder email is sent to them two hours before their meeting.
-The email reminders must not be tracked in the system.
Dogs
-Dog information is stored in a Dog table, which is organization owned.
-Breed, size, and weight are fields in the table.
Dog residency
-A Resident table tracks the stay of each dog.
-Each resident record has a lookup for the dog and its food.
-The food type and amount are logged on each resident record. Auto-posting is not configured for changes to food type and amount.
-A fee of $120 is in a currency column named Adoption Fee. This fee can be changed depending on the adoption circumstances.
-A formula column named Deposit is automatically populated with 20% of the adoption fee.
-A resident record is generated automatically when a dog record is created. This is the only way a resident record can be created.
Exercise and feedings
-Exercise for the dogs is tracked in an Exercise table.
-Feedings are tracked in a Feeding table.
-Exercise and feeding records appear in a resident record timeline.
Care staff
-The care staff must be able to view who changed the food type and the amount that was given, for up to three months ago.
-The staff must be able to update the weight of a dog on the resident record.
-The staff report that the buttons are too small on the touch screen they use to log exercise and feeding.
-The staff must be able to view who the adopters are for upcoming meetings. The staff must not be able to update adopter information.
Administrative staff
-Administrative staff must receive a weekly list of duplicate contacts. Duplicate alerts must not appear when a staff member saves a new contact.
-When an adopter wants to adopt a dog, the staff must perform a series of adoption duties in order. The following duty list must be displayed on the screen:
- Commitment:
o Obtain adopter signature in a commitment document.
o Collect deposit.
- Pre-pickup:
o Document spay or neutering date.
o Perform spay or neutering.
o Document pickup date.
- Pickup:
o Collect full payment.
o Verify dog is picked up.
- A dog must be picked up no sooner than two days after spaying or neutering.
- A pop-up window must appear with an error message if the Pickup date is too soon.
- Only administrative staff must be able to add new adopters and dogs.
Hide Case Study

This is a case study. Case studies are not timed separately from other exam sections. You can use as much exam time as you would like to complete each case study. However, there might be additional case studies or other exam sections. Manage your time to ensure that you can complete all the exam sections in the time provided. Pay attention to the Exam Progress at the top of the screen so you have sufficient time to complete any exam sections that follow this case study.
To answer the case study questions, you will need to reference information that is provided in the case. Case studies and associated questions might contain exhibits or other resources that provide more information about the scenario described in the case. Information provided in an individual question does not apply to the other questions in the case study.
A Review Screen will appear at the end of this case study. From the Review Screen, you can review and change your answers before you move to the next exam section. After you leave this case study, you will NOT be able to return to it.
To start the case study
To display the first question in this case study, select the “Next” button. To the left of the question, a menu provides links to information such as business requirements, the existing environment, and problem statements. Please read through all this information before answering any questions.
When you are ready to answer a question, select the “Question” button to return to the question.
Background
Contoso Suites is an animal shelter that specializes in finding homes for dogs that have been given up by their owners. The shelter can house up to 20 dogs.
The shelter is implementing one model-driven Power Apps app to track the dogs and schedule meetings with potential adopters. No other apps will be created.
The model-driven app uses Dataverse with out-of-the-box functionality when possible. Dataverse is set up with the following configuration:
-The solution prefix “cs” is used for all new components.
-Only the root business unit is used.
-All tables are stored in Dataverse and do not require rapid scaling.
-Exchange server-side sync is not configured.
Adopters
-Adopter information is stored in a Contact table.
-Contacts are considered to be duplicates if they have the same email address and last name.
-Adopters are often late to meetings, so a reminder email is sent to them two hours before their meeting.
-The email reminders must not be tracked in the system.
Dogs
-Dog information is stored in a Dog table, which is organization owned.
-Breed, size, and weight are fields in the table.
Dog residency
-A Resident table tracks the stay of each dog.
-Each resident record has a lookup for the dog and its food.
-The food type and amount are logged on each resident record. Auto-posting is not configured for changes to food type and amount.
-A fee of $120 is in a currency column named Adoption Fee. This fee can be changed depending on the adoption circumstances.
-A formula column named Deposit is automatically populated with 20% of the adoption fee.
-A resident record is generated automatically when a dog record is created. This is the only way a resident record can be created.
Exercise and feedings
-Exercise for the dogs is tracked in an Exercise table.
-Feedings are tracked in a Feeding table.
-Exercise and feeding records appear in a resident record timeline.
Care staff
-The care staff must be able to view who changed the food type and the amount that was given, for up to three months ago.
-The staff must be able to update the weight of a dog on the resident record.
-The staff report that the buttons are too small on the touch screen they use to log exercise and feeding.
-The staff must be able to view who the adopters are for upcoming meetings. The staff must not be able to update adopter information.
Administrative staff
-Administrative staff must receive a weekly list of duplicate contacts. Duplicate alerts must not appear when a staff member saves a new contact.
-When an adopter wants to adopt a dog, the staff must perform a series of adoption duties in order. The following duty list must be displayed on the screen:
- Commitment:
o Obtain adopter signature in a commitment document.
o Collect deposit.
- Pre-pickup:
o Document spay or neutering date.
o Perform spay or neutering.
o Document pickup date.
- Pickup:
o Collect full payment.
o Verify dog is picked up.
- A dog must be picked up no sooner than two days after spaying or neutering.
- A pop-up window must appear with an error message if the Pickup date is too soon.
- Only administrative staff must be able to add new adopters and dogs.
Hide Case Study

This is a case study. Case studies are not timed separately from other exam sections. You can use as much exam time as you would like to complete each case study. However, there might be additional case studies or other exam sections. Manage your time to ensure that you can complete all the exam sections in the time provided. Pay attention to the Exam Progress at the top of the screen so you have sufficient time to complete any exam sections that follow this case study.
To answer the case study questions, you will need to reference information that is provided in the case. Case studies and associated questions might contain exhibits or other resources that provide more information about the scenario described in the case. Information provided in an individual question does not apply to the other questions in the case study.
A Review Screen will appear at the end of this case study. From the Review Screen, you can review and change your answers before you move to the next exam section. After you leave this case study, you will NOT be able to return to it.
To start the case study
To display the first question in this case study, select the “Next” button. To the left of the question, a menu provides links to information such as business requirements, the existing environment, and problem statements. Please read through all this information before answering any questions.
When you are ready to answer a question, select the “Question” button to return to the question.
Background
Contoso Suites is an animal shelter that specializes in finding homes for dogs that have been given up by their owners. The shelter can house up to 20 dogs.
The shelter is implementing one model-driven Power Apps app to track the dogs and schedule meetings with potential adopters. No other apps will be created.
The model-driven app uses Dataverse with out-of-the-box functionality when possible. Dataverse is set up with the following configuration:
-The solution prefix “cs” is used for all new components.
-Only the root business unit is used.
-All tables are stored in Dataverse and do not require rapid scaling.
-Exchange server-side sync is not configured.
Adopters
-Adopter information is stored in a Contact table.
-Contacts are considered to be duplicates if they have the same email address and last name.
-Adopters are often late to meetings, so a reminder email is sent to them two hours before their meeting.
-The email reminders must not be tracked in the system.
Dogs
-Dog information is stored in a Dog table, which is organization owned.
-Breed, size, and weight are fields in the table.
Dog residency
-A Resident table tracks the stay of each dog.
-Each resident record has a lookup for the dog and its food.
-The food type and amount are logged on each resident record. Auto-posting is not configured for changes to food type and amount.
-A fee of $120 is in a currency column named Adoption Fee. This fee can be changed depending on the adoption circumstances.
-A formula column named Deposit is automatically populated with 20% of the adoption fee.
-A resident record is generated automatically when a dog record is created. This is the only way a resident record can be created.
Exercise and feedings
-Exercise for the dogs is tracked in an Exercise table.
-Feedings are tracked in a Feeding table.
-Exercise and feeding records appear in a resident record timeline.
Care staff
-The care staff must be able to view who changed the food type and the amount that was given, for up to three months ago.
-The staff must be able to update the weight of a dog on the resident record.
-The staff report that the buttons are too small on the touch screen they use to log exercise and feeding.
-The staff must be able to view who the adopters are for upcoming meetings. The staff must not be able to update adopter information.
Administrative staff
-Administrative staff must receive a weekly list of duplicate contacts. Duplicate alerts must not appear when a staff member saves a new contact.
-When an adopter wants to adopt a dog, the staff must perform a series of adoption duties in order. The following duty list must be displayed on the screen:
- Commitment:
o Obtain adopter signature in a commitment document.
o Collect deposit.
- Pre-pickup:
o Document spay or neutering date.
o Perform spay or neutering.
o Document pickup date.
- Pickup:
o Collect full payment.
o Verify dog is picked up.
- A dog must be picked up no sooner than two days after spaying or neutering.
- A pop-up window must appear with an error message if the Pickup date is too soon.
- Only administrative staff must be able to add new adopters and dogs.
Hide Case Study

This is a case study. Case studies are not timed separately from other exam sections. You can use as much exam time as you would like to complete each case study. However, there might be additional case studies or other exam sections. Manage your time to ensure that you can complete all the exam sections in the time provided. Pay attention to the Exam Progress at the top of the screen so you have sufficient time to complete any exam sections that follow this case study.
To answer the case study questions, you will need to reference information that is provided in the case. Case studies and associated questions might contain exhibits or other resources that provide more information about the scenario described in the case. Information provided in an individual question does not apply to the other questions in the case study.
A Review Screen will appear at the end of this case study. From the Review Screen, you can review and change your answers before you move to the next exam section. After you leave this case study, you will NOT be able to return to it.
To start the case study
To display the first question in this case study, select the “Next” button. To the left of the question, a menu provides links to information such as business requirements, the existing environment, and problem statements. Please read through all this information before answering any questions.
When you are ready to answer a question, select the “Question” button to return to the question.
Background
Contoso Suites is an animal shelter that specializes in finding homes for dogs that have been given up by their owners. The shelter can house up to 20 dogs.
The shelter is implementing one model-driven Power Apps app to track the dogs and schedule meetings with potential adopters. No other apps will be created.
The model-driven app uses Dataverse with out-of-the-box functionality when possible. Dataverse is set up with the following configuration:
-The solution prefix “cs” is used for all new components.
-Only the root business unit is used.
-All tables are stored in Dataverse and do not require rapid scaling.
-Exchange server-side sync is not configured.
Adopters
-Adopter information is stored in a Contact table.
-Contacts are considered to be duplicates if they have the same email address and last name.
-Adopters are often late to meetings, so a reminder email is sent to them two hours before their meeting.
-The email reminders must not be tracked in the system.
Dogs
-Dog information is stored in a Dog table, which is organization owned.
-Breed, size, and weight are fields in the table.
Dog residency
-A Resident table tracks the stay of each dog.
-Each resident record has a lookup for the dog and its food.
-The food type and amount are logged on each resident record. Auto-posting is not configured for changes to food type and amount.
-A fee of $120 is in a currency column named Adoption Fee. This fee can be changed depending on the adoption circumstances.
-A formula column named Deposit is automatically populated with 20% of the adoption fee.
-A resident record is generated automatically when a dog record is created. This is the only way a resident record can be created.
Exercise and feedings
-Exercise for the dogs is tracked in an Exercise table.
-Feedings are tracked in a Feeding table.
-Exercise and feeding records appear in a resident record timeline.
Care staff
-The care staff must be able to view who changed the food type and the amount that was given, for up to three months ago.
-The staff must be able to update the weight of a dog on the resident record.
-The staff report that the buttons are too small on the touch screen they use to log exercise and feeding.
-The staff must be able to view who the adopters are for upcoming meetings. The staff must not be able to update adopter information.
Administrative staff
-Administrative staff must receive a weekly list of duplicate contacts. Duplicate alerts must not appear when a staff member saves a new contact.
-When an adopter wants to adopt a dog, the staff must perform a series of adoption duties in order. The following duty list must be displayed on the screen:
- Commitment:
o Obtain adopter signature in a commitment document.
o Collect deposit.
- Pre-pickup:
o Document spay or neutering date.
o Perform spay or neutering.
o Document pickup date.
- Pickup:
o Collect full payment.
o Verify dog is picked up.
- A dog must be picked up no sooner than two days after spaying or neutering.
- A pop-up window must appear with an error message if the Pickup date is too soon.
- Only administrative staff must be able to add new adopters and dogs.
Hide Case Study

This is a case study. Case studies are not timed separately from other exam sections. You can use as much exam time as you would like to complete each case study. However, there might be additional case studies or other exam sections. Manage your time to ensure that you can complete all the exam sections in the time provided. Pay attention to the Exam Progress at the top of the screen so you have sufficient time to complete any exam sections that follow this case study.
To answer the case study questions, you will need to reference information that is provided in the case. Case studies and associated questions might contain exhibits or other resources that provide more information about the scenario described in the case. Information provided in an individual question does not apply to the other questions in the case study.
A Review Screen will appear at the end of this case study. From the Review Screen, you can review and change your answers before you move to the next exam section. After you leave this case study, you will NOT be able to return to it.
To start the case study
To display the first question in this case study, select the “Next” button. To the left of the question, a menu provides links to information such as business requirements, the existing environment, and problem statements. Please read through all this information before answering any questions.
When you are ready to answer a question, select the “Question” button to return to the question.
Background
Contoso Suites is an animal shelter that specializes in finding homes for dogs that have been given up by their owners. The shelter can house up to 20 dogs.
The shelter is implementing one model-driven Power Apps app to track the dogs and schedule meetings with potential adopters. No other apps will be created.
The model-driven app uses Dataverse with out-of-the-box functionality when possible. Dataverse is set up with the following configuration:
-The solution prefix “cs” is used for all new components.
-Only the root business unit is used.
-All tables are stored in Dataverse and do not require rapid scaling.
-Exchange server-side sync is not configured.
Adopters
-Adopter information is stored in a Contact table.
-Contacts are considered to be duplicates if they have the same email address and last name.
-Adopters are often late to meetings, so a reminder email is sent to them two hours before their meeting.
-The email reminders must not be tracked in the system.
Dogs
-Dog information is stored in a Dog table, which is organization owned.
-Breed, size, and weight are fields in the table.
Dog residency
-A Resident table tracks the stay of each dog.
-Each resident record has a lookup for the dog and its food.
-The food type and amount are logged on each resident record. Auto-posting is not configured for changes to food type and amount.
-A fee of $120 is in a currency column named Adoption Fee. This fee can be changed depending on the adoption circumstances.
-A formula column named Deposit is automatically populated with 20% of the adoption fee.
-A resident record is generated automatically when a dog record is created. This is the only way a resident record can be created.
Exercise and feedings
-Exercise for the dogs is tracked in an Exercise table.
-Feedings are tracked in a Feeding table.
-Exercise and feeding records appear in a resident record timeline.
Care staff
-The care staff must be able to view who changed the food type and the amount that was given, for up to three months ago.
-The staff must be able to update the weight of a dog on the resident record.
-The staff report that the buttons are too small on the touch screen they use to log exercise and feeding.
-The staff must be able to view who the adopters are for upcoming meetings. The staff must not be able to update adopter information.
Administrative staff
-Administrative staff must receive a weekly list of duplicate contacts. Duplicate alerts must not appear when a staff member saves a new contact.
-When an adopter wants to adopt a dog, the staff must perform a series of adoption duties in order. The following duty list must be displayed on the screen:
- Commitment:
o Obtain adopter signature in a commitment document.
o Collect deposit.
- Pre-pickup:
o Document spay or neutering date.
o Perform spay or neutering.
o Document pickup date.
- Pickup:
o Collect full payment.
o Verify dog is picked up.
- A dog must be picked up no sooner than two days after spaying or neutering.
- A pop-up window must appear with an error message if the Pickup date is too soon.
- Only administrative staff must be able to add new adopters and dogs.
Hide Case Study