This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
What is the purpose of parameters in Azure Load Testing?
To hard-code values in the test script.
To make the test plan configurable instead of hard-coding values in the test script.
To split the CSV input data evenly across all engine instances.
What is the purpose of the engineInstances key in a load test configuration?
engineInstances
It specifies the number of virtual users in the test script.
It determines the load pattern in the test script.
It specifies the number of parallel test engine instances for running the test plan.
What is the purpose of defining fail criteria in Azure Load Testing?
To define performance and quality expectations for your application under load.
To add test engine instances automatically when a metric exceeds a threshold.
To trigger a load test to start when the error rate surpasses a given threshold.
What is the purpose of using secrets in Azure Load Testing?
To securely pass sensitive information such as web service credentials to the load test engine without hard-coding them in the test script.
To hard-code sensitive information in the test script.
To store nonsensitive information and make it available as environment variables in the load test engine.
A GitHub-hosted workflow must run an Azure load test without storing a client secret. Which authentication configuration meets this requirement?
Store a service principal client secret in the repository and pass it directly to the load test script.
Configure a federated identity credential, grant id-token: write, and use Azure Login with the client, tenant, and subscription IDs.
id-token: write
Assign the Load Test Contributor role to the GitHub repository without configuring a Microsoft Entra identity.
You must answer all questions before checking your work.
Was this page helpful?
Need help with this topic?
Want to try using Ask Learn to clarify or guide you through this topic?