70-583 · Question #40
You develop an ASP.NET web application that uses a Windows Azure web role. The application includes a startup script that installs a third-party component. You are developing a test plan for the…
The correct answer is A. Enable Remote Desktop Protocol (RDP) and deploy the application without the startup script. So, here are my thoughts on how you might test an OSS/Azure application...from "easiest" to "best". All of these approaches assume that you are deploying a testing framework and test suite with your application. 1. RDP to staging instance and run command-line tests. This…
Question
You develop an ASP.NET web application that uses a Windows Azure web role. The application includes a startup script that installs a third-party component. You are developing a test plan for the startup script. What should you recommend?
Options
- AEnable Remote Desktop Protocol (RDP) and deploy the application without the startup script.
- BDeploy the application in the Windows Azure Compute Emulator.
- CDeploy the application with a custom error page.
- DDeploy the application and then use IntelliTrace.
How the community answered
(17 responses)- A76% (13)
- C18% (3)
- D6% (1)
Explanation
So, here are my thoughts on how you might test an OSS/Azure application...from "easiest" to "best". All of these approaches assume that you are deploying a testing framework and test suite with your application. 1. RDP to staging instance and run command-line tests. This approach involves enabling RDP access to a deployment (I'm assuming deployment to a staging slot), opening a command prompt, and running your tests as (many of you) normally would. The benefit to this approach is that you likely won't have to deviate much from your normal testing routine. The drawbacks are that you have to manually run your tests and disable RDP access to your instances after you push to production.
Topics
Community Discussion
No community discussion yet for this question.