AWS Certified SysOps Administrator – AssociateDeployment, Provisioning, and AutomationMedium
A data analytics team uses AWS Glue for ETL jobs. They need to ensure that new Glue jobs are deployed automatically after code changes are committed to a Git repository, and that job execution can be triggered on a schedule or by data arrival. Which AWS services should be integrated to create this automated deployment and triggering mechanism?
- AAWS CodeCommit, AWS CodePipeline, and AWS Step Functions.
- BAWS CodeCommit, AWS Lambda, and Amazon EventBridge.
- CAWS CodeCommit, AWS CodePipeline, and AWS Glue Triggers.
- DAWS CodeCommit, AWS CodeBuild, AWS CodeDeploy, and AWS Glue Triggers.
Show answer & explanationAnswer & explanation
Correct answer: C. AWS CodeCommit, AWS CodePipeline, and AWS Glue Triggers.
AWS CodeCommit provides the source control. AWS CodePipeline can automate the deployment of Glue job definitions directly from the repository. Once deployed, AWS Glue Triggers can then be configured to initiate the execution of these jobs based on schedules or events like S3 data arrival.
Why the other options are wrong
- A. AWS Step Functions could orchestrate Glue jobs, but CodePipeline is better suited for the *deployment* of the job definition itself.
- B. Lambda and EventBridge could trigger existing Glue jobs, but CodePipeline is the standard for automating the *deployment* of the job definition from source control.
- D. AWS CodeDeploy is typically for deploying applications to EC2, Lambda, or ECS, not directly for Glue job definitions. CodeBuild might be used for testing, but not strictly necessary for deployment of the job definition.
AWS Glue Triggers
Mechanisms within AWS Glue that initiate the execution of Glue jobs or crawlers based on schedules, on-demand, or events.
- Supports time-based schedules (cron).
- Supports event-based triggers (e.g., S3 object creation).
- Can trigger multiple jobs sequentially or in parallel.
Memory trick: Commit, Pipeline, then Glue Triggers align.