Examkin

Soru

Zorluk: OrtaConfigure Application Insights Web Tests and Availability Monitoring

You are configuring a Standard test in Azure Application Insights to monitor a public HTTP API endpoint. The endpoint requires a custom HTTP header named `X-Auth-Token` containing a static API key to authenticate requests, and it expects an HTTP POST request. You want to ensure the test runs from multiple geographic locations and alerts you if the endpoint becomes unavailable or returns an error status code.

Which of the following statements correctly describes a configuration capability or limitation when setting up this availability test?

  1. Standard tests support custom HTTP headers and the POST verb, but you must enter the static API key value directly in the test configuration because Standard tests do not natively support Azure Key Vault references.Cevap
  2. B
    Standard tests do not support custom HTTP headers, so you must write custom code using the `TelemetryClient.TrackAvailability()` SDK method and deploy it as a scheduled background job.
  3. C
    You can secure the API key in Azure Key Vault and reference it in the Standard test header configuration using the `@Microsoft.KeyVault` syntax, provided you grant the Application Insights resource a Key Vault access policy with Secret Get permissions.
  4. D
    Standard tests can be configured to dynamically adjust their test frequency and location count by associating the availability test with an Azure Monitor autoscale rule.

Cevap

Standard tests support custom HTTP headers and the POST verb, but you must enter the static API key value directly in the test configuration because Standard tests do not natively support Azure Key Vault references.
The correct answer identifies that Standard availability tests natively support configuring custom headers and custom HTTP verbs (like POST) directly in the Azure Portal. However, because they are hosted outside of the application's hosting environment context, they cannot resolve `@Microsoft.KeyVault` references, meaning the auth token secret must be entered as a static value in the test properties.

Adım Adım Çözüm

1
Analyze the requirements for the availability monitoring solution (HTTP POST request, custom headers, and external multi-region probing).
Determine that a Standard availability test fits the basic request requirements because it supports single-URL testing with customized HTTP verbs, custom headers, and request bodies.
Choosing the correct out-of-the-box tool prevents writing unnecessary custom infrastructure code.
2
Evaluate the limitations of Standard web tests regarding secret management.
Acknowledge that Application Insights Standard tests do not support resolving Azure Key Vault reference syntax.
This prevents runtime authentication failures caused by transmitting the literal reference string to the API.
3
Select the option that correctly describes the capability to configure custom headers and POST verbs while highlighting the direct value configuration limitation.
Identify that the option stating Standard tests support these configurations but require direct value entry is correct.
This matches official Azure documentation for Application Insights availability tests.

Anahtar Kavram

Standard availability tests support advanced HTTP configurations (verbs, headers, payloads) but do not support native integration with Azure Key Vault references or dynamic autoscaling.
Bu soruyu puanla

Konular

Configure Application Insights Web Tests and Availability Monitoring