A team is preparing a production rollout and needs to avoid a design mistake. What is the best way to handle source integration while staying aligned with the certification objectives?

Here's the deal: this is where a demo turns into an operation. The design has to survive real users, real failures, and real audits. In this scenario, answer A is the practical move because it keeps the implementation tied to the real IBM capability instead of chasing a shortcut. The other choices sound tempting, but they either skip governance, ignore operational reality, or solve the wrong problem.

The correct answer is A. Connect disparate sources through supported connectors, ingestion, or federation based on latency and use-case needs. That aligns with the Domain 4: Data Integration objective because it applies the feature or practice in the context where IBM expects a practitioner to use it. It also keeps the design reviewable, supportable, and realistic for a production environment.

Let's examine why the other options are incorrect: - Option B is incorrect because it uses an overbroad rule instead of matching the design to the actual workload and risk. - Option C is incorrect because it uses an overbroad rule instead of matching the design to the actual workload and risk. - Option D is incorrect because it uses an overbroad rule instead of matching the design to the actual workload and risk. For the exam, connect the feature to the operational outcome: the right answer is the one that preserves control, accuracy, and maintainability instead of relying on a brittle shortcut. The incorrect options ("Manually paste source data into SQL worksheets", "Require all data to be exported as screenshots", "Use only one connector for all source types") are distractors that don't fully capture the concept described.