###BeginCaseStudy###
Case Study: 3
Mortgage Loan
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 (ARRJ affinity must be disabled for the website.
Solution Structure
The solution structure for the website is shown in the following exhibit.
###EndCaseStudy###
DRAG DROP
You need to create the VM to replace the on-premises server.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list
of actions to the answer area and arrange them in the correct order.
Answer: 
I think the answer is correct, except that it should be STANDARD tier instead.
1. Generalize
2. Connect PwSh to Azure
3. Create new VM
I think it is correct
correct
agreed with davi
https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-create-upload-vhd-windows-server/
agree
i think you need to go to standard before you’d be able to upload a certificate ..
so it i think it should be
configure website to use standard hosting
get a wildcard certificate
select name of domain SSL secures ( that’s where you do the SSL bindings )
https://azure.microsoft.com/en-us/documentation/articles/web-sites-configure-ssl-certificate/
I think you’re correct
Agreed.
1. Generalize
2. Connect PwSh to Azure
3. Create new VM with portal using the generic image.
I agree with Mohamed. Those 3 Actions provide https.
but note that to actually ENFORCE security, one needs to change the webconfig or else the users can still use Http for non MVC Apps. MVC should use require https sucha as
public static void RegisterGlobalFilters(GlobalFilterCollection filters)
{
filters.Add(new HandleErrorAttribute());
filters.Add(new System.Web.Mvc.AuthorizeAttribute());
filters.Add(new RequireHttpsAttribute());
}
Standard
Upload
Select
Standard
Upload Wildcard*
Select
Yes, create the VM from the VHD uploaded to Azure, not Create New VHD.
Generalize
COnnect ps to upload vhd
crate new vm