ICC Testing & Quality Assurance 3 — Questions and Answers
Question 1: During unit testing of an IDMC mapping, a tester discovers that a Lookup transformation returns incorrect results for null keys. What is the best corrective action?
- Enable the 'Return Default Value on No Match' option
- Configure null handling in the Lookup condition or add a default value expression (Correct answer)
- Remove the Lookup and use a Joiner instead
- Increase the Lookup cache size
Correct answer: Configure null handling in the Lookup condition or add a default value expression
Configuring null handling in the Lookup condition or providing default values explicitly prevents unexpected behavior when keys are null.
Question 2: What does the 'Commit Interval' setting control in the context of testing IDMC target writes?
- How often the task writes a checkpoint to the monitor log
- The number of rows written before the target is committed as a transaction batch (Correct answer)
- How frequently the source is re-queried for new data
- The interval between scheduled task runs
Correct answer: The number of rows written before the target is committed as a transaction batch
Commit Interval defines the batch size of rows written before a database commit is issued, affecting transaction granularity and rollback behavior during testing.
Question 3: A QA team needs to verify that an IDMC integration correctly rejects records that violate a NOT NULL constraint on the target. Which approach best tests this scenario?
- Set the target to truncate-insert mode and observe counts
- Inject test records with null values in the required field and confirm rejection in the session log (Correct answer)
- Disable the NOT NULL constraint temporarily during the test
- Run the task in verbose mode without any test data
Correct answer: Inject test records with null values in the required field and confirm rejection in the session log
Injecting known-null records lets testers confirm the mapping correctly handles constraint violations and logs rejected rows.
Question 4: In IDMC Application Integration, what is the purpose of a Service Connector's test connection feature?
- To execute a full end-to-end integration test
- To verify that the configured endpoint URL and credentials are reachable before runtime (Correct answer)
- To generate sample response payloads for mapping
- To measure latency of the target REST service
Correct answer: To verify that the configured endpoint URL and credentials are reachable before runtime
Test connection validates the endpoint URL, authentication credentials, and network reachability without executing any integration logic.
Question 5: Which IDMC feature provides the ability to compare source and target row counts automatically as part of post-load validation?
- Data Validation Option (DVO) (Correct answer)
- Operational Insights
- Advanced Run Properties
- Data Profiling in Monitor
Correct answer: Data Validation Option (DVO)
The Data Validation Option runs automated source-to-target reconciliation checks including row count comparison after a task completes.
Question 6: When testing an IDMC Mapping Task that uses parameterized connections, what must be done before executing a test run?
- Hard-code connection names directly in the mapping
- Provide a Parameter file or set parameter values in the task configuration (Correct answer)
- Remove all parameters and use static connections
- Export the mapping and re-import without parameters
Correct answer: Provide a Parameter file or set parameter values in the task configuration
Parameters must be resolved to real values via a Parameter file or task-level overrides so the runtime knows which actual connection to use.
Question 7: A tester runs an IDMC Mass Ingestion Files task and notices some files were skipped. Where is the best place to investigate the reason for skipped files?
- The Operational Insights dashboard
- The Monitor session log for the specific job run (Correct answer)
- The source file system audit trail
- The target database error table
Correct answer: The Monitor session log for the specific job run
The session log for the Mass Ingestion job run contains file-level status messages including reasons why specific files were skipped.
During unit testing of an IDMC mapping, a tester discovers that a Lookup transformation returns incorrect results for null keys.
What is the best corrective action?