###BeginCaseStudy###
Testlet 1
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 levelagreement (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###
You need to recommend a solution for publishing one of the company websites to Azure and configuring it for
remote debugging.Which two actions should you perform? Each correct answer presents part of the solution.
A.
From Visual Studio, attach the debugger to the solution.
B.
Set the application logging level to Verbose and enable logging.
C.
Set the Web Server logging level to Information and enable logging.
D.
Set the Web Server logging level to Verbose and enable logging.
E.
From Visual Studio, configure the site to enable Debugger Attaching and then publish the site.
Explanation:
* Scenario:
/ Mitigate the need to purchase additional tools for monitoring and debugging.
/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.
* A: After publishing your application you can use the Server Explorer in Visual Studio to access your web sites.
After signing in you will see your Web Sites under the Windows Azure node in Server Explorer. Right click on
the site that you would like to debug and select Attach Debugger.
D: We need to debug the web site, not an application. We should use the more informative Verbose logging
level.
http://blogs.msdn.com/b/webdev/archive/2013/11/05/remote-debugging-a-window-azure-web-sitewith-visual-studio-2013.aspx
Should be A and E
I think A & D are right
https://docs.microsoft.com/en-us/azure/app-service/web-sites-dotnet-troubleshoot-visual-studio
This article doesn’t say anything about enabling debugger attaching.
It does, however, indicate you attach the debugger and enable verbose logging.
MCEPHIN is correct
From Visual Studio, attach the debugger to the solution.
Set the Web Server logging level to Verbose and enable logging
We need to debug the web site, not an application. We should use the more informative Verbose logging level.
Its A and E isn’t it?? You certainly have to enable debugging and publish before attaching. The wording is slightly different. Tricky
See here:https://docs.microsoft.com/en-us/azure/app-service/web-sites-dotnet-troubleshoot-visual-studio
Remote debugging web apps
1. In Solution Explorer, right-click the project, and click Publish.
2. In the Profile drop-down list, select the same profile that you used in
[Create an ASP.NET web app in Azure][app-service-web-get-started-dotnet.md].
Then, click Settings.
3. In the Publish dialog, click the Settings tab, and then change Configuration
to Debug, and then click Save.
4. Click Publish. After deployment finishes and your browser opens to the Azure
URL of your web app, close the browser.
5. In Server Explorer, right-click your web app, and then click Attach Debugger.