Testing & Quality Assurance Flashcards

In IDMC, what is the recommended method to test a Mapping Task without affecting production target tables?

Answer: Point the task to a sandbox or staging target environment via environment-specific connections

Using sandbox or staging connections isolates test execution from production data, preventing unintended side effects.

A tester notices that an IDMC mapping produces duplicate target records when rerun after a failure. Which target write strategy should be used to prevent this?

Answer: Upsert (Insert-or-Update)

Upsert checks for existing records and updates them rather than inserting duplicates, making reruns idempotent.

Which IDMC testing best practice reduces the risk of connection failures in automated regression test pipelines?

Answer: Use Named Credentials stored in the org and reference them via parameters

Named Credentials centralize credential management and allow mappings to reference them securely without embedding secrets in the design.

In IDMC, which scheduler option allows a QA team to trigger a task immediately for an ad-hoc test run without modifying its recurring schedule?

Answer: Run Now from the Monitor page

'Run Now' triggers an immediate execution of the task independent of its configured schedule, leaving the recurring schedule unchanged.

What is the purpose of the 'Reject File' in IDMC target configuration during testing?

Answer: To capture rows that could not be written to the target due to errors for later review

The Reject File stores rows that the target rejected due to errors, allowing testers to review and reprocess failed records.

When validating an IDMC API-triggered integration using Application Integration, which tool is most appropriate for sending test HTTP requests and inspecting responses?

Answer: An external REST client such as Postman or curl

External REST clients like Postman or curl allow testers to craft specific HTTP requests, inspect headers, payloads, and status codes independently of the IDMC UI.

In IDMC, what is the key difference between 'Normal' and 'Full' recovery strategies when testing a failed Mapping Task rerun?

Answer: Normal resumes from the last committed checkpoint; Full reruns the entire task from the beginning

Normal recovery resumes processing from the last successful checkpoint, while Full recovery restarts the entire task from scratch regardless of prior progress.