Test Types for Monitoring ASP.NET Web App in Azure
Question
You develop and deploy an ASP.NET web app to Azure App Service.
You use Application Insights telemetry to monitor the app.
You must test the app to ensure that the app is available and responsive from various points around the world and at regular intervals.
If the app is not responding, you must send an alert to support staff.
You need to configure a test for the web app.
Which two test types can you use? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D. E.BC.
There are three types of availability tests: -> URL ping test: a simple test that you can create in the Azure portal.
-> Multi-step web test: A recording of a sequence of web requests, which can be played back to test more complex scenarios.
Multi-step web tests are created in Visual Studio Enterprise and uploaded to the portal for execution.
-> Custom Track Availability Tests: If you decide to create a custom application to run availability tests, the TrackAvailability() method can be used to send the results to Application Insights.
https://docs.microsoft.com/en-us/azure/azure-monitor/app/monitor-web-app-availabilityTo monitor the availability and responsiveness of an ASP.NET web app deployed to Azure App Service, you can configure a test using Application Insights. Application Insights offers different types of tests, and you need to choose the most appropriate type based on your requirements.
Here are the descriptions of the test types and their suitability for the given scenario:
A. Integration Test: Integration tests are used to verify that different components of the application work together correctly. They can simulate user interactions and test the application's behavior in a controlled environment. However, integration tests do not measure the application's availability and responsiveness from different geographic locations. Therefore, integration tests are not suitable for this scenario.
B. Multi-Step Web Test: Multi-step web tests are used to simulate user interactions with the application by visiting multiple pages in a specific sequence. They can measure the application's availability and responsiveness from different geographic locations and provide detailed performance metrics for each step. You can configure multi-step web tests to run at regular intervals and send an alert if the application fails to respond. Therefore, multi-step web tests are a suitable option for this scenario.
C. URL Ping Test: URL ping tests are used to verify that the application's URL is reachable from different geographic locations. They send a simple HTTP request to the URL and check the response code. URL ping tests do not measure the application's responsiveness or simulate user interactions. They can be used as a basic check to ensure that the application's URL is accessible. However, they do not provide detailed performance metrics or simulate user interactions. Therefore, URL ping tests are not suitable for this scenario.
D. Unit Test: Unit tests are used to test individual units or components of the application in isolation. They do not measure the application's availability or responsiveness from different geographic locations. Therefore, unit tests are not suitable for this scenario.
E. Load Test: Load tests are used to simulate heavy user traffic on the application and measure its performance under high load. They can measure the application's availability and responsiveness under high load conditions but do not measure its availability and responsiveness from different geographic locations. Therefore, load tests are not suitable for this scenario.
In summary, the two test types that are suitable for this scenario are Multi-Step Web Test and URL Ping Test. However, Multi-Step Web Test is a more appropriate option as it measures the application's availability and responsiveness from different geographic locations and provides detailed performance metrics for each step.
