A systems administrator must run a scheduled nightly job from a terminal that stops all development EC2 instances and produces a report of running resources. The steps should be captured in a script that runs the same way every night. Which access method fits this requirement?
Choose one.
The AWS Command Line Interface (AWS CLI) controls AWS services through terminal commands, which can be combined into scripts for repeatable, schedulable administrative automation.
The scenario contains the two classic CLI triggers: an operational task performed from a terminal, and a requirement that it be scripted and run identically every night. The CLI turns each step into a text command, so the whole sequence becomes a script a scheduler can invoke. CloudFormation is the tempting distractor because it is also automation, but it declares infrastructure to provision, not a list of operational actions to run. The Management Console and the Console Mobile Application are manual interfaces for people and cannot be scheduled.
- Identify the actor and context: an administrator working from a terminal.
- Spot the keywords: scheduled, script, runs the same way every time.
- Separate operational commands (CLI) from provisioning templates (CloudFormation).
- Eliminate both console options as manual human interfaces.
Exam tip: Scripted, scheduled administrative tasks from a terminal are the home turf of the AWS CLI.
Deploying and Operating in AWS: Console, CLI, SDKs, IaC, and Connectivity — the lesson that teaches this.