CV0-002 · Question #15
A public cloud provider recently updated one of its services to provide a new type of application load balancer. The cloud administrator is tasked with building out a proof-of-concept using this new…
The correct answer is B. The administrator needs to update the version of the CLI tool. When a cloud provider introduces a new service, administrators automating its deployment must update their CLI tools or SDKs to ensure the new functionalities and service types are recognized and available for scripting.
Question
A public cloud provider recently updated one of its services to provide a new type of application load balancer. The cloud administrator is tasked with building out a proof-of-concept using this new service type. The administrator sets out to update the scripts and notices the cloud provider does not list the load balancer as an available option type for deploying this service. Which of the following is the MOST likely reason?
Options
- AThe administrator can deploy the new load balancer via the cloud provider's web console.
- BThe administrator needs to update the version of the CLI tool.
- CThe administrator needs to write a new script function to call this service.
- DThe administrator is not using the correct cloud provider account.
How the community answered
(29 responses)- A3% (1)
- B90% (26)
- D7% (2)
Why each option
When a cloud provider introduces a new service, administrators automating its deployment must update their CLI tools or SDKs to ensure the new functionalities and service types are recognized and available for scripting.
While the new service might be deployable via the web console, this does not explain why the scripting tools are failing to list the new service option.
Cloud provider CLI tools and SDKs are updated to include support for new services and features. If an administrator is using an older version of the CLI tool, it will not recognize or list the newly released load balancer type, preventing its deployment via scripts until the tool is updated.
The problem is that the cloud provider's CLI tool does not list the new load balancer as an available option, indicating the tool itself lacks the necessary support, not just that a new script function needs to be written for a known option.
Using the wrong cloud provider account typically results in permission errors or inability to see existing resources, but it usually would not prevent the CLI tool from listing generally available service types if the tool itself is up-to-date.
Concept tested: Cloud CLI/SDK versioning and feature support
Source: https://learn.microsoft.com/en-us/cli/azure/install-azure-cli-windows?tabs=azure-cli
Topics
Community Discussion
No community discussion yet for this question.