An application must debit one DynamoDB item and credit another atomically. It also needs bounded retries without applying the transfer twice. Which choices support this? Select 2 answers.

1. Use TransactWriteItems with conditions that enforce the transfer invariants.
2. Create a fresh transfer identity on every timeout and debit again.
3. Use an appropriate idempotent request identity within the transaction API guarantees and business deduplication requirements.
4. Perform two independent writes and assume they commit or roll back together.
5. Read both balances eventually consistently and skip write conditions.