Plan from the supplied facts
The fictional design permits one software version per writable ledger during transition, with no cross-version bridge. Teams A and B write L1; C writes independent L2. Therefore A/B form one transition group and C can form another. This is a supplied architecture constraint, not a universal deployment rule.
| Team | Writable dataset | Required rollout group |
|---|---|---|
| A | L1 | A + B |
| B | L1 | A + B |
| C | L2 | C |
Work through the choice
A wave containing A alone would leave two writer versions on L1 if B stays old. Splitting C from A/B does not cross a supplied shared ledger.
How many independent transition groups does the supplied model allow?
Show the worked answer
Two: {A,B} and {C}. This partitions the stated shared-data boundary, not actual deployment readiness.
Material to use in your plan
List each team’s writable datasets, connect teams sharing a constrained dataset, then group connected teams. Document any bridge before splitting a group.