###BeginCaseStudy###

Testlet 1
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.

###EndCaseStudy###

You need to implement the web application deployment workflow.
In the Azure management portal, what should you do?

###BeginCaseStudy###

Testlet 1
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.

###EndCaseStudy###

You need to configure session affinity for the website.
Which two actions will achieve the goal? Each correct answer presents a complete solution.

###BeginCaseStudy###

Testlet 1
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.

###EndCaseStudy###

You need to move the VM.
What should you do?

###BeginCaseStudy###

Testlet 1
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.

###EndCaseStudy###

You need to debug the website remotely.
Which three actions should you take? Each correct answer presents part of the solution.

###BeginCaseStudy###

Testlet 1
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.

###EndCaseStudy###

HOTSPOT
You need to implement endpoint monitoring.
What should you do? To answer, configure the appropriate options in the dialog box in the answer area.
Hot Area:

###BeginCaseStudy###

Testlet 1
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 mobileapplications 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.

###EndCaseStudy###

Please see background below for this question.
Background
Contoso, Ltd. is developing a patient monitoring solution for a hospital. The solution consists of an Azure Web
App 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.
You need to implement data storage for patient information.
What should you do?

###BeginCaseStudy###

Testlet 1
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 mobileapplications 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.

###EndCaseStudy###

You need to implement error logging.
Which code segment should you insert at line CF13?

###BeginCaseStudy###

Testlet 1
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 mobileapplications 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.

###EndCaseStudy###

DRAG DROP
Contoso, Ltd. reports that hackers have compromised a computer on its network.
You need to prevent access to the site from all Contoso, Ltd. computers.How should you complete the relevant Windows PowerShell script? To answer, drag the appropriate Windows
PowerShell segment to the correct location. Each Windows PowerShell segment 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.
Select and Place:

###BeginCaseStudy###

Testlet 1
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 mobileapplications 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.

###EndCaseStudy###

You need to implement tracing for the website after the website is deployed.
Which code segment should you insert at line CF13?

###BeginCaseStudy###

Testlet 1
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 mobileapplications 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.

###EndCaseStudy###

HOTSPOT
You configure alerts in Azure. The metrics shown in the following exhibit represent the average values for each
five-minute period.

To answer, make the appropriate selections in the answer area.
Hot Area: