A payment system requires events for each individual account to be processed in order. Events for different accounts should be processed concurrently. Producers also need FIFO deduplication for retried sends. Which TWO settings best support this design? (Choose TWO.)

1. Reuse one MessageDeduplicationId for all distinct events produced during a billing cycle.
2. Use an SQS standard queue and assume it guarantees account-level order.
3. Put every payment for every account in the same message group to maximize parallel processing.
4. Use a stable, event-specific MessageDeduplicationId when retrying a send within the deduplication window.
5. Use an SQS FIFO queue and set MessageGroupId to the account identifier.