While the correct Azure CLI command is upgrade, it is not offered as an option.

Given the choices, updates is the most plausible selection as it conceptually aligns

with the task of performing an upgrade. The core of the question lies in configuring

the upgrade process. The --max-surge parameter is used to specify the number of

additional buffer nodes created during an upgrade to ensure application availability.

Setting --max-surge 2 directly fulfills the requirement to "Deploy two new nodes to

perform the upgrade," allowing for a controlled, rolling update while managing costs.

Note: The official documentation will refer to the correct command upgrade, which

substantiates the use of the --max-surge parameter as described in the scenario.

1. Azure CLI Documentation for az aks nodepool upgrade: This official

source confirms that the --max-surge parameter is the correct mechanism for

controlling the number of buffer nodes during a node pool upgrade.

o Source: Microsoft Learn, Azure Command-Line Interface (CLI)

Documentation.

o URL: https://learn.microsoft.com/enus/cli/azure/aks/nodepool?view=azure-cli-latest#az-aks-nodepool-

upgrade

o Specific Section: Parameter Set, --max-surge.

2. AKS Cluster and Nodepool Upgrade Concepts: This document explains

the surge upgrade strategy. It clarifies that --max-surge is the setting that

controls how many extra nodes are provisioned to facilitate the upgrade

process, which is central to the question's requirements.

o Source: Microsoft Learn, Azure Kubernetes Service (AKS)

Documentation.

o URL: https://learn.microsoft.com/en-us/azure/aks/upgradecluster#customize-node-surge-upgrade

o Specific Section: "Customize node surge upgrade".