Which of the following Read-only service-defined variables would you use in the AutoScale formula when you want scaling depending upon the number of tasks that are running at a specific point in time?
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: B
$RunningTasks variable should be used while scaling depending upon the number of tasks running at a point in time.
Option A is incorrect.
$ActiveTasks variable is used when scaling depending upon the number of tasks that are queued up to run.
Option B is correct.
$RunningTasks variable should be used when scaling depending upon the number of tasks running at a point in time.
Option C is incorrect.
$SucceededTasks is used for the number of tasks completed successfully.
Option D is incorrect.
$PendingTasks is used for the number of tasks that are queued or running.
To know more about creating automatic formulas, please visit the following link:
In Azure, Autoscale allows you to automatically adjust the number of virtual machines or instances in a cloud service based on metrics such as CPU utilization, memory usage, and other custom metrics.
When defining the Autoscale formula, you can use service-defined variables that represent metrics related to the service, such as the number of active, running, or pending tasks.
In this case, you would want to scale based on the number of tasks that are running at a specific point in time, so the correct read-only service-defined variable to use in the Autoscale formula would be $RunningTasks.
Option A, $ActiveTasks, refers to the total number of tasks that are currently running, regardless of whether they are actively using resources or not.
Option C, $SucceededTasks, refers to the total number of tasks that have completed successfully since the job started, which is not relevant to scaling based on the number of running tasks.
Option D, $PendingTasks, refers to the number of tasks that are waiting to be scheduled and executed, which is also not relevant to scaling based on the number of running tasks.
Therefore, option B, $RunningTasks, is the correct choice for scaling based on the number of running tasks.