Explain how you would handle a requirement to report across two Salesforce orgs after a merger.

The honest first answer is that cross-org reporting is a symptom; the strategic question is whether the orgs consolidate. Assuming consolidation is not immediate:

1. Short term: Salesforce Connect with the cross-org adapter exposes Org B records as external objects in Org A. Users get contextual visibility with no data copy and no storage cost, and it can be stood up quickly.
2. Its limits: External objects have reporting and aggregation constraints, so this covers 'look up a record' far better than 'analyse the combined pipeline'.
3. For real analytics: Extract both orgs into a data warehouse or a shared analytics layer using Bulk API 2.0 or Change Data Capture, and conform the models there. That is where the cross-org trend reporting genuinely belongs.
4. The hard part is semantics: Two orgs will have different picklist values, different record types, different stage definitions, and different notions of what an Account is. Mapping those is most of the work, and it is a business exercise, not a technical one.
5. Position it as a bridge: I would present this as an interim architecture with an explicit review point, so the organisation does not accidentally standardise on a permanent two-org model by default.