B and D are what I'd pick too. Mapping fields (B) and designing the architecture (D) are core steps for actual system integration, not just data handoff. C feels more like a temporary workaround than integration. Pretty sure that's the intent here, but open if someone has seen C used in real projects.
Yeah, definitely B and D. Field mapping (B) is always needed so the two systems actually understand each other, and an architecture diagram (D) is key for planning out how data moves between them. A and C are more about manual handoffs, which isn't real integration in most project contexts. Pretty confident on this, but open if there's an angle I'm missing.
I'd go with C and D for this one. Sometimes teams share files to kick off an integration process before fully automating, and designing the architecture (D) is a must. Not 100 percent sure, but that's what I remember from similar exam questions-agree?