Automated after-hours shutdown eliminates billable idle compute in a work-hours-only environment

Given a scenario, optimize cloud environments.
Answer Correct answer: C — Automating shutdown after work hours stops all billable compute for the idle window, which access controls alone cannot do.

A cloud solutions architect has an environment that must only be accessed during work hours. Which of the following processes should be automated to best reduce cost?

  1. Scaling of the environment after work hours
  2. Implementing access control after work hours
  3. Shutting down the environment after work hours Correct Answer
  4. Blocking external access to the environment after work hours

Community Votes

C
100%

100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

Cloud compute bills for running state, not for use, so the only way to stop the off-hours cost of an idle-hours environment is to stop the machines.

An environment is only used during work hours, so every off-hours hour of running compute is money spent on nothing. Automating a shutdown after work hours stops the billing meter entirely for those hours, which no access or traffic control can achieve.

Blocking access or implementing access control after hours (B, D) changes who can reach the environment but leaves every VM running and billing at full rate.

Community Discussion (3 comments)

BigM 👍 1 Selected: C
Explanation: Cloud providers charge for compute resources (such as virtual machines, containers, and databases) as long as they are running. To reduce costs, the best approach is to automate the shutdown of the environment when it is not needed (after work hours). ✔ Shutting down the environment ensures that compute resources are not consuming billable usage when they are not actively needed. ✔ Most cloud platforms provide scheduling tools (e.g., AWS Lambda, Azure Automation, Google Cloud Scheduler) to automate start/stop tasks based on time. ✔ This method significantly reduces cloud expenses by eliminating unnecessary resource usage.
54a6b25 👍 1
D. Migrate the data to flash storage Explanation: Flash storage (such as SSDs) offers significantly higher performance and lower latency compared to NL-SAS (Near Line Serial Attached SCSI) storage. Migrating the data to flash storage can address the high application latency issue more effectively than other options. Flash storage provides faster read/write speeds, which can improve the overall performance of the critical application.
Joshuac1392 👍 4 Selected: C
C. Shutting down the environment after work hours Automating the process of shutting down the environment after work hours is the best option to reduce costs in this scenario. By automatically shutting down the environment during non-working hours, the architect can avoid paying for compute resources that are not being utilized. This approach can result in significant cost savings, especially for environments with high resource consumption during working hours and minimal usage during non-working hours.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

Cloud providers charge for compute while instances run, regardless of whether anyone is using them. An environment that must only be accessed during work hours sits idle roughly two-thirds of each day, and scheduled shutdown automation turns that idle time into zero cost. Most providers and orchestrators offer native start/stop schedules, making this both the largest saving and a trivially automatable process.

Why the Other Options Are Wrong

A, scaling the environment down after hours, still leaves some instances running and billing, and scaling workloads that serve no after-hours users wastes more than it saves compared with simply stopping. B, access control after hours, is a security measure that reduces risk but not spend. D, blocking external access, likewise leaves the entire stack powered on and billed while merely filtering traffic that nobody should be sending anyway.

Community Comment Notes

Joshuac1392 explains that automated shutdown avoids paying for compute that is not utilized, delivering significant savings for environments with predictable usage windows. BigM adds that providers bill for VMs, containers, and databases as long as they run, so shutdown is the only option that stops billable usage. The unanimous vote backs C, and 54a6b25's flash-storage comment belongs to a different question entirely.

Related Analysis

← Back to CV0-003 Study Guide