Use a Standard workflow with a parallel state started directly by an EventBridge rule on S3 object creation
A company runs an application that stores artifacts in an Amazon S3 bucket. The application has a large user base. The application writes a high volume of objects to the S3 bucket. The company has enabled event notifications for the S3 bucket. When the application writes an object to the S3 bucket, several processing tasks need to be performed simultaneously. The company's DevOps team needs to create an AWS Step Functions workflow to orchestrate the processing tasks. Which combination of steps should the DevOps team take to meet these requirements with the LEAST operational overhead? (Choose two.)
Community Votes
100% of anonymous learners picked answer AD. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
EventBridge can target a Step Functions state machine directly, so the workflow can be started without a bridging Lambda, which is what minimizes overhead and matches the already-configured S3 event notifications (D). The concurrency requirement maps to a parallel state (A). A Standard workflow is the appropriate type because it supports long-running executions up to one year with durable execution and CloudTrail-based auditability, which suits per-object processing pipelines; a Synchronous Express workflow in option B uses a map state, which iterates over items rather than running tasks in parallel, so it does not express the requirement.
The S3 bucket already emits event notifications and the pipeline must orchestrate several processing tasks that run simultaneously for each object. An EventBridge rule matching new S3 object creation events can start a Step Functions workflow directly through EventBridge target support, so no intermediate Lambda is needed. Within the workflow, a Standard workflow containing a parallel state expresses the concurrent processing tasks, and Standard workflows are the recommended type for long-running, durable, and auditable orchestration.
Using a Synchronous Express workflow with a map state (B) — a map state iterates over an array of items sequentially or with limited concurrency, whereas several tasks must run simultaneously, which requires a parallel state. Adding an extra Lambda between EventBridge and the workflow (C) — EventBridge can invoke a Step Functions workflow directly, so a Lambda adds code and cost without adding capability. Using an Asynchronous Express workflow (part of A) — Express workflows are intended for high-volume, short-duration processing rather than durable long-running orchestration.
Community Discussion (6 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Two requirements drive the design. First, several processing tasks must run simultaneously for each new object, which in Step Functions is expressed with a parallel state; the Standard workflow in option A is the right container because Standard workflows support long-running, durable executions of up to one year with full execution auditability, which suits a per-object processing pipeline (A). Second, the bucket already emits event notifications and the orchestration should start with the least operational overhead: an EventBridge rule matching new S3 object creation events can target a Step Functions state machine directly, so the workflow is started without a Lambda in between (D). A and D together deliver concurrent, event-driven orchestration with no custom bridging code.Why the Other Options Are Wrong
B uses a Synchronous Express workflow containing a map state. A map state iterates over the items of an array, which is not the construct for running several independent tasks at the same time; concurrency across tasks requires a parallel state. Synchronous Express workflows are also limited to five minutes and are intended for high-volume short processing, not durable orchestration. C adds an EventBridge rule that invokes a Lambda function which then starts the workflow. Because EventBridge supports Step Functions state machines as a target directly, the Lambda adds code, cost, and a failure point without adding any capability. The Asynchronous Express workflow mentioned in option A is likewise the wrong workflow type for long-running durable processing. A and D are the correct combination.Community Comment Notes
Community voted A,D (78). teo2157 explained the reasoning in two parts, noting the misspelling in option B and that Standard workflows are recommended for long-running, durable, auditable workflows. luisfsm_111 selected A and D specifically because of the parallel task processing requirement. tinyshare preferred B on the theory that Express suits high volume, but Express workflows do not support the parallel-state construct the requirement needs and are limited to short executions.Official Reference
Related Analysis
Practice All DOP-C02 Questions
Access 85 questions with complete answers and detailed explanations.
View Full DOP-C02 Practice Test →