← GCDL·Google Cloud

Question 41 of 507

Scaling with Google Cloud operations →hardMultiple ChoiceObjective-mapped

Quick Answer

The correct choice is to build the automation, as eliminating toil permanently is a core SRE principle that prioritizes long-term reliability over short-term effort. The 4-week engineering investment is justified because the manual task consumes 10 hours per month (20 occurrences × 0.5 hours), yielding a payback period of roughly 16 months—after which the team gains indefinite time savings for higher-value reliability work. On the Google Cloud Digital Leader exam, this question tests your understanding of toil reduction as a strategic decision, not a pure cost-benefit analysis; a common trap is overcomplicating the math or fixating on salary data, when the core concept is that any automation that permanently eliminates toil is generally worth pursuing. Remember the SRE toil automation decision hinges on the principle that time saved from toil compounds into improved system resilience. Memory tip: “16 months to break even, then forever free.”

Cloud Digital Leader Scaling with Google Cloud operations Practice Question

This GCDL practice question tests your understanding of scaling with google cloud operations. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A company's SRE team is debating whether to automate a frequently performed manual operational task. The automation would take 4 weeks of engineering time to build. The manual task takes 30 minutes per occurrence and happens approximately 20 times per month. Using the SRE concept of 'toil,' how should the team approach this decision?

Question 1hardmultiple choice

Full question →

A
Do not automate — the manual task is only 10 hours per month and the 4-week build cost is too high to justify
Why wrong: SRE philosophy strongly favors eliminating toil through automation. 10 hours/month of toil is significant, and the automation investment pays back within ~16 months and then provides permanent relief. The long-term value far exceeds the short-term cost.
B
Build the automation: eliminating toil permanently is a core SRE principle, and the 4-week investment pays back within approximately 16 months while freeing engineers for higher-value reliability work indefinitely
This is the SRE-aligned answer. Toil elimination is a core SRE value. The math: 10 hours/month saved, 160 hours invested → 16 month payback. But the more important point is that automation eliminates the toil permanently and scales with service growth, while manual toil grows proportionally. SREs should invest in eliminating toil even with moderate payback periods.
C
Hire an additional junior engineer to perform the manual task more efficiently instead of automating
Why wrong: Hiring more people to do toil is the opposite of SRE philosophy. It scales costs proportionally with growth and doesn't address the root cause. SRE explicitly avoids 'throwing people at the problem' when automation is feasible.
D
The team cannot make this decision without knowing the exact annual salary cost of the engineers who perform the manual task
Why wrong: While cost calculations are relevant, the SRE framework provides a clear principle: eliminate automatable toil. The decision doesn't require precise salary data — the direction (build automation) is clear from SRE principles.

Full breakdown with real-world context →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Build the automation: eliminating toil permanently is a core SRE principle, and the 4-week investment pays back within approximately 16 months while freeing engineers for higher-value reliability work indefinitely

Option B is correct because automating toil aligns with the core SRE principle of eliminating repetitive, manual work to free engineers for higher-value reliability tasks. The 4-week build cost is justified: 20 occurrences/month × 0.5 hours = 10 hours/month, so the payback period is 4 weeks × 40 hours/week ÷ 10 hours/month = 16 months, after which the team gains indefinite time savings. This decision does not require exact salary data, as the primary goal is reducing toil, not purely cost optimization.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Do not automate — the manual task is only 10 hours per month and the 4-week build cost is too high to justify
Why it's wrong here
SRE philosophy strongly favors eliminating toil through automation. 10 hours/month of toil is significant, and the automation investment pays back within ~16 months and then provides permanent relief. The long-term value far exceeds the short-term cost.
✓
Build the automation: eliminating toil permanently is a core SRE principle, and the 4-week investment pays back within approximately 16 months while freeing engineers for higher-value reliability work indefinitely
Why this is correct
This is the SRE-aligned answer. Toil elimination is a core SRE value. The math: 10 hours/month saved, 160 hours invested → 16 month payback. But the more important point is that automation eliminates the toil permanently and scales with service growth, while manual toil grows proportionally. SREs should invest in eliminating toil even with moderate payback periods.
Related concept
Read the scenario before looking for a memorised answer.
✗
Hire an additional junior engineer to perform the manual task more efficiently instead of automating
Why it's wrong here
Hiring more people to do toil is the opposite of SRE philosophy. It scales costs proportionally with growth and doesn't address the root cause. SRE explicitly avoids 'throwing people at the problem' when automation is feasible.
✗
The team cannot make this decision without knowing the exact annual salary cost of the engineers who perform the manual task
Why it's wrong here
While cost calculations are relevant, the SRE framework provides a clear principle: eliminate automatable toil. The decision doesn't require precise salary data — the direction (build automation) is clear from SRE principles.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Cisco often tests the misconception that automation decisions require detailed financial cost analysis (like salary data) rather than the SRE principle of prioritizing toil elimination for long-term reliability gains, leading candidates to pick Option D or A.

Detailed technical explanation

How to think about this question

Under the hood, toil is defined as work that is manual, repetitive, automatable, tactical, and devoid of enduring value—automation reduces the operational burden and error risk. In a real-world scenario, automating a task like database backup verification (30 minutes, 20 times/month) not only saves 10 hours/month but also reduces human error and frees engineers to focus on proactive reliability improvements, such as implementing SLOs and error budgets. The payback period calculation assumes the automation is maintained and does not degrade, which is a subtle risk; teams must also consider the ongoing maintenance cost of the automation code.

KKey Concepts to Remember

Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.

TExam Day Tips

Watch for words such as best, first, most likely and least administrative effort.
Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related GCDL practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Why cloud technology is transforming business practice questions

Practise GCDL questions linked to Why cloud technology is transforming business.

Fundamental cloud concepts practice questions

Practise GCDL questions linked to Fundamental cloud concepts.

Google Cloud products, services, and solutions practice questions

Practise GCDL questions linked to Google Cloud products, services, and solutions.

Scaling with Google Cloud operations practice questions

Practise GCDL questions linked to Scaling with Google Cloud operations.

Trust and security with Google Cloud practice questions

Practise GCDL questions linked to Trust and security with Google Cloud.

GCDL fundamentals practice questions

Practise GCDL questions linked to GCDL fundamentals.

GCDL scenario practice questions

Practise GCDL questions linked to GCDL scenario.

GCDL troubleshooting practice questions

Practise GCDL questions linked to GCDL troubleshooting.

Practice this exam

Start a free GCDL practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

10 questions 20 questions 30 questions 50 questions Timed 30

GCDL practice-test guide →Study guide →Browse all practice tests

FAQ

Questions learners often ask

What does this GCDL question test?

Scaling with Google Cloud operations — This question tests Scaling with Google Cloud operations — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Build the automation: eliminating toil permanently is a core SRE principle, and the 4-week investment pays back within approximately 16 months while freeing engineers for higher-value reliability work indefinitely — Option B is correct because automating toil aligns with the core SRE principle of eliminating repetitive, manual work to free engineers for higher-value reliability tasks. The 4-week build cost is justified: 20 occurrences/month × 0.5 hours = 10 hours/month, so the payback period is 4 weeks × 40 hours/week ÷ 10 hours/month = 16 months, after which the team gains indefinite time savings. This decision does not require exact salary data, as the primary goal is reducing toil, not purely cost optimization.

What should I do if I get this GCDL question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Keep practising

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

This GCDL practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GCDL exam.