Contoso, Ltd. is developing a patient monitoring solution for a hospital

Background: Contoso, Ltd. is developing a patient monitoring solution for a hospital. The solution consists of an Azure website and a set of mobile applications that health care providers use to monitor patients remotely.
Monitoring devices that run the embedded version of Windows will be attached to patients. The devices will collect information from patients and will transmit real-time continuous data to a service that runs on Azure. The service collects and distributes data. The data that the service provides must be accessible by the website and by the mobile applications.
Business Requirements Patients: All patient data must be stored securely on Azure. Data security must meet or exceed Health Insurance Portability and Accountability Act of 1996 (HIPAA) standards in the United States and must meet or exceed ISO/ICE 27002 data security standards in the rest of the world.

Contractors: Third-party contractors will develop the mobile applications. All contractors must develop the applications by using virtual machines (VMs) that are hosted on Azure. Only authorized contractors and authorized IP addresses are permitted to access the VMs. The contractors can use Near Field Communication (NFC) tags to launch Remote Desktop (RD) connections to the VMs from NFC-enabled devices. For testing purposes, contractors must be able to run multiple instances of mobile applications within the VMs.

Data Collection and Distribution Service: The service must monitor the patient data and send out alerts to health care providers when specific conditions are detected. The service must send the alerts to mobile applications and to the website in real time so that doctors, nurses, and caregivers can attend to the patient. Partner organizations and diagnostic laboratories must be able to securely access the data and the website from remote locations.
Current Issues: A partner that is testing a prototype of the website reports that after signing in to the website, the partner is redirected to the settings page instead of to the home page.
The data from the patient devices is slow to appear on the website and does not always appear. All patient devices online have active connections to the data collection service.
Technical Requirements Contractors: All contractors will use virtual machines that are initially configured as size A3. Contractors must sign in to the assigned VM by using IP addresses from a list of preapproved addresses.
– Data Collection and Distribution Service
– The service runs Node.js in a worker role.
– The service must use at least 2048-bit encryption and must use port 8888.
– All patient information must be encrypted and stored by using a NoSQL data store.
– Data must be stored and retrieved securely by using RESTful endpoints.
– Data must NOT be stored within a virtual machine.
All deployed services must send an alert email to watchguard@contoso.com when any of the following conditions is met:
– The CPU Percentage metric is at or above 85 percent for at least 10 minutes.
– The Network In metric is at or above 2 KB for at least 10 minutes.
– The Network Out metric is at or above 2 KB for at least 10 minutes.
– The Disk Write metric is at or above 1 KB/sec for at least 30 minutes.
– The Disk Read metric is at or above 1 KB/sec for at least 30 minutes.
Website and Mobile Devices: The website must be secure and must be accessible only within the hospital’s physical grounds. All mobile applications and websites must be responsive. All websites must produce error logs that can be viewed remotely.
Virtual Machines: All Azure instances must be deployed and tested on staging instances before they are deployed to production instances.
All deployed instances must scale up to the next available CPU instance at a CPU usage threshold of 90 percent and scale down when the usage is below 10 percent.
Application Structure: Relevant portions of the application files are shown in the following code segments. Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.
All Deployed instances
You need to implement data storage for patient information.
What should you do?
A. Use the Update Entity operation of the Table Service REST API.
B. Use the Put Blob operation of the Blob Service REST API.
C. Use the Put Message operation of the Create Queue REST API.
D. Use the Set Share Metadata operation of the File Service REST API.

ase studies are not timed separately. You can use as much exam time as you would like to complete each case

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 question on 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 sections 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 on 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 you are a developer for LitWare, Inc., a game development company. You are developing a backend service for an online social gaming platform named GamerData. The game is built around point generators, which are associated with physical landmarks. Players claim point generators which give them a set amount of points per day.

Business Requirements Mobile App The game itself runs on various mobile devices and is developed by Tailspin Toys, a company that specializes in mobile game development.
The mobile app will periodically make calls to the GamerData service to find thefive closest point generators that are located less than the specified distance from the player’s current location. If no point generators are found, the search distance increases until one is found. The mobile app shows all the point generators owned by each player.

The mobile app allows for each player to search for claimed point generators by player name. This search does not require exact spelling of names. The details for each claimed generator is shown in the app.

When a player claims a point generator, they should receive an email notification. An Azure Function named EmailPlayer has been developed to email players with details about recently claimed point generators.

Sponsors: The platform allows business to sponsor point generators within a business location.

Reports: A report named Daily Sponsor Report must be generated each day at midnight. The report must contain a section for each sponsor. Each sponsor section must contain two subsections.
The first subsection of the report contains the names of the point generators for that sponsor, ordered by the last time the point generator was claimed. The second subsection contains the current owners for each of the point generators for the sponsor. Generation of reports must not impact the GamerData service.

Technical Requirements:
GamerData Service all data for the GamerData service is stored in an Azure DocumentDB instance named GamerData. Business and players interact with the service by using a REST API.

The REST API must:
Produce valid Swagger API specifications for non-obsolete actions. Be optimized for loading specific point generators. Follow REST best practices. Include appropriate terms of service. Costs for all Azure services must be minimized.

Build and Deployment the GamerData service will be deployed to Azure in a private VNet. Security
Sponsors have accounts in an Azure Active Directory (Azure AD) with business-to-consumer (B2C) enabled named litwaregamerdata.onmicrosoft.com managed by Litware, Inc. for both GamerData and LitWare, Inc. services.

Only Litware, Inc. developers and automated testing tools should be able to directly access the GamerData service.

All other use of the service must be through Azure API Management. A description of the security practices used during development, available on Microsoft SharePoint, must be available to users of the API under the terms of service.
Reporting Azure Search will be used as the source for running reports. The properties of indexes in Azure Search must match the names of the properties in DocumentDB.
Performance The Azure DocumentDB must not be used for reporting purposes. All services must perform queries in the data store when possible.

Application Structure Startup.cs Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)Build and DeplomentPointController.cs
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)
Application structurePointGenerator.cs
Relevant portions of the app files are shown below. (Line numbers in the code segments are included for reference only and include a two-character prefix that denotes the specific file to which they belong.)PointGenerator
You need to build a Swagger specification for creating the GamerData managed API. What should you do? To answer, select the appropriate options in the answer area.
Hot Area:
build a Swagger