You company has an Azure subscription named Sub1. Sub1 contains an Azure web app named WebApp1 that uses Azure Application Insights. WebApp1 requires users to authenticate by using OAuth 2.0 client…

Question

Options

• AIn Microsoft Visual Studio, modify the .webtest file.
• BUpload the .webtest file to Application Insights.
• CRegister the web test app in Azure AD.
• DAdd a plug-in to the web test app.

• A
  71% (24)
• B
  9% (3)
• C
  15% (5)
• D
  6% (2)

Explanation

Explanation

Modifying the .webtest file in Visual Studio is the first required step because the file must be updated to include the OAuth 2.0 authentication logic (client secrets and token requests) so the synthetic transaction can handle authentication without human interaction - this is what enables the test to run unattended. Before anything else can happen, the test file itself must be properly configured to handle the authentication flow programmatically.

Why the distractors are wrong:

• Option B (Upload to Application Insights) is a subsequent step that comes after the .webtest file has been properly modified - you can't upload a file that isn't configured correctly yet.
• Option C (Register in Azure AD) is not required because the web test app is emulating user traffic, not acting as its own application identity; it uses the existing client secrets already configured for WebApp1.
• Option D (Add a plug-in) may be relevant in some scenarios to extend test functionality, but it is not the first action needed to enable unattended authentication handling.

Memory Tip

Think "Configure before you upload" - just like writing code before deploying it, you must modify the .webtest file to embed authentication credentials first, then upload it to Application Insights. The sequence is: Edit → Upload → Run.

No community discussion yet for this question.