Mass Ingestion and Data Synchronization Flashcards
6 cards from real IICS Certification practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 6 Mass Ingestion and Data Synchronization flashcards as text
In IICS Mass Ingestion Databases, which source database types are typically supported for CDC?
Answer: Oracle, SQL Server, MySQL, PostgreSQL, and other major enterprise relational databases
Mass Ingestion Databases supports CDC from major relational databases including Oracle, Microsoft SQL Server, MySQL, and PostgreSQL.
What does 'restart' capability in IICS Mass Ingestion CDC ensure?
Answer: Recovery from the last committed checkpoint so no data is lost or duplicated after a failure
CDC restart checkpointing ensures that after a failure or pause, ingestion resumes from the last committed position, preventing data loss or duplication.
In IICS Data Synchronization tasks, what is 'upsert' mode?
Answer: Inserting new records and updating existing records based on a key match in a single operation
Upsert mode inserts a record if it doesn't exist in the target or updates it if a matching key is found, combining insert and update operations.
Which IICS Mass Ingestion feature lets you monitor real-time ingestion metrics such as rows processed and latency?
Answer: Monitor tab with Mass Ingestion-specific dashboards
The Monitor tab in IICS provides real-time and historical metrics for Mass Ingestion tasks including rows processed, apply latency, and error counts.
In IICS Mass Ingestion, what happens to the target table during an 'initial load and continue with CDC' run mode?
Answer: Target is truncated, fully loaded with source data, then CDC begins capturing ongoing changes
In this mode, Mass Ingestion first performs a full initial load into the target and then automatically transitions to CDC for ongoing change capture.
What is the significance of 'source row ID' tracking in IICS Mass Ingestion CDC?
Answer: It assigns a unique identifier to each change event for deduplication and ordering at the target
Source row IDs uniquely identify each change event, enabling the target system to correctly apply changes in order and deduplicate if needed.