Read the component meanings
Synthetic campaign has H1 “Explore the evening workshop” paired with O1 evening workshop, and H2 “View the weekend practice” with O2 weekend practice. Local assembly permits those two pairs only.
| Candidate | Headline/offer | Supported |
|---|---|---|
| C1 | H1/O1 | Yes |
| C2 | H2/O2 | Yes |
| C3 | H1/O2 | No |
Select supported pairs
- Identify each component’s offer
- Match against permitted pairs
- Reject C3 cross-pair
- Record C1/C2 tuples
An unknown component remains unmatched; do not infer meaning from a similar filename.
How many candidate assemblies are supported?
Show the worked answer
Two, C1/C2. C3’s evening headline cannot describe the weekend offer under the supplied pairing sheet.
Keep the assembly tuple
| Case | Decision or result | Reason |
|---|---|---|
| Both H1/O2 individually usable | Pair still rejected | Offer association mismatches |
| H2/O2 tuple | Supported | Same weekend subject |
The delivery manifest carries headline ID and offer ID together. A file-count check cannot detect this semantic mismatch.