nerdexam
CompTIA

CV0-004 · Question #247

A company's VMs that are created using the noncritical application tag are automatically shut down at 5:00 p.m. using a cronjob. Which of the following actions would allow a cloud engineer to stop…

The correct answer is C. Using the cloud provider command line to stop the Instances based on tags. To efficiently stop unresponsive instances tagged as 'noncritical application' with the least effort if automation fails, a cloud engineer should use the cloud provider's command-line interface (CLI) to filter and stop instances based on their tags.

Operations

Question

A company's VMs that are created using the noncritical application tag are automatically shut down at 5:00 p.m. using a cronjob. Which of the following actions would allow a cloud engineer to stop all unresponsive instances with the least effort in case the automation fails?

Options

  • AUsing the cloud audit logs for tagging and stopping events
  • BUsing the cloud provider web console to check and stop the instances
  • CUsing the cloud provider command line to stop the Instances based on tags
  • DUsing a Bash script to shut down all instances

How the community answered

(30 responses)
  • A
    13% (4)
  • B
    7% (2)
  • C
    77% (23)
  • D
    3% (1)

Why each option

To efficiently stop unresponsive instances tagged as 'noncritical application' with the least effort if automation fails, a cloud engineer should use the cloud provider's command-line interface (CLI) to filter and stop instances based on their tags.

AUsing the cloud audit logs for tagging and stopping events

Cloud audit logs are for monitoring and investigation, not for taking immediate action like stopping instances, and filtering through logs to identify and then stop instances would be time-consuming.

BUsing the cloud provider web console to check and stop the instances

While the web console can be used, manually identifying and stopping multiple unresponsive instances one by one would be more effort than a single CLI command or script, especially if there are many instances.

CUsing the cloud provider command line to stop the Instances based on tagsCorrect

Cloud provider CLIs allow for scripting and filtering resources by tags, which are already in use for identifying 'noncritical application' VMs. This method provides a programmatic way to target and stop multiple unresponsive instances simultaneously with minimal manual intervention, making it the least effort option.

DUsing a Bash script to shut down all instances

A generic Bash script to shut down *all* instances might stop critical ones as well, which is not desired, as the specific context is about 'noncritical application' instances identified by a tag.

Concept tested: Cloud resource management via CLI and tags

Source: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/tag-resources

Topics

#Cloud CLI#Resource Tagging#Instance Management#Operational Efficiency

Community Discussion

No community discussion yet for this question.

Full CV0-004 Practice