Case Study 5 - Northwind Electric Cars Background Northwind Electric Cars' ride sharing service is growing rapidly. The company is expanding to offer ride sharing in new cities. The company reports…

Case Study 5 - Northwind Electric Cars Background Northwind Electric Cars' ride sharing service is growing rapidly. The company is expanding to offer ride sharing in new cities. The company reports that their ability to perform background checks for potential employees is outpacing the capacity of the human resources (HR) department. The current background check process requires significant manual work. Current Environment The HR department uses a model-driven app to manage candidate information. Regional managers report that it is difficult to determine where a candidate is in the background check process without having to contact HR. The IT department performs all system customizations. Verification process Service providers Each of the third-party services has an API available. Northwind wants to automate the verification process by calling the APIs from a Microsoft Power Platform solution. Each of the third-party services charge per result. Northwind wants to perform the background check processes only when necessary to minimize costs. Cross-origin resource sharing (CORS) is disabled for all three APIs. Requirements. General This project is a top priority for the Northwind. The company has provided time for developers to write code as needed to support the project. Use of Microsoft Azure resources is approved for use if necessary. Requirements. Address verification The system must perform address validation any time an address is added or updated in the model-driven app user interface. Validation must not be performed unless an address is changed. Users must initiate address validation by selecting a button on the command bar. The API must return a version of the address in a uniform format. The returned address must replace the address entered by the user. The API must return an error if the address entered cannot be validated. If the API returns an error, the user must contact the candidate to resolve the issue. The user must re-enter the address information to trigger validation. Requirements. Driving record verification Driving record verification must only be performed once for each candidate. Information required for driving record verification must be sent to the driving record verification service automatically after the candidate's address is verified. The API must return a value of either Approved or Rejected to indicate whether the candidate has met the company's requirements. Requirements. Background check verification Background check verification must be performed only once for each candidate. The candidate's information must be sent to the background check service automatically if the candidate's driving record check is approved. The API must return a submission identification number to the caller. The identification number can be used to return the latest stage information from the service. The API also returns one of ten possible values. The value returned identifies the current stage of the verification process. The returned value may signify whether the candidate is automatically rejected, automatically passed, or calls for further manual investigation. The content and number of stage values is subject to change. The HR department must be able to update the stage values. In cases where further investigation is required, users must manually update the value to reflect the final result. Regional managers must be able to use the model-driven app to identify the current stage of each of the verification processes for any candidate. The solution must include fields for the candidate's record to represent each stage. The solution must connect to the service and update the background check stage for candidates at least once per hour for incomplete background checks. Requirements. Environments Issues. Address verification Users report that the address verification API returns the following error message: The Same Origin Policy disallows reading the remote resource. Issues. Background check verification While reviewing API information for the background check verification process you observe that the API uses an IP address and not a fully-qualified domain name. Code AddressVerificationAPI.js You create a custom action to communicate with the address verification API by using the following code. (Line numbers are included for reference only.) Question You need to connect to the background check API. Which mechanism should you use?