A public cloud provider updated a service with a new type of application load balancer, but the option does not appear in deployment options. What is the most likely reason?

A public cloud provider updated a service with a new type of application load balancer, but the option does not appear in deployment options. What is the most likely reason?

• A. The administrator can deploy the new load balancer via the cloud provider's web console.
• B. The administrator needs to update the version of the CLI tool.
• C. The administrator needs to write a new script function to call this service.
• D. The administrator is not using the correct cloud provider account.

Answer: (B)

Tooling compatibility with the cloud provider’s updated services is what this question is testing. When a new type of application load balancer is released, the platform’s API may support it, but your local tooling (the CLI) must be updated to know how to create and manage that resource. If the new load balancer type doesn’t appear in your deployment commands, the most likely cause is that the CLI version you’re using is outdated and doesn’t include the new resource type, flags, or syntax. Upgrading the CLI brings in the updated API definitions and command set, enabling you to provision the new load balancer. The other possibilities don’t fit as neatly: the web console might show the new option if the UI is updated, but your deployment tooling still relies on the CLI version; writing a new script function isn’t necessary when a simple version upgrade provides the built-in support; and an incorrect account typically causes permission errors or access issues rather than a missing resource type in deployment options.

Tooling compatibility with the cloud provider’s updated services is what this question is testing. When a new type of application load balancer is released, the platform’s API may support it, but your local tooling (the CLI) must be updated to know how to create and manage that resource. If the new load balancer type doesn’t appear in your deployment commands, the most likely cause is that the CLI version you’re using is outdated and doesn’t include the new resource type, flags, or syntax. Upgrading the CLI brings in the updated API definitions and command set, enabling you to provision the new load balancer.

The other possibilities don’t fit as neatly: the web console might show the new option if the UI is updated, but your deployment tooling still relies on the CLI version; writing a new script function isn’t necessary when a simple version upgrade provides the built-in support; and an incorrect account typically causes permission errors or access issues rather than a missing resource type in deployment options.