Q77 — AWS SAA-C03 Ch.16

Question 77 of 100 | ← Chapter 16

Q1277. A company is redesigning its data intake process. In the existing data intake process, the company receives data transfers and uploads the data to an Amazon S3 bucket every night. The company has AWS Glue crawlers and AWS Glue jobs that prepare the data for a machine leaning(ML) workflow.The company needs a low-code solution to run multiple AWS Glue jobs in sequence and provide a visual workflow.Which solution will meet these requirements?

Correct Answer: B. Use Amazon EventBridge to call an AWS Step Functions workflow for the AWS Glue jobs. Use Step Functions to create a visual workflow.

Explanation

The correct solution must provide a low-code, visual workflow to sequence AWS Glue jobs while avoiding manual orchestration. Let's evaluate each option:Correct Answer: B. Use Amazon EventBridge to call an AWS Step Functions workflow for the AWS Glue jobs. Use Step Functions to create a visual workflow.Why Option B is Best:Low-Code Orchestration:AWS Step Functions is a serverless workflow service that allows drag-and-drop visualization of job sequences.No need for custom scripting (unlike EC2, Lambda, or ECS-based solutions).Visual Workflow:Step Functions provides a built-in state machine diagram showing job execution flow, success/failure paths, and retries.Integration with AWS Glue:Step Functions can directly invoke AWS Glue jobs using the AWS Glue StartJobRun API. Supports error handling (e.g., retries, fallbacks) and conditional branching.Event-Driven Trigger:Amazon EventBridge can trigger the Step Functions workflow when new data arrives in S3 (e.g., via an S3 event rule).Why Other Options Fail:A. Use an Amazon EC2 instance to run a cron job and a script to check for the S3 files and call the AWS Glue jobs. Create an Amazon CloudWatch dashboard to visualize the workflow.High Maintenance:Requires manual management of EC2 instances (patching, scaling, uptime).No Native Visual Workflow:CloudWatch dashboards do not show job sequencing--only metrics/logs.Not Low-Code:Requires custom scripting (e.g., Bash/Python) to orchestrate Glue jobs. C. Use S3 Event Notifications to invoke a series of AWS Lambda functions and AWS Glue jobs in sequence. Use Amazon QuickSight to create a visual workflow.Lambda Limitations:Lambda has 15-minute timeout limits, making it unsuitable for long-running Glue jobs. Sequencing multiple Lambdas requires complex event chaining (e.g., SNS/SQS).No Native Workflow Visualization: QuickSight is for BI/analytics, not job orchestration diagrams. D. Create an Amazon Elastic Container Service (Amazon ECS) task that contains a Python script that manages the AWS Glue jobs and creates a visual workflow. Use Amazon EventBridge Scheduler to start the ECS task.Overkill for Low-Code Needs:Requires Docker containerization and Python scripting (not low-code).No Built-in Visualization:ECS does not provide a workflow diagram--requires external tools (e.g., AWS X-Ray, custom dashboards).Key Comparison:RequirementStep Functions (B)Other OptionsLow-code/no-code(Drag-and-drop UI) (Requires scripting/containers) Visual workflow diagram(Built-in state machine) (CloudWatch/QuickSight/ECS lack this) Direct Glue job integration(Native API support) (Lambda timeouts; EC2/ECS need custom code) Event-driven trigger(EventBridge) (S3 Events + Lambda is fragile; EC2 cron jobs)Conclusion:Option B is the only solution that:Provides a serverless, low-code visual workflow (Step Functions).Natively integrates with AWS Glue without scripting.Supports event-driven triggers (EventBridge).Final Answer: B