Quiz Microsoft-70-532

TESTLET-1. Background You are developing a web-based solution that students and teachers can use to collaborate on written assignments. Teachers can also use the solution to detect potential plagiarism, and they can manage assignments and data by using locally accessible network shares. Business Requirements The solution consists of three parts: a website where students work on assignments and where teachers view and grade assignments, the plagiarism detection service, and a connector service to manage data by using a network share. The system availability agreement states that operating hours are weekdays between midnight on Sunday and midnight on Friday. Plagiarism Service The plagiarism detection portion of the solution compares a new work against a repository of existing works. The initial dataset contains a large database of existing works. Teachers upload additional works. In addition, the service itself searches for other works and adds those works to the repository. Technical Requirements Website The website for the solution must run on an Azure web role. Plagiarism Service The plagiarism detection service runs on an Azure worker role. The computation uses a random number generator. Certain values can result in an infinite loop, so if a particular work item takes longer than one hour to process, other instances of the service must be able to process the work item. Computation results are cached in local storage resources to reduce computation time. Repository of Existing Works The plagiarism detection service works by comparing student submissions against a repository of existing works by using a custom matching algorithm. The master copies of the works are stored in Azure blob storage. A daily process synchronizes files between blob storage and a file share on a virtual machine (VM). As part of this synchronization, the ExistingWorkRepository object adds the files to Azure Cache to improve the display performance of the website. If a student's submission is overdue, the Late property is set to the number of days that the work is overdue. Work files can be downloaded by using the Work action of the TeacherController object Network Connector Clients can interact with files that are stored on the VM by using a network share. The network permissions are configured in a startup task in the plagiarism detection service. Service Monitoring The CPU of the system on which the plagiarism detection service runs usually limits the plagiarism detection service. However, certain combinations of input can cause memory issues, which results in decreased performance. The average time for a given computation is 45 seconds. Unexpected results during computations might cause a memory dump. Memory dump files are stored in the Windows temporary folder on the VM that hosts the worker role. Security Only valid users of the solution must be able to view content that users submit. Privacy regulations require that all content that users submit must be retained only in Azure Storage. All documents that students upload must be signed by using a certificate named DocCert that is installed in both the worker role and the web role. Solution Development You use Microsoft Visual Studio 2013 and the Azure emulator to develop and test both the compute component and the storage component. New versions of the solution must undergo testing by using production data. Scaling During non-operating hours, the plagiarism detection service should not use more than 40 CPU cores. During operating hours, the plagiarism detection service should automatically scale when 500 work items are waiting to be processed. To facilitate maintenance of the system, no plagiarism detection work should occur during non-operating hours. All ASP.NET MVC actions must support files that are up to 2 GB in size. Biographical Information Biographical information about students and teachers is stored in a Microsoft Azure SQL database. All services run in the US West region. The plagiarism detection service runs on Extra Large instances. The Azure worker role must fully utilize all available CPU cores. Solution Structure Relevant portions of the solution 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 the line belongs. Tap the image to zoom Tap the image to zoom Tap the image to zoom Tap the image to zoom Tap the image to zoom Tap the image to zoom Tap the image to zoom

TESTLET-1. Background You are developing a web-based solution that students and teachers can use to collaborate on written assignments. Teachers can also use the solution to detect potential plagiarism, and they can manage assignments and data by using locally accessible network shares. Business Requirements The solution consists of three parts: a website where students work on assignments and where teachers view and grade assignments, the plagiarism detection service, and a connector service to manage data by using a network share. The system availability agreement states that operating hours are weekdays between midnight on Sunday and midnight on Friday. Plagiarism Service The plagiarism detection portion of the solution compares a new work against a repository of existing works. The initial dataset contains a large database of existing works. Teachers upload additional works. In addition, the service itself searches for other works and adds those works to the repository. Technical Requirements Website The website for the solution must run on an Azure web role. Plagiarism Service The plagiarism detection service runs on an Azure worker role. The computation uses a random number generator. Certain values can result in an infinite loop, so if a particular work item takes longer than one hour to process, other instances of the service must be able to process the work item. Computation results are cached in local storage resources to reduce computation time. Repository of Existing Works The plagiarism detection service works by comparing student submissions against a repository of existing works by using a custom matching algorithm. The master copies of the works are stored in Azure blob storage. A daily process synchronizes files between blob storage and a file share on a virtual machine (VM). As part of this synchronization, the ExistingWorkRepository object adds the files to Azure Cache to improve the display performance of the website. If a student's submission is overdue, the Late property is set to the number of days that the work is overdue. Work files can be downloaded by using the Work action of the TeacherController object Network Connector Clients can interact with files that are stored on the VM by using a network share. The network permissions are configured in a startup task in the plagiarism detection service. Service Monitoring The CPU of the system on which the plagiarism detection service runs usually limits the plagiarism detection service. However, certain combinations of input can cause memory issues, which results in decreased performance. The average time for a given computation is 45 seconds. Unexpected results during computations might cause a memory dump. Memory dump files are stored in the Windows temporary folder on the VM that hosts the worker role. Security Only valid users of the solution must be able to view content that users submit. Privacy regulations require that all content that users submit must be retained only in Azure Storage. All documents that students upload must be signed by using a certificate named DocCert that is installed in both the worker role and the web role. Solution Development You use Microsoft Visual Studio 2013 and the Azure emulator to develop and test both the compute component and the storage component. New versions of the solution must undergo testing by using production data. Scaling During non-operating hours, the plagiarism detection service should not use more than 40 CPU cores. During operating hours, the plagiarism detection service should automatically scale when 500 work items are waiting to be processed. To facilitate maintenance of the system, no plagiarism detection work should occur during non-operating hours. All ASP.NET MVC actions must support files that are up to 2 GB in size. Biographical Information Biographical information about students and teachers is stored in a Microsoft Azure SQL database. All services run in the US West region. The plagiarism detection service runs on Extra Large instances. The Azure worker role must fully utilize all available CPU cores. Solution Structure Relevant portions of the solution 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 the line belongs. Tap the image to zoom Tap the image to zoom Tap the image to zoom Tap the image to zoom Tap the image to zoom Tap the image to zoom Tap the image to zoom

TESTLET-2. 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 [email protected] 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. Tap the image to zoom Tap the image to zoom

TESTLET-2. 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 [email protected] 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. Tap the image to zoom Tap the image to zoom

TESTLET-2. 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 [email protected] 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. Tap the image to zoom Tap the image to zoom

TESTLET-2. 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 [email protected] 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. Tap the image to zoom Tap the image to zoom

TESTLET-2. 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 [email protected] 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. Tap the image to zoom Tap the image to zoom

TESTLET-2. 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 [email protected] 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. Tap the image to zoom Tap the image to zoom

TESTLET-2. 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 [email protected] 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. Tap the image to zoom Tap the image to zoom

TESTLET-3. Background A company is developing a website that supports mortgage loan processing. You use the Azure management portal to create a website. You initially configure the website to use the Basic hosting plan. You register a custom domain for the website with a valid registrar. Customers complete mortgage applications and upload supporting documents to the website. A custom executable named FileProcessor.exe processes all of the information received. An on-premises server that runs Windows Server hosts the executable. You create a virtual hard disk (VHD) image of the on-premises server. You plan to use this VHD to replace the on-premises server with a new virtual machine (VM) that is hosted in Azure. Business Requirements Business stakeholders have identified the following requirements for the mortgage loan processing website: - The website must provide a secure mortgage application process for the customer. - Business users must validate new versions of the website before you publish them to the production site. You must be able to revert to the previous version easily when issues arise. - The website must remain available to users while new features and bug fixes are deployed. - Network traffic must be monitored on all ports that the website uses. Technical Requirements General: - You must develop the website by using Microsoft Visual Studio 2013. - The website must be stateless. Subsequent requests from a user might or might not be routed back to the website instance that the user initially connected to. Security: You must secure the custom domain and all subdomains by using SSL. Storage: - The custom executable must use native file system APIs to share data between different parts of the website. - The custom executable must continue to use a network file share to access files. Monitoring: The website must use port 6000 with UDP to submit information to another process. This port must be actively monitored by using the same external port number. Deployment: - You must deploy the VM and the associated VHD. You will need to move this VM to a different Azure subscription after deployment. - You must establish a continuous deployment process that uses staged publishing. - The custom domain must handle requests for multiple subdomains. - The custom domain must use a www CNAME record that points to the domain's @ A record. - The custom executable must run continuously and must be deployed as an Azure web job named FileProcessor - Application Request Routing (ARR) affinity must be disabled for the website. Solution Structure The solution structure for the website is shown in the following exhibit. Tap the image to zoom