###BeginCaseStudy###
Case Study: 3
Contoso, Ltd
Background
Overview
Contoso, Ltd., manufactures and sells golf clubs and golf balls. Contoso also sells golf
accessories under the Contoso Golf and Odyssey brands worldwide.
Most of the company’s IT infrastructure is located in the company’s Carlsbad, California,
headquarters. Contoso also has a sizable third-party colocation datacenter that costs the
company USD $30,000 to $40,000 a month. Contoso has other servers scattered around the
United States.
Contoso, Ltd., has the following goals:
• Move many consumer-facing websites, enterprise databases, and enterprise web
services to Azure.
• Improve the performance for customers and resellers who are access company
websites from around the world.
• Provide support for provisioning resources to meet bursts of demand.
• Consolidate and improve the utilization of website- and database-hosting resources.
• Avoid downtime, particularly that caused by web and database server updating.
• Leverage familiarity with Microsoft server management tools.
Infrastructure
Contoso’s datacenters are filled with dozens of smaller web servers and databases that run on
under-utilized hardware. This creates issues for data backup. Contoso currently backs up data
to tape by using System Center Data Protection Manager. System Center Operations Manager
is not deployed in the enterprise.
All of the servers are expensive to acquire and maintain, and scaling the infrastructure takes
significant time. Contoso conducts weekly server maintenance, which causes downtime for
some of its global offices. Special events, such as high-profile golf tournaments, create a
large increase in site traffic. Contoso has difficulty scaling the web-hosting environment fast
enough to meet these surges in site traffic.
Contoso has resellers and consumers in Japan and China. These resellers must use
applications that run in a datacenter that is located in the state of Texas, in the United States.
Because of the physical distance, the resellers experience slow response times and downtime.
Business Requirements
Management and Performance
Management
• Web servers and databases must automatically apply updates to the operating system
and products.
• Automatically monitor the health of worldwide sites, databases, and virtual machines.• Automatically back up the website and databases.
• Manage hosted resources by using on-premises tools.
Performance
• The management team would like to centralize data backups and eliminate the use of
tapes.
• The website must automatically scale without code changes or redeployment.
• Support changes in service tier without reconfiguration or redeployment.
• Site-hosting must automatically scale to accommodate data bandwidth and number of
connections.
• Scale databases without requiring migration to a larger server.
• Migrate business critical applications to Azure.
• Migrate databases to the cloud and centralize databases where possible.
Business Continuity and Support
Business Continuity
• Minimize downtime in the event of regional disasters.
• Recover data if unintentional modifications or deletions are discovered.
• Run the website on multiple web server instances to minimize downtime and support
a high service level agreement (SLA).
Connectivity
• Allow enterprise web services to access data and other services located on-premises.
• Provide and monitor lowest latency possible to website visitors.
• Automatically balance traffic among all web servers.
• Provide secure transactions for users of both legacy and modern browsers.
• Provide automated auditing and reporting of web servers and databases.
• Support single sign-on from multiple domains.
Development Environment
You identify the following requirements for the development environment:
• Support the current development team’s knowledge of Microsoft web development
and SQL Service tools.
• Support building experimental applications by using data from the Azure deployment
and on-premises data sources.
• Mitigate the need to purchase additional tools for monitoring and debugging.
• System designers and architects must be able to create custom Web APIs without
requiring any coding.
• Support automatic website deployment from source control.
• Support automated build verification and testing to mitigate bugs introduced during
builds.
• Manage website versions across all deployments.
• Ensure that website versions are consistent across all deployments.
Technical Requirement
Management and Performance
Management
• Use build automation to deploy directly from Visual Studio.
• Use build-time versioning of assets and builds/releases.• Automate common IT tasks such as VM creation by using Windows PowerShell
workflows.
• Use advanced monitoring features and reports of workloads in Azure by using
existing Microsoft tools.
Performance
• Websites must automatically load balance across multiple servers to adapt to varying
traffic.
• In production, websites must run on multiple instances.
• First-time published websites must be published by using Visual Studio and scaled to
a single instance to test publishing.
• Data storage must support automatic load balancing across multiple servers.
• Websites must adapt to wide increases in traffic during special events.
• Azure virtual machines (VMs) must be created in the same datacenter when
applicable.
Business Continuity and Support
Business Continuity
• Automatically co-locate data and applications in different geographic locations.
• Provide real-time reporting of changes to critical data and binaries.
• Provide real-time alerts of security exceptions.
• Unwanted deletions or modifications of data must be reversible for up to one month,
especially in business critical applications and databases.
• Any cloud-hosted servers must be highly available.
Enterprise Support
• The solution must use stored procedures to access on-premises SQL Server data from
Azure.
• A debugger must automatically attach to websites on a weekly basis. The scripts that
handle the configuration and setup of debugging cannot work if there is a delay in
attaching the debugger.

###EndCaseStudy###

DRAG DROP
You need to recommend network connectivity solutions for the experimental applications.
What should you recommend? To answer, drag the appropriate solution to the correct network
connection requirements. Each solution 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.

Answer:

Explanation:
Box 1: ExpressRoute
ExpressRoute gives you a fast and reliable connection to Azure making it suitable for scenarios like
periodic data migration, replication for business continuity, disaster recovery and other high
availability strategies. It can also be a cost-effective option for transferring large amounts of data
such as datasets for high performance computing applications or moving large VMs between your
dev/test environment in Azure and on-premises production environment.
Box 2: point-to-site VPN
Box 3: point-to-site VPN
A point-to-site VPN also allows you to create a secure connection to your virtual network. In a pointto-site configuration, the connection is configured individually on each client computer that you
want to connect to the virtual network
Box 4: site-to-site VPN
A site-to-site VPN allows you to create a secure connection between your on-premises site and your
virtual network. To create a site-to-site connection, a VPN device that is located on your on-premises
network is configured to create a secure connection with the Azure Virtual Network Gateway. Once
the connection is created, resources on your local network and resources located in your virtual
network can communicate directly and securely. Site-to-site connections do not require you to
establish a separate connection for each client computer on your local network to access resources
in the virtual network.
* Scenario: Support building experimental applications by using data from the Azure deployment
and on-premises data sources.

ExpressRoute, Experience a faster, private connection to Azure
http://azure.microsoft.com/en-us/services/expressroute/
About Virtual Network Secure Cross-Premises Connectivity
https://msdn.microsoft.com/en-us/library/azure/dn133798.aspx