How to Automatically Provision Tapes in AWS Tape Gateway?
A company has a large on-premises tape backup solution. The company has started to use AWS Storage Gateway. The company created a Tape Gateway to replace the existing on-premises hardware. The company's backup engineer noticed that some of the backup jobs that were supposed to write to AWS failed to run because of a "Not Enough Space" error. The company does not want these failures to happen again. The company also wants to consistently have enough tape available on AWS. What is the MOST operationally efficient way for a CloudOps engineer to meet these requirements?
Community Insight
This question tests whether you know Tape Gateway's built-in auto-create feature; the trap is building a CloudWatch/Lambda remediation loop that reacts only after a backup job has already failed.
AWS Storage Gateway Tape Gateway supports automatic virtual tape creation when free tape capacity falls below a configured minimum. This page explains why enabling tape auto-create with a barcode prefix and tape pool is the most operationally efficient fix for recurring 'Not Enough Space' backup failures.
Many learners pick B because it sounds automated, but it is reactive and operationally heavy; Tape Gateway can create tapes natively before the shortage causes a failure.
Community Discussion (1 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option D uses Tape Gateway's native auto-create capability, which provisions virtual tapes automatically when the configured minimum is reached. The settings named in the option—minimum number of tapes, barcode prefix, and tape pool—are exactly the controls needed to keep a consistent supply of tapes assigned to the correct pool. This directly prevents the 'Not Enough Space' failures without custom code or manual intervention. Because AWS manages the replenishment, it is the most operationally efficient solution among the choices.Why the Other Options Are Wrong
A is a custom hourly poll that could still miss a spike between checks and requires maintaining a Lambda function and threshold logic. B adds CloudWatch agent installation, log shipping, a metric filter, an alarm, and a Lambda function, and it only reacts after the 'Not Enough Space' error has already caused a failed backup. C adds a second Tape Gateway and only sends an SNS notification; it does not automatically provision tapes on the primary gateway and increases cost and management overhead. None of these match the native, preventive behavior of auto-create.Community Comment Notes
The community comment from Bad_Mat endorses D, calling it the "most operationally efficient choice" and identifying the minimum tape count, barcode prefix, and tape pool as the settings to configure. That aligns with the AWS-native behavior of Tape Gateway auto-create. No commenter provided a substantive argument for the Lambda-based or second-gateway options.Official Reference
Exam Strategy
When an AWS service has a native automation feature that directly addresses the stated capacity threshold, prefer it over Lambda/CloudWatch orchestration. Look for keywords such as "operationally efficient" and "consistently have enough tape"—they point to built-in auto-create.
Frequently Asked Questions
Why is a Lambda function that creates tapes on 'Not Enough Space' not the best fix?
It reacts only after a backup job has already failed and adds custom code, logs, and alarms to maintain; Tape Gateway auto-create prevents the shortage natively.
What settings does Tape Gateway auto-create require?
You specify a minimum number of virtual tapes, a barcode prefix, and a tape pool so new tapes are created and assigned before jobs run out of capacity.
Related Analysis
Practice All SOA-C03 Questions
Access 100 questions with complete answers and detailed explanations.
View Full SOA-C03 Practice Test →