###BeginCaseStudy###
Case Study: 4
File Tax-Related Document
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 Azuremanagement 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 PI performance level for On-Peak mode.
P1 should be enough
0
0
agree
0
0
It should be B:
P1 – 250GB storage + 200 concurrent
P2 – 500GB storage + 750 concurrent
Required is 300 GB + 750 concurrent sessions
https://azure.microsoft.com/en-us/documentation/articles/sql-database-service-tiers/#understanding-dtus
0
0
P1 has 500GB and allows for 2400 Max Sessions. RadeK’s values are for Elastic Pool, not the case here. https://azure.microsoft.com/en-gb/documentation/articles/sql-database-service-tiers/.
0
0
Agree. D is correct answer.
0
0