AWS Step Functions State Machine Language Collocations
Practise the standard verbs for building AWS Step Functions state machines.
0 / 5 completed
1 / 5
Fill in: 'We ___ every branch of the state machine explicitly, including the error paths, so a failed step has a defined transition instead of an undefined dead end.'
We 'define a branch' — the standard, simple collocation for specifying a state machine's possible transitions. The other options are less idiomatic here.
2 / 5
Fill in: 'Omitting a catch clause on a risky step can ___ the entire execution failing with an opaque error instead of retrying or routing to a fallback state.'
We say a missing catch clause will 'leave' the execution failing opaquely — the standard, natural collocation for the resulting gap. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ every state machine definition in source control so a console edit can't silently change production workflow behaviour without a reviewable diff.'
We 'version a definition' — the standard, established collocation for tracking a state machine's structure like any other source artefact. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ a new state machine version against sample inputs covering every branch before it replaces the one currently handling live executions.'
We 'test' a version — the standard, simple collocation for validating behaviour before trusting it in production. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ failed executions in the console after an incident to tell a transient downstream timeout apart from a genuine logic error in the workflow.'
We 'inspect' executions — the standard, simple collocation for examining a recorded run's history. The other options are less idiomatic here.