You are developing a web-based solution that students and teachers……

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 Existing WorkRepository 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 Teacher Controller 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.







HOTSPOT
You need to implement the Work action on the TeacherController object.
How should you complete the relevant code? To answer, select the appropriate options in the answer area.
Hot Area:

Continue reading “You are developing a web-based solution that students and teachers……”

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.

HOTSPOT
You run the following Windows PowerShell script. Line numbers are included for reference only.

For each of the following statements, select Yes if the statement is true. Otherwise, select No.
Hot Area:


Continue reading “Contoso, Ltd. is developing a patient monitoring solution for a hospital…..”

Developing Microsoft Azure Solution…

Background: You are Developing Microsoft Azure Solution that individuals and small businesses will use to prepare and file tax-related documents.
Business Requirements General: The solution must provide a way for customers to enter personal and demographic information. Customers must be able to upload income documents and related documents to the solution. The solution must provide reports and summary documents for customers in PDF format.
Scope and Device Accessibility: The solution must support two operational modes: On-Peak and Off-Peak. On-Peak is defined as the first quarter of a year. Off-Peak is defined as the other three quarters of a year. Customers must be able to access the solution by using desktop computers, laptop computers, mobile devices, and tablets.
High Availability and Business Continuity: The solution must be available at all times. When the solution transitions between Off-Peak mode and On-Peak mode, solution availability must not be affected. Disaster recovery must be established for the customers’ stored data.
Diagnostics: The solution must log relevant diagnostic data that can be used to troubleshoot the cloud service.
Scalability: The solution must scale out while transitioning from Off-Peak mode to On-Peak mode.
Cost: The solution must use cloud resources optimally to minimize operating costs.
Storage and Security: The solution must be secure to prevent any anonymous access (including read access) to the customers’ tax documents.
Cross-Premises Networking: The solution must extend the developers’ on-premises network into Azure.
Technical Requirements: The logical design for the solution is shown in the following exhibit.

Platform-as-a-Service (PaaS): The solution must have two roles: a web role and worker role. The web interface of the solution uses a web role to accept and send user input and any related documents. The worker role must access the stored data and prepare the tax documents in the background.
Compute: The solution must support a minimum of 10 role instances. When the solution is in On-Peak mode, each role instance must be allocated at least 6 GB of memory. The memory can be scaled down to 3 GB when the solution is in Off-Peak mode.
The solution must cache documents locally. The cache does not need to be refreshed during the lifecycle of the worker role.
Role instances that are running should not be affected by topology changes such as an increase in instance count.
Storage: The web role must store documents in blob storage. A SQL database is used to store customer information.
The worker role must use queues to process the final tax documents.
Performance and Scalability: When the solution is in Off-Peak mode, it must support at least 150 concurrent database sessions, and the maximum size of the database is 50 GB. When the solution is in On-Peak mode, it must support 750 concurrent database sessions, and the maximum size of the database is 300 GB. Geo-replication must be enabled and must be configurable by using the Azure management portal.
Software Prerequisites: The solution must install the software that is necessary to generate PDF documents on the server. The software will be provided as a Windows Installer package.
Debugging: Solution errors and warnings that occur in a web role must be logged. The worker role must log any crash dump files. Detailed information about errors and their context must be collected so that the environment in which errors occurred can be simulated locally.
Security: At the time that a customer’s tax information and documents are accepted, the solution must send an email to the customer. The email contains a secure hyperlink that the customer can use to upload any additional necessary documents. The customer is asked to upload these documents within 48 hours. If the customer does not upload the documents within 48 hours, the solution should not issue a new hyperlink. The solution must send an email to the customer to remind the customer to use the original hyperlink to upload any additional necessary documents.
Network Services: The solution must use a cross-premises secure network. The network must be configurable by using the Azure management portal.
Social 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 they belong.


###EndCaseStudy###
You need to configure diagnostics for the Azure solution.
Which two types of diagnostic data should you collect? Each correct answer presents part of the solution.
A. application logs
B. IIS logs
C. crash dumps
D. trace logs
E. performance counters
F. infrastructure logs
Continue reading “Developing Microsoft Azure Solution…”

You are developing an Azure solution that individuals and small businesses…….

Background: You are developing an Azure solution that individuals and small businesses will use to prepare and file tax related documents.
Business Requirements General: The solution must provide a way for customers to enter personal and demographic information. Customers must be able to upload income documents and related documents to the solution. The solution must provide reports and summary documents for customers in PDF format.
Scope and Device Accessibility: The solution must support two operational modes: On-Peak and Off-Peak. On-Peak is defined as the first quarter of a year. Off-Peak is defined as the other three quarters of a year. Customers must be able to access the solution by using desktop computers, laptop computers, mobile devices, and tablets.
High Availability and Business Continuity: The solution must be available at all times. When the solution transitions between Off-Peak mode and On-Peak mode, solution availability must not be affected. Disaster recovery must be established for the customers’ stored data.
Diagnostics: The solution must log relevant diagnostic data that can be used to troubleshoot the cloud service.
Scalability: The solution must scale out while transitioning from Off-Peak mode to On-Peak mode.
Cost: The solution must use cloud resources optimally to minimize operating costs.
Storage and Security: The solution must be secure to prevent any anonymous access (including read access) to the customers’ tax documents.
Cross-Premises Networking: The solution must extend the developers’ on-premises network into Azure.
Technical Requirements: The logical design for the solution is shown in the following exhibit.

Platform-as-a-Service (PaaS): The solution must have two roles: a web role and worker role. The web interface of the solution uses a web role to accept and send user input and any related documents. The worker role must access the stored data and prepare the tax documents in the background.
Compute: The solution must support a minimum of 10 role instances. When the solution is in On-Peak mode, each role instance must be allocated at least 6 GB of memory. The memory can be scaled down to 3 GB when the solution is in Off-Peak mode.
The solution must cache documents locally. The cache does not need to be refreshed during the lifecycle of the worker role.
Role instances that are running should not be affected by topology changes such as an increase in instance count.
Storage: The web role must store documents in blob storage. A SQL database is used to store customer information.
The worker role must use queues to process the final tax documents.
Performance and Scalability: When the solution is in Off-Peak mode, it must support at least 150 concurrent database sessions, and the maximum size of the database is 50 GB. When the solution is in On-Peak mode, it must support 750 concurrent database sessions, and the maximum size of the database is 300 GB. Geo-replication must be enabled and must be configurable by using the Azure management portal.
Software Prerequisites: The solution must install the software that is necessary to generate PDF documents on the server. The software will be provided as a Windows Installer package.
Debugging: Solution errors and warnings that occur in a web role must be logged. The worker role must log any crash dump files. Detailed information about errors and their context must be collected so that the environment in which errors occurred can be simulated locally.
Security: At the time that a customer’s tax information and documents are accepted, the solution must send an email to the customer. The email contains a secure hyperlink that the customer can use to upload any additional necessary documents. The customer is asked to upload these documents within 48 hours. If the customer does not upload the documents within 48 hours, the solution should not issue a new hyperlink. The solution must send an email to the customer to remind the customer to use the original hyperlink to upload any additional necessary documents.
Network Services: The solution must use a cross-premises secure network. The network must be configurable by using the Azure management portal.
Social 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 they belong.


###EndCaseStudy###
You need to configure the virtual network.
What are two possible ways to achieve this goal? Each correct answer presents a complete solution.
A. Configure a point-to-site virtual network.
B. Configure a site-to-site virtual network.
C. Configure a multi-site virtual network.
D. Configure a cloud-only virtual network.
Continue reading “You are developing an Azure solution that individuals and small businesses…….”

You are developing an Azure solution that individuals and small businesses……

Background: You are developing an Azure solution that individuals and small businesses will use to prepare and file tax related documents.
Business Requirements General: The solution must provide a way for customers to enter personal and demographic information. Customers must be able to upload income documents and related documents to the solution. The solution must provide reports and summary documents for customers in PDF format.
Scope and Device Accessibility: The solution must support two operational modes: On-Peak and Off-Peak. On-Peak is defined as the first quarter of a year. Off-Peak is defined as the other three quarters of a year. Customers must be able to access the solution by using desktop computers, laptop computers, mobile devices, and tablets.
High Availability and Business Continuity: The solution must be available at all times. When the solution transitions between Off-Peak mode and On-Peak mode, solution availability must not be affected. Disaster recovery must be established for the customers’ stored data.
Diagnostics: The solution must log relevant diagnostic data that can be used to troubleshoot the cloud service.
Scalability: The solution must scale out while transitioning from Off-Peak mode to On-Peak mode.
Cost: The solution must use cloud resources optimally to minimize operating costs.
Storage and Security: The solution must be secure to prevent any anonymous access (including read access) to the customers’ tax documents.
Cross-Premises Networking: The solution must extend the developers’ on-premises network into Azure.
Technical Requirements: The logical design for the solution is shown in the following exhibit.

Platform-as-a-Service (PaaS): The solution must have two roles: a web role and worker role. The web interface of the solution uses a web role to accept and send user input and any related documents. The worker role must access the stored data and prepare the tax documents in the background.
Compute: The solution must support a minimum of 10 role instances. When the solution is in On-Peak mode, each role instance must be allocated at least 6 GB of memory. The memory can be scaled down to 3 GB when the solution is in Off-Peak mode.
The solution must cache documents locally. The cache does not need to be refreshed during the lifecycle of the worker role.
Role instances that are running should not be affected by topology changes such as an increase in instance count.
Storage: The web role must store documents in blob storage. A SQL database is used to store customer information.
The worker role must use queues to process the final tax documents.
Performance and Scalability: When the solution is in Off-Peak mode, it must support at least 150 concurrent database sessions, and the maximum size of the database is 50 GB. When the solution is in On-Peak mode, it must support 750 concurrent database sessions, and the maximum size of the database is 300 GB. Geo-replication must be enabled and must be configurable by using the Azure management portal.
Software Prerequisites: The solution must install the software that is necessary to generate PDF documents on the server. The software will be provided as a Windows Installer package.
Debugging: Solution errors and warnings that occur in a web role must be logged. The worker role must log any crash dump files. Detailed information about errors and their context must be collected so that the environment in which errors occurred can be simulated locally.
Security: At the time that a customer’s tax information and documents are accepted, the solution must send an email to the customer. The email contains a secure hyperlink that the customer can use to upload any additional necessary documents. The customer is asked to upload these documents within 48 hours. If the customer does not upload the documents within 48 hours, the solution should not issue a new hyperlink. The solution must send an email to the customer to remind the customer to use the original hyperlink to upload any additional necessary documents.
Network Services: The solution must use a cross-premises secure network. The network must be configurable by using the Azure management portal.
Social 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 they belong.


###EndCaseStudy###
You need to configure role instances.
Which size should you specify for the VM?
A. Use Small for Off-Peak mode.
B. Use Large for On-Peak mode.
C. Use Extra Large for On-Peak mode.
D. Use Extra Small for Off-Peak mode.
Continue reading “You are developing an Azure solution that individuals and small businesses……”

You are developing an Azure solution that individuals and small businesses

Background: You are developing an Azure solution that individuals and small businesses will use to prepare and file tax related documents.
Business Requirements General: The solution must provide a way for customers to enter personal and demographic information. Customers must be able to upload income documents and related documents to the solution. The solution must provide reports and summary documents for customers in PDF format.
Scope and Device Accessibility: The solution must support two operational modes: On-Peak and Off-Peak. On-Peak is defined as the first quarter of a year. Off-Peak is defined as the other three quarters of a year. Customers must be able to access the solution by using desktop computers, laptop computers, mobile devices, and tablets.
High Availability and Business Continuity: The solution must be available at all times. When the solution transitions between Off-Peak mode and On-Peak mode, solution availability must not be affected. Disaster recovery must be established for the customers’ stored data.
Diagnostics: The solution must log relevant diagnostic data that can be used to troubleshoot the cloud service.
Scalability: The solution must scale out while transitioning from Off-Peak mode to On-Peak mode.
Cost: The solution must use cloud resources optimally to minimize operating costs.
Storage and Security: The solution must be secure to prevent any anonymous access (including read access) to the customers’ tax documents.
Cross-Premises Networking: The solution must extend the developers’ on-premises network into Azure.
Technical Requirements: The logical design for the solution is shown in the following exhibit.

Platform-as-a-Service (PaaS): The solution must have two roles: a web role and worker role. The web interface of the solution uses a web role to accept and send user input and any related documents. The worker role must access the stored data and prepare the tax documents in the background.
Compute: The solution must support a minimum of 10 role instances. When the solution is in On-Peak mode, each role instance must be allocated at least 6 GB of memory. The memory can be scaled down to 3 GB when the solution is in Off-Peak mode.
The solution must cache documents locally. The cache does not need to be refreshed during the lifecycle of the worker role.
Role instances that are running should not be affected by topology changes such as an increase in instance count.
Storage: The web role must store documents in blob storage. A SQL database is used to store customer information.
The worker role must use queues to process the final tax documents.
Performance and Scalability: When the solution is in Off-Peak mode, it must support at least 150 concurrent database sessions, and the maximum size of the database is 50 GB. When the solution is in On-Peak mode, it must support 750 concurrent database sessions, and the maximum size of the database is 300 GB. Geo-replication must be enabled and must be configurable by using the Azure management portal.
Software Prerequisites: The solution must install the software that is necessary to generate PDF documents on the server. The software will be provided as a Windows Installer package.
Debugging: Solution errors and warnings that occur in a web role must be logged. The worker role must log any crash dump files. Detailed information about errors and their context must be collected so that the environment in which errors occurred can be simulated locally.
Security: At the time that a customer’s tax information and documents are accepted, the solution must send an email to the customer. The email contains a secure hyperlink that the customer can use to upload any additional necessary documents. The customer is asked to upload these documents within 48 hours. If the customer does not upload the documents within 48 hours, the solution should not issue a new hyperlink. The solution must send an email to the customer to remind the customer to use the original hyperlink to upload any additional necessary documents.
Network Services: The solution must use a cross-premises secure network. The network must be configurable by using the Azure management portal.
Social 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 they belong.


###EndCaseStudy###
You need to meet the performance and scalability requirements.
Which SQL Database configuration should you use?
A. Use the S1 performance level for On-Peak mode.
B. Use the P2 performance level for On-Peak mode.
C. Use the S2 performance level for On-Peak mode.
D. Use the P1 performance level for On-Peak mode.
Continue reading “You are developing an Azure solution that individuals and small businesses”

You are developing an Azure solution that individuals and small businesses……..

Background: You are developing an Azure solution that individuals and small businesses will use to prepare and file tax related documents.
Business Requirements General: The solution must provide a way for customers to enter personal and demographic information. Customers must be able to upload income documents and related documents to the solution. The solution must provide reports and summary documents for customers in PDF format.
Scope and Device Accessibility: The solution must support two operational modes: On-Peak and Off-Peak. On-Peak is defined as the first quarter of a year. Off-Peak is defined as the other three quarters of a year. Customers must be able to access the solution by using desktop computers, laptop computers, mobile devices, and tablets.
High Availability and Business Continuity: The solution must be available at all times. When the solution transitions between Off-Peak mode and On-Peak mode, solution availability must not be affected. Disaster recovery must be established for the customers’ stored data.
Diagnostics: The solution must log relevant diagnostic data that can be used to troubleshoot the cloud service.
Scalability: The solution must scale out while transitioning from Off-Peak mode to On-Peak mode.
Cost: The solution must use cloud resources optimally to minimize operating costs.
Storage and Security: The solution must be secure to prevent any anonymous access (including read access) to the customers’ tax documents.
Cross-Premises Networking: The solution must extend the developers’ on-premises network into Azure.
Technical Requirements: The logical design for the solution is shown in the following exhibit.

Platform-as-a-Service (PaaS): The solution must have two roles: a web role and worker role. The web interface of the solution uses a web role to accept and send user input and any related documents. The worker role must access the stored data and prepare the tax documents in the background.
Compute: The solution must support a minimum of 10 role instances. When the solution is in On-Peak mode, each role instance must be allocated at least 6 GB of memory. The memory can be scaled down to 3 GB when the solution is in Off-Peak mode.
The solution must cache documents locally. The cache does not need to be refreshed during the lifecycle of the worker role.
Role instances that are running should not be affected by topology changes such as an increase in instance count.
Storage: The web role must store documents in blob storage. A SQL database is used to store customer information.
The worker role must use queues to process the final tax documents.
Performance and Scalability: When the solution is in Off-Peak mode, it must support at least 150 concurrent database sessions, and the maximum size of the database is 50 GB. When the solution is in On-Peak mode, it must support 750 concurrent database sessions, and the maximum size of the database is 300 GB. Geo-replication must be enabled and must be configurable by using the Azure management portal.
Software Prerequisites: The solution must install the software that is necessary to generate PDF documents on the server. The software will be provided as a Windows Installer package.
Debugging: Solution errors and warnings that occur in a web role must be logged. The worker role must log any crash dump files. Detailed information about errors and their context must be collected so that the environment in which errors occurred can be simulated locally.
Security: At the time that a customer’s tax information and documents are accepted, the solution must send an email to the customer. The email contains a secure hyperlink that the customer can use to upload any additional necessary documents. The customer is asked to upload these documents within 48 hours. If the customer does not upload the documents within 48 hours, the solution should not issue a new hyperlink. The solution must send an email to the customer to remind the customer to use the original hyperlink to upload any additional necessary documents.
Network Services: The solution must use a cross-premises secure network. The network must be configurable by using the Azure management portal.
Social 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 they belong.


HOTSPOT
You need to insert code at line SB11 to apply the storage access policy.
How should you complete the relevant code segment? To answer, select the appropriate option or options in the answer area.
Hot Area:

Continue reading “You are developing an Azure solution that individuals and small businesses……..”

You are developing an Azure solution that individuals and small businesses……..

Background: You are developing an Azure solution that individuals and small businesses will use to prepare and file tax related documents.
Business Requirements General: The solution must provide a way for customers to enter personal and demographic information. Customers must be able to upload income documents and related documents to the solution. The solution must provide reports and summary documents for customers in PDF format.
Scope and Device Accessibility: The solution must support two operational modes: On-Peak and Off-Peak. On-Peak is defined as the first quarter of a year. Off-Peak is defined as the other three quarters of a year. Customers must be able to access the solution by using desktop computers, laptop computers, mobile devices, and tablets.
High Availability and Business Continuity: The solution must be available at all times. When the solution transitions between Off-Peak mode and On-Peak mode, solution availability must not be affected. Disaster recovery must be established for the customers’ stored data.
Diagnostics: The solution must log relevant diagnostic data that can be used to troubleshoot the cloud service.
Scalability: The solution must scale out while transitioning from Off-Peak mode to On-Peak mode.
Cost: The solution must use cloud resources optimally to minimize operating costs.
Storage and Security: The solution must be secure to prevent any anonymous access (including read access) to the customers’ tax documents.
Cross-Premises Networking: The solution must extend the developers’ on-premises network into Azure.
Technical Requirements: The logical design for the solution is shown in the following exhibit.

Platform-as-a-Service (PaaS): The solution must have two roles: a web role and worker role. The web interface of the solution uses a web role to accept and send user input and any related documents. The worker role must access the stored data and prepare the tax documents in the background.
Compute: The solution must support a minimum of 10 role instances. When the solution is in On-Peak mode, each role instance must be allocated at least 6 GB of memory. The memory can be scaled down to 3 GB when the solution is in Off-Peak mode.
The solution must cache documents locally. The cache does not need to be refreshed during the lifecycle of the worker role.
Role instances that are running should not be affected by topology changes such as an increase in instance count.
Storage: The web role must store documents in blob storage. A SQL database is used to store customer information.
The worker role must use queues to process the final tax documents.
Performance and Scalability: When the solution is in Off-Peak mode, it must support at least 150 concurrent database sessions, and the maximum size of the database is 50 GB. When the solution is in On-Peak mode, it must support 750 concurrent database sessions, and the maximum size of the database is 300 GB. Geo-replication must be enabled and must be configurable by using the Azure management portal.
Software Prerequisites: The solution must install the software that is necessary to generate PDF documents on the server. The software will be provided as a Windows Installer package.
Debugging: Solution errors and warnings that occur in a web role must be logged. The worker role must log any crash dump files. Detailed information about errors and their context must be collected so that the environment in which errors occurred can be simulated locally.
Security: At the time that a customer’s tax information and documents are accepted, the solution must send an email to the customer. The email contains a secure hyperlink that the customer can use to upload any additional necessary documents. The customer is asked to upload these documents within 48 hours. If the customer does not upload the documents within 48 hours, the solution should not issue a new hyperlink. The solution must send an email to the customer to remind the customer to use the original hyperlink to upload any additional necessary documents.
Network Services: The solution must use a cross-premises secure network. The network must be configurable by using the Azure management portal.
Social 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 they belong.


DRAG DROP
You need to insert markup at line SD22 to install the software that generates PDF documents.
How should you complete the relevant markup? To answer, drag the appropriate code segments to the correct locations. Each code 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:

Continue reading “You are developing an Azure solution that individuals and small businesses……..”