HOTSPOT -
You need to synchronize pharmacy names and ensure that Dynamics 365 Sales data propagates correctly to the Cerner system.
What should you do? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:
Show Answer
Correct Answer: Synchronize pharmacy names: Use a Data integration template in Power Apps.
Propagate data to the Cerner system: Create a custom connector in Power Apps.
Explanation: Data integration templates are the standard low-code approach for synchronizing Dynamics 365 data. Because Cerner uses a proprietary system, integration typically requires a custom connector to exchange data with it.
Question 122
DRAG DROP
-
Case study
-
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
-
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Background
-
Contoso Pharmaceuticals manufactures and sells drugs to retail and wholesale pharmacies, hospitals, and research facilities.
The company plans to implement Dynamics 365 Sales and Dynamics 365 Finance.
Current environment
-
• Contoso maintains a Microsoft Excel workbook that lists all drugs they supply.
• Pharmacies submit order requests through email.
• All information at customer locations is handwritten by customer representatives.
• Contoso uses Cerner, which is a medical industry application that uses a proprietary database.
• Some accounts are referrals from other pharmacies.
• Every pharmacy has its own Dynamics 365 Sales instance.
Requirements
-
General
-
You must create a model-driven app to meet Contoso’s needs. You must minimize the use of custom code and custom connectors.
Accounts
-
• Ensure that the names of the pharmacies are synced between the accounting and the customer management systems.
• Account numbers should be entered automatically into the pharmaceutical system that is in a Cerner database and kept in sync.
• When the account is entered into the system, extra fields must appear if the referral customer box is selected. If the box is not selected, the extra fields must not appear.
• A trigger must be created that changes the Priority field to 1 in the Account record 10 days after an Account record is created.
• A field named Priority_Trigger must be created to trigger the Priority field.
• A field named Facility type field must be added in order to select whether a customer is a retail pharmacy, wholesale pharmacy, research facility, or hospital.
Users
-
• UserA must be able to create and publish Power Apps apps.
• UserB must be the owner of all the systems and be able to provide permissions and create all new environments.
• UserC must be able to create apps connected to the systems and update the security roles and entities.
• Pharmacy representatives must only be able to run the apps and access their own records.
• Access to the accounting Power Apps app must be restricted to accounting team members.
• End users must have minimum access to the required systems.
• Only supervisors must be able to view phone numbers in the Accounts form.
• Developers must be able to create new apps for all users.
• Sales users must only have access to their own records.
Reporting
-
Pharmacy orders must be displayed in four graphs as follows:
• Annual revenue over $100,000
• Annual revenues under $100,000
• Research facilities
• Hospitals
The graphs must be interactive, and users must be able to drill down on any dimension.
Customizations
-
• Ensure that notifications are sent to the sales team when a lead is added by using Slack.
• Ensure that leads have a review stage added to the sales process.
• Doctors must be manually added to a custom entity named Doctor if the doctor is not listed.
• Refill dates for customer prescriptions should be automatically determined and a notification should be sent to the customer.
• Fields for the doctor’s name and phone number must be displayed in the customer record.
• The doctor entered on the customer’s record must be validated against doctors that exist in the system.
• The new solution will be sold to other pharmacies for use. The application must not allow changes to be made.
• The solution must be error free so that when it is installed in other environments it does not cause issues.
Mobile app
-
• A custom mobile app must be created to allow salespeople to add or search by pharmacy name.
• Pharmacy records must be uniquely identified by pharmacy name, address, contact name, and phone number.
• When a pharmacy is added by using the mobile app, the phone number must be validated to be all digits.
You need to assign the minimum environmental security role to the appropriate users.
Which security roles should you use? To answer, drag the appropriate security roles to the correct users. Each security role may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Show Answer
Correct Answer: UserA — Environment Maker
UserB — System Administrator
UserC — System Customizer
All employees — Basic User
Explanation: Environment Maker can create and publish apps. System Administrator has full administrative control over environments and permissions. System Customizer is the minimum role for customizing apps and Dataverse components. Basic User provides minimal end-user access.
Question 123
Case Study -
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study -
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. When you are ready to answer a question, click the Question button to return to the question.
Background -
Proseware, Inc. is an industry leading software company with several thousand employees. The company has had some trouble recruiting talented employees. Top-level candidates interview with the company but go on to work for competitors.
Feedback from candidates show that some offers were not accepted because the interview scheduling process was unpleasant. The company does not have a system to keep track of the candidates that were not selected.
Current Environment -
The recruiting process starts when an individual applies for a position on the company website. The individual may have found the position on their own, they may have been officially referred by an employee, or in some cases were contacted directly by a hiring manager and encouraged to apply.
Recruiters schedule an interview with a hiring manager and interviews with two senior team members. Each interview results in feedback about the candidate and a recommendation whether to hire or not.
The recruiting team manages all information by using a model-driven application.
The company has the following Microsoft Dataverse tables and columns:
• JobPosting
- Hiring Manager - lookup to SystemUser
- Recruiter Assigned - lookup to SystemUser
• Contact (Job Applicant)
- Contact identifier
- First name
- Last name
- Time-Zone Offset
- Person of Interest - Yes/No (default)
• Application proapplication
- Contact identifier, Contact - lookup to Contact
- Job Posting - lookup to JobPosting
- pro_recruiterassignedid
• Interview
- Application - lookup to Application
- Job Posting - lookup to JobPosting
- Recommend - Choice (Yes (0), No (1), and null (default) are the available values)
- Person of Interest - Yes/No, No is the default value
• Referral
- Contact - lookup to Contact
- Referrer - lookup to SystemUser
- Job Posting - lookup to JobPosting
• SystemUser
- Manager - lookup to SystemUser
- Time-Zone Offset
• Recruiter
- Recruiter identifier
- Recruiter name
Applications -
There may be multiple applications associated with each job posting. Applications are linked to an employee record if an employee referred the applicant for a position. The same individual can be an applicant for multiple job postings.
Interviews -
Each interview is performed by an employee and is related to a single application.
The interview scheduling process may force potential candidates to accept interviews at unusual times with the senior team members due to time-zone differences.
Requirements. Interview Scheduling
The system must provide recruiters with a list of team members and their time-zone information. You must create a Microsoft Power Apps Component Framework (PCF) control for the Job Application form to display a list of senior team members who report directly to a hiring manager.
• The control must display the current time in each team member's local time.
• The control must be bound so that it minimizes the amount of code that must be written.
• You must display the list of team members and sort the list to show team members who reside in time zones closest to the applicant's time zone first.
You must develop a second PCF control that displays the time-zone name and current time on the Job Application form. You must display the data in the candidate’s local time.
Requirements. Historical Information Tracking
You must create a process to identify individuals as a person of interest that the company should consider hiring. You must assign each individual a score based on their past interactions.
• You must be able to determine the following information about a candidate:
- The number of interviews in the past two years and whether team members provided recommendations
- The number of hiring manager referrals and employee referrals in the past two years
- Whether the individual has any of the 12 designations or certifications that the company considers significant
• Only a single referral can be made per job application. The system must be able to support multiple referrals for a candidate.
• The system must track referrals even if an application is not completed.
Requirements. Historical Information Scoring
The automated process must run weekly to assess all candidates. The process must also run automatically when historical information is updated. You must be able to perform scoring by selecting a command button on the contact form.
• This new command button must only be visible to employees who belong to a security role assigned named Recruiter. The command button must not be visible to anyone unless the contact form is in Update mode.
• A person of interest is defined as having a score of 15 or more based on the following historical information criteria:
- Each interview with a recommendation adds two to the score.
- Each interview without a recommendation subtracts two from the score.
- Each employee or manager referral adds one to the score.
- Each designation or certification adds one to the score.
• All scoring elements must be recalculated when changes occur. You must assign the score to the Person of interest field.
• Values representing totals or scores must be stored in their own numeric fields.
• Plug-ins must be used to keep the Person of Interest field on active interview records associated with the Contact.
• Plug-ins registered on the update of the Person of interest field must send an email notification when the candidate named in the email is a person of interest. Recruiters must receive the message when the field is updated on the Contact record.
• Interviewers must get an email notification when the Person of Interest field on the interview record is successfully updated.
Requirements. Design Guidelines -
The following design guidelines must be followed:
• Schema changes must be made using the method requiring the least amount of storage to meet the requirement.
• Out-of-the-box functionality must be used when possible.
• Any code required to calculate scores must be able to be run from a single point.
• Email notifications need to be kept to a minimum.
Issues -
• Recruiters report that the command button to score a candidate is not working. You debug the code and observe that the context input parameter is null.
• The system does not support associating designations and certifications with candidates.
• The value for the field used by the PCF control to display local time is saved to Microsoft Dataverse each time an active application record is opened.
• Interviewers report that they do not receive email notifications when interview records are created for an existing person of interest.
You need to prevent the field used by the PCF control from updating the record.
What are two possible ways to achieve the goal? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
A. Create a business rule to clear the field value.
B. Make the field read-only.
C. Call the setSubmitMode(‘never’) function on the field.
D. Disable existing event handlers on the field.
Show Answer
Correct Answer: B, C
Explanation: A bound PCF control can change the bound field value, causing Dataverse to persist it on save. Calling setSubmitMode('never') on the attribute prevents that field from being submitted during save, so the value is not written back. Making the field read-only is another valid approach to prevent user edits to the underlying field while still allowing it to be used for display. A business rule that clears the field does not prevent updates, and disabling event handlers does not stop the field value from being submitted.
Question 124
Case Study -
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study -
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. When you are ready to answer a question, click the Question button to return to the question.
Background -
Proseware, Inc. is an industry leading software company with several thousand employees. The company has had some trouble recruiting talented employees. Top-level candidates interview with the company but go on to work for competitors.
Feedback from candidates show that some offers were not accepted because the interview scheduling process was unpleasant. The company does not have a system to keep track of the candidates that were not selected.
Current Environment -
The recruiting process starts when an individual applies for a position on the company website. The individual may have found the position on their own, they may have been officially referred by an employee, or in some cases were contacted directly by a hiring manager and encouraged to apply.
Recruiters schedule an interview with a hiring manager and interviews with two senior team members. Each interview results in feedback about the candidate and a recommendation whether to hire or not.
The recruiting team manages all information by using a model-driven application.
The company has the following Microsoft Dataverse tables and columns:
• JobPosting
- Hiring Manager - lookup to SystemUser
- Recruiter Assigned - lookup to SystemUser
• Contact (Job Applicant)
- Contact identifier
- First name
- Last name
- Time-Zone Offset
- Person of Interest - Yes/No (default)
• Application proapplication
- Contact identifier, Contact - lookup to Contact
- Job Posting - lookup to JobPosting
- pro_recruiterassignedid
• Interview
- Application - lookup to Application
- Job Posting - lookup to JobPosting
- Recommend - Choice (Yes (0), No (1), and null (default) are the available values)
- Person of Interest - Yes/No, No is the default value
• Referral
- Contact - lookup to Contact
- Referrer - lookup to SystemUser
- Job Posting - lookup to JobPosting
• SystemUser
- Manager - lookup to SystemUser
- Time-Zone Offset
• Recruiter
- Recruiter identifier
- Recruiter name
Applications -
There may be multiple applications associated with each job posting. Applications are linked to an employee record if an employee referred the applicant for a position. The same individual can be an applicant for multiple job postings.
Interviews -
Each interview is performed by an employee and is related to a single application.
The interview scheduling process may force potential candidates to accept interviews at unusual times with the senior team members due to time-zone differences.
Requirements. Interview Scheduling
The system must provide recruiters with a list of team members and their time-zone information. You must create a Microsoft Power Apps Component Framework (PCF) control for the Job Application form to display a list of senior team members who report directly to a hiring manager.
• The control must display the current time in each team member's local time.
• The control must be bound so that it minimizes the amount of code that must be written.
• You must display the list of team members and sort the list to show team members who reside in time zones closest to the applicant's time zone first.
You must develop a second PCF control that displays the time-zone name and current time on the Job Application form. You must display the data in the candidate’s local time.
Requirements. Historical Information Tracking
You must create a process to identify individuals as a person of interest that the company should consider hiring. You must assign each individual a score based on their past interactions.
• You must be able to determine the following information about a candidate:
- The number of interviews in the past two years and whether team members provided recommendations
- The number of hiring manager referrals and employee referrals in the past two years
- Whether the individual has any of the 12 designations or certifications that the company considers significant
• Only a single referral can be made per job application. The system must be able to support multiple referrals for a candidate.
• The system must track referrals even if an application is not completed.
Requirements. Historical Information Scoring
The automated process must run weekly to assess all candidates. The process must also run automatically when historical information is updated. You must be able to perform scoring by selecting a command button on the contact form.
• This new command button must only be visible to employees who belong to a security role assigned named Recruiter. The command button must not be visible to anyone unless the contact form is in Update mode.
• A person of interest is defined as having a score of 15 or more based on the following historical information criteria:
- Each interview with a recommendation adds two to the score.
- Each interview without a recommendation subtracts two from the score.
- Each employee or manager referral adds one to the score.
- Each designation or certification adds one to the score.
• All scoring elements must be recalculated when changes occur. You must assign the score to the Person of interest field.
• Values representing totals or scores must be stored in their own numeric fields.
• Plug-ins must be used to keep the Person of Interest field on active interview records associated with the Contact.
• Plug-ins registered on the update of the Person of interest field must send an email notification when the candidate named in the email is a person of interest. Recruiters must receive the message when the field is updated on the Contact record.
• Interviewers must get an email notification when the Person of Interest field on the interview record is successfully updated.
Requirements. Design Guidelines -
The following design guidelines must be followed:
• Schema changes must be made using the method requiring the least amount of storage to meet the requirement.
• Out-of-the-box functionality must be used when possible.
• Any code required to calculate scores must be able to be run from a single point.
• Email notifications need to be kept to a minimum.
Issues -
• Recruiters report that the command button to score a candidate is not working. You debug the code and observe that the context input parameter is null.
• The system does not support associating designations and certifications with candidates.
• The value for the field used by the PCF control to display local time is saved to Microsoft Dataverse each time an active application record is opened.
• Interviewers report that they do not receive email notifications when interview records are created for an existing person of interest.
You need to store designations and certifications.
What should you do?
A. Create a new Lookup column on the Contact table.
B. Create a new table that has an N:N relationship with the Contact table.
C. Create a new table that has an N:1 relationship with the Contact table.
D. Create a new Choices column on the Contact table.
Show Answer
Correct Answer: B
Explanation: A dedicated Designation/Certification table with a many-to-many relationship to Contact best models the requirement that each candidate can have multiple designations/certifications and each designation can apply to many candidates. It is the standard Dataverse approach for reusable reference data and supports future expansion beyond a fixed list. A lookup or N:1 relationship would not allow multiple certifications per contact, and a multi-select Choices column is less appropriate for entity-like data that may need its own records or relationships.
Question 125
Case study -
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study -
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Background -
Contoso Pharmaceuticals manufactures and sells drugs to retail and wholesale pharmacies, hospitals, and research facilities.
The company plans to implement Dynamics 365 Sales and Dynamics 365 Finance.
Current environment -
• Contoso maintains a Microsoft Excel workbook that lists all drugs they supply.
• Pharmacies submit order requests through email.
• All information at customer locations is handwritten by customer representatives.
• Contoso uses Cerner, which is a medical industry application that uses a proprietary database.
• Some accounts are referrals from other pharmacies.
• Every pharmacy has its own Dynamics 365 Sales instance.
Requirements -
General -
You must create a model-driven app to meet Contoso’s needs. You must minimize the use of custom code and custom connectors.
Accounts -
• Ensure that the names of the pharmacies are synced between the accounting and the customer management systems.
• Account numbers should be entered automatically into the pharmaceutical system that is in a Cerner database and kept in sync.
• When the account is entered into the system, extra fields must appear if the referral customer box is selected. If the box is not selected, the extra fields must not appear.
• A trigger must be created that changes the Priority field to 1 in the Account record 10 days after an Account record is created.
• A field named Priority_Trigger must be created to trigger the Priority field.
• A field named Facility type field must be added in order to select whether a customer is a retail pharmacy, wholesale pharmacy, research facility, or hospital.
Users -
• UserA must be able to create and publish Power Apps apps.
• UserB must be the owner of all the systems and be able to provide permissions and create all new environments.
• UserC must be able to create apps connected to the systems and update the security roles and entities.
• Pharmacy representatives must only be able to run the apps and access their own records.
• Access to the accounting Power Apps app must be restricted to accounting team members.
• End users must have minimum access to the required systems.
• Only supervisors must be able to view phone numbers in the Accounts form.
• Developers must be able to create new apps for all users.
• Sales users must only have access to their own records.
Reporting -
Pharmacy orders must be displayed in four graphs as follows:
• Annual revenue over $100,000
• Annual revenues under $100,000
• Research facilities
• Hospitals
The graphs must be interactive, and users must be able to drill down on any dimension.
Customizations -
• Ensure that notifications are sent to the sales team when a lead is added by using Slack.
• Ensure that leads have a review stage added to the sales process.
• Doctors must be manually added to a custom entity named Doctor if the doctor is not listed.
• Refill dates for customer prescriptions should be automatically determined and a notification should be sent to the customer.
• Fields for the doctor’s name and phone number must be displayed in the customer record.
• The doctor entered on the customer’s record must be validated against doctors that exist in the system.
• The new solution will be sold to other pharmacies for use. The application must not allow changes to be made.
• The solution must be error free so that when it is installed in other environments it does not cause issues.
Mobile app -
• A custom mobile app must be created to allow salespeople to add or search by pharmacy name.
• Pharmacy records must be uniquely identified by pharmacy name, address, contact name, and phone number.
• When a pharmacy is added by using the mobile app, the phone number must be validated to be all digits.
You need to create an application to deploy to other pharmacies.
What should you do?
A. Clone the solution.
B. Create packages for Package Deployer.
C. Recreate customizations in a new environment.
D. Navigate to Customize the System and export everything to a managed solution.
Show Answer
Correct Answer: B
Explanation: Use Package Deployer packages to distribute a Power Platform/Dynamics 365 application to other organizations in a repeatable, reliable way. A package can include managed solutions along with configuration, data, and deployment logic, making it appropriate for shipping a commercial application. Cloning a solution is for solution lifecycle/versioning, recreating customizations manually is inappropriate, and simply exporting a managed solution does not provide the complete deployment experience described.
Question 126
A company designs a solution that contains a new real-time workflow. The workflow populates a lookup column that has a default value.
A managed solution is imported to the test environment.
An error occurs when a test engineer attempts to create a record. The error message states, "Record is not available."
You need to resolve the error.
What should you do?
A. Add missing lookup table records to the solution.
B. Go to the test environment and manually create missing lookup table records.
C. Use the Configuration Migration Tool to extract the lookup table data from the development environment and import it to the test environment.
Show Answer
Correct Answer: C
Explanation: The workflow's lookup default value depends on reference data existing in the target environment. Managed solutions do not automatically include table data, only metadata. The correct way to move required lookup/reference data between environments is to use the Configuration Migration Tool to export the data from development and import it into the test environment, preserving the necessary relationships. Manually creating records may not preserve the expected references, and simply adding records to the solution is not how data is deployed in managed solutions.
Question 127
HOTSPOT -
You develop the following code for a console application that performs the data import to Microsoft Dataverse.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Show Answer
Correct Answer: Yes
No
No
Explanation: The code writes LastCrmError when the client is not ready. Duplicate detection is enabled for the account create because SuppressDuplicateDetection is false, so a detected duplicate causes that request to fail. ExecuteMultiple has ContinueOnError=false, so processing stops after the first error and the contact is not guaranteed to be created.
Question 128
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution. Determine whether the solution meets the stated goals. Some question sets might have more than once correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
A company designs data integration with an external system by using virtual tables.
You need to implement the virtual tables.
Solution: Create a calculated column on the virtual table.
Does the solution meet the goal?
A. Yes
B. No
Show Answer
Correct Answer: B
Explanation: Virtual tables (virtual entities) do not support calculated or rollup columns. Calculations must be performed in the external data source or by the virtual table data provider, so creating a calculated column on the virtual table does not meet the goal.
Question 129
DRAG DROP
-
Case Study
-
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
-
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. When you are ready to answer a question, click the Question button to return to the question.
Background
-
Proseware, Inc. is an industry leading software company with several thousand employees. The company has had some trouble recruiting talented employees. Top-level candidates interview with the company but go on to work for competitors.
Feedback from candidates show that some offers were not accepted because the interview scheduling process was unpleasant. The company does not have a system to keep track of the candidates that were not selected.
Current Environment
-
The recruiting process starts when an individual applies for a position on the company website. The individual may have found the position on their own, they may have been officially referred by an employee, or in some cases were contacted directly by a hiring manager and encouraged to apply.
Recruiters schedule an interview with a hiring manager and interviews with two senior team members. Each interview results in feedback about the candidate and a recommendation whether to hire or not.
The recruiting team manages all information by using a model-driven application.
The company has the following Microsoft Dataverse tables and columns:
• JobPosting
- Hiring Manager - lookup to SystemUser
- Recruiter Assigned - lookup to SystemUser
• Contact (Job Applicant)
- Contact identifier
- First name
- Last name
- Time-Zone Offset
- Person of Interest - Yes/No (default)
• Application proapplication
- Contact identifier, Contact - lookup to Contact
- Job Posting - lookup to JobPosting
- pro_recruiterassignedid
• Interview
- Application - lookup to Application
- Job Posting - lookup to JobPosting
- Recommend - Choice (Yes (0), No (1), and null (default) are the available values)
- Person of Interest - Yes/No, No is the default value
• Referral
- Contact - lookup to Contact
- Referrer - lookup to SystemUser
- Job Posting - lookup to JobPosting
• SystemUser
- Manager - lookup to SystemUser
- Time-Zone Offset
• Recruiter
- Recruiter identifier
- Recruiter name
Applications
-
There may be multiple applications associated with each job posting. Applications are linked to an employee record if an employee referred the applicant for a position. The same individual can be an applicant for multiple job postings.
Interviews
-
Each interview is performed by an employee and is related to a single application.
The interview scheduling process may force potential candidates to accept interviews at unusual times with the senior team members due to time-zone differences.
Requirements. Interview Scheduling
The system must provide recruiters with a list of team members and their time-zone information. You must create a Microsoft Power Apps Component Framework (PCF) control for the Job Application form to display a list of senior team members who report directly to a hiring manager.
• The control must display the current time in each team member's local time.
• The control must be bound so that it minimizes the amount of code that must be written.
• You must display the list of team members and sort the list to show team members who reside in time zones closest to the applicant's time zone first.
You must develop a second PCF control that displays the time-zone name and current time on the Job Application form. You must display the data in the candidate’s local time.
Requirements. Historical Information Tracking
You must create a process to identify individuals as a person of interest that the company should consider hiring. You must assign each individual a score based on their past interactions.
• You must be able to determine the following information about a candidate:
- The number of interviews in the past two years and whether team members provided recommendations
- The number of hiring manager referrals and employee referrals in the past two years
- Whether the individual has any of the 12 designations or certifications that the company considers significant
• Only a single referral can be made per job application. The system must be able to support multiple referrals for a candidate.
• The system must track referrals even if an application is not completed.
Requirements. Historical Information Scoring
The automated process must run weekly to assess all candidates. The process must also run automatically when historical information is updated. You must be able to perform scoring by selecting a command button on the contact form.
• This new command button must only be visible to employees who belong to a security role assigned named Recruiter. The command button must not be visible to anyone unless the contact form is in Update mode.
• A person of interest is defined as having a score of 15 or more based on the following historical information criteria:
- Each interview with a recommendation adds two to the score.
- Each interview without a recommendation subtracts two from the score.
- Each employee or manager referral adds one to the score.
- Each designation or certification adds one to the score.
• All scoring elements must be recalculated when changes occur. You must assign the score to the Person of interest field.
• Values representing totals or scores must be stored in their own numeric fields.
• Plug-ins must be used to keep the Person of Interest field on active interview records associated with the Contact.
• Plug-ins registered on the update of the Person of interest field must send an email notification when the candidate named in the email is a person of interest. Recruiters must receive the message when the field is updated on the Contact record.
• Interviewers must get an email notification when the Person of Interest field on the interview record is successfully updated.
Requirements. Design Guidelines
The following design guidelines must be followed:
• Schema changes must be made using the method requiring the least amount of storage to meet the requirement.
• Out-of-the-box functionality must be used when possible.
• Any code required to calculate scores must be able to be run from a single point.
• Email notifications need to be kept to a minimum.
Issues
-
• Recruiters report that the command button to score a candidate is not working. You debug the code and observe that the context input parameter is null.
• The system does not support associating designations and certifications with candidates.
• The value for the field used by the PCF control to display local time is saved to Microsoft Dataverse each time an active application record is opened.
• Interviewers report that they do not receive email notifications when interview records are created for an existing person of interest.
You need to implement scoring.
Which methods should you use? To answer, drag the appropriate methods to the correct actions. Each method may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Show Answer
Correct Answer: Initiate process for all individuals. → Power Automate flow
Calculate for a specific individual. → Custom process action and plug-in
Explanation: Use a scheduled/automated Power Automate flow to run weekly and trigger recalculation for all candidates. Centralize the scoring logic in a custom action executed by a plug-in so the same logic can be invoked from the command button for a single contact and from automation, satisfying the requirement for a single calculation point.
Question 130
Case Study -
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study -
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. When you are ready to answer a question, click the Question button to return to the question.
Background -
Proseware, Inc. is an industry leading software company with several thousand employees. The company has had some trouble recruiting talented employees. Top-level candidates interview with the company but go on to work for competitors.
Feedback from candidates show that some offers were not accepted because the interview scheduling process was unpleasant. The company does not have a system to keep track of the candidates that were not selected.
Current Environment -
The recruiting process starts when an individual applies for a position on the company website. The individual may have found the position on their own, they may have been officially referred by an employee, or in some cases were contacted directly by a hiring manager and encouraged to apply.
Recruiters schedule an interview with a hiring manager and interviews with two senior team members. Each interview results in feedback about the candidate and a recommendation whether to hire or not.
The recruiting team manages all information by using a model-driven application.
The company has the following Microsoft Dataverse tables and columns:
• JobPosting
- Hiring Manager - lookup to SystemUser
- Recruiter Assigned - lookup to SystemUser
• Contact (Job Applicant)
- Contact identifier
- First name
- Last name
- Time-Zone Offset
- Person of Interest - Yes/No (default)
• Application proapplication
- Contact identifier, Contact - lookup to Contact
- Job Posting - lookup to JobPosting
- pro_recruiterassignedid
• Interview
- Application - lookup to Application
- Job Posting - lookup to JobPosting
- Recommend - Choice (Yes (0), No (1), and null (default) are the available values)
- Person of Interest - Yes/No, No is the default value
• Referral
- Contact - lookup to Contact
- Referrer - lookup to SystemUser
- Job Posting - lookup to JobPosting
• SystemUser
- Manager - lookup to SystemUser
- Time-Zone Offset
• Recruiter
- Recruiter identifier
- Recruiter name
Applications -
There may be multiple applications associated with each job posting. Applications are linked to an employee record if an employee referred the applicant for a position. The same individual can be an applicant for multiple job postings.
Interviews -
Each interview is performed by an employee and is related to a single application.
The interview scheduling process may force potential candidates to accept interviews at unusual times with the senior team members due to time-zone differences.
Requirements. Interview Scheduling
The system must provide recruiters with a list of team members and their time-zone information. You must create a Microsoft Power Apps Component Framework (PCF) control for the Job Application form to display a list of senior team members who report directly to a hiring manager.
• The control must display the current time in each team member's local time.
• The control must be bound so that it minimizes the amount of code that must be written.
• You must display the list of team members and sort the list to show team members who reside in time zones closest to the applicant's time zone first.
You must develop a second PCF control that displays the time-zone name and current time on the Job Application form. You must display the data in the candidate’s local time.
Requirements. Historical Information Tracking
You must create a process to identify individuals as a person of interest that the company should consider hiring. You must assign each individual a score based on their past interactions.
• You must be able to determine the following information about a candidate:
- The number of interviews in the past two years and whether team members provided recommendations
- The number of hiring manager referrals and employee referrals in the past two years
- Whether the individual has any of the 12 designations or certifications that the company considers significant
• Only a single referral can be made per job application. The system must be able to support multiple referrals for a candidate.
• The system must track referrals even if an application is not completed.
Requirements. Historical Information Scoring
The automated process must run weekly to assess all candidates. The process must also run automatically when historical information is updated. You must be able to perform scoring by selecting a command button on the contact form.
• This new command button must only be visible to employees who belong to a security role assigned named Recruiter. The command button must not be visible to anyone unless the contact form is in Update mode.
• A person of interest is defined as having a score of 15 or more based on the following historical information criteria:
- Each interview with a recommendation adds two to the score.
- Each interview without a recommendation subtracts two from the score.
- Each employee or manager referral adds one to the score.
- Each designation or certification adds one to the score.
• All scoring elements must be recalculated when changes occur. You must assign the score to the Person of interest field.
• Values representing totals or scores must be stored in their own numeric fields.
• Plug-ins must be used to keep the Person of Interest field on active interview records associated with the Contact.
• Plug-ins registered on the update of the Person of interest field must send an email notification when the candidate named in the email is a person of interest. Recruiters must receive the message when the field is updated on the Contact record.
• Interviewers must get an email notification when the Person of Interest field on the interview record is successfully updated.
Requirements. Design Guidelines -
The following design guidelines must be followed:
• Schema changes must be made using the method requiring the least amount of storage to meet the requirement.
• Out-of-the-box functionality must be used when possible.
• Any code required to calculate scores must be able to be run from a single point.
• Email notifications need to be kept to a minimum.
Issues -
• Recruiters report that the command button to score a candidate is not working. You debug the code and observe that the context input parameter is null.
• The system does not support associating designations and certifications with candidates.
• The value for the field used by the PCF control to display local time is saved to Microsoft Dataverse each time an active application record is opened.
• Interviewers report that they do not receive email notifications when interview records are created for an existing person of interest.
You need to determine the cause for the issue reported by the interviewers.
What is the root cause of the issue?
A. There was an error in the event pipeline and the entire transaction was rolled back.
B. There is no plug-in registered to run when an interview record is created.
C. The plug-in used to synchronize the Person of Interest field from Contact to Interview was not triggered.
Show Answer
Correct Answer: C
Explanation: The email to interviewers is triggered by a plug-in registered on updates to the Interview.Person of Interest field. When a new Interview is created for a Contact who is already marked as a Person of Interest, the Contact record is not being updated, so the synchronization plug-in that copies the Contact's Person of Interest value to the Interview record is never triggered. As a result, the Interview.Person of Interest field is not updated after creation, and the email notification plug-in registered on Interview field updates does not execute.
$19
Get all 409 questions with detailed answers and explanations
Instant download HTML + PDF delivered the moment payment clears.
Secure Stripe checkout we never see or store your card details.
7-day refund if files are defective see our refund policy.