B -- AMPscript can dynamically lookup the subscriber's preferred language and pull the appropriate localized content inside the same email template.
D -- Enhanced Dynamic Content Blocks allow managing different content variations (like languages) efficiently inside Content Builder without duplicating entire templates.

This is a classic transactional use case involving multiple channels: if the password reset email fails to send, the system must fallback to SMS delivery.
The best-practice solution is to:
Use a Transactional Send API for password reset emails.
Use the Event Notification Service (ENS) to monitor delivery or bounce events in near real-time.
Based on failure status, trigger an API call to initiate an SMS message.
D is the only option that uses Salesforce's native ENS and API infrastructure for near real-time failure handling, which meets the requirement for "timely delivery."

In Marketing Cloud, using Email Address as the Subscriber Key can lead to issues with tracking subscriber preferences, especially when integrating with Salesforce via Marketing Cloud Connect.
If the previous send (from the external system) used Email Address as the Subscriber Key, it might not have correctly updated the subscriber's status in the All Subscribers list. Consequently, when MCC sent the email, it treated the subscriber as active, resulting in the email being sent despite the prior unsubscribe.

Because the same Contact/Subscriber record is being reused with a changing Email Address value at send time, standard data views and reports that key off the current subscriber record will not preserve the specific address that was actually used for a given historical send - they reflect present-state data, not point-in-time send detail. Send Logging is the feature purpose-built for this exact requirement: when enabled, it captures a persistent, granular record for every individual send, storing the exact email address (and other attributes) as they existed at the moment of send, independent of any later changes to the subscriber record. That data lands in a queryable Send Log Data Extension the consultant can report from. Data Views (A) reflect current, not historical, attribute values and would show whichever email address is on the record now, not what was used per send. Recent Email Send Report (C) is a high-level send-count summary, not per-subscriber address-level detail. Tracking Extract (D) captures engagement events (opens, clicks) rather than the address used at send time and is not designed to solve the ' which address received which specific send ' problem. Reference: Send Logging, Marketing Cloud Reporting.