IICS Certification Mass Ingestion and Data Synchronization 1 — Questions and Answers
Question 1: What is 'Mass Ingestion' in IICS primarily designed for?
- Running complex multi-step orchestration workflows
- High-volume, efficient ingestion of data from databases or files into cloud targets with minimal configuration (Correct answer)
- Designing custom data transformations
- Building REST API endpoints for external consumers
Correct answer: High-volume, efficient ingestion of data from databases or files into cloud targets with minimal configuration
Mass Ingestion is optimized for high-volume bulk data loading from databases or files into cloud data warehouses or data lakes with minimal setup.
Question 2: Which two types of Mass Ingestion tasks does IICS provide?
- Mass Ingestion Files and Mass Ingestion Databases (Correct answer)
- Mass Ingestion Streaming and Mass Ingestion Batch
- Mass Ingestion REST and Mass Ingestion SOAP
- Mass Ingestion Cloud and Mass Ingestion On-Premise
Correct answer: Mass Ingestion Files and Mass Ingestion Databases
IICS offers Mass Ingestion Files (for file-to-cloud loads) and Mass Ingestion Databases (for database-to-cloud loads) as the two primary task types.
Question 3: In IICS Mass Ingestion Databases, what does 'initial load' refer to?
- The first historical bulk load of all data from the source database into the target (Correct answer)
- Loading only the most recent 24 hours of data
- Loading schema metadata without actual row data
- The configuration step before task execution
Correct answer: The first historical bulk load of all data from the source database into the target
An initial load performs a full historical bulk extract of source table data into the target, establishing the baseline dataset.
Question 4: What technology does IICS Mass Ingestion Databases use to capture ongoing changes from the source after the initial load?
- Periodic full table scans
- Change Data Capture (CDC) using database transaction logs (Correct answer)
- Scheduled diff queries using timestamps
- File-based change detection
Correct answer: Change Data Capture (CDC) using database transaction logs
Mass Ingestion Databases uses CDC, reading database transaction logs to capture inserts, updates, and deletes in near real-time after the initial load.
Question 5: Which cloud storage targets are commonly supported by IICS Mass Ingestion Files?
- Only on-premise file systems
- Amazon S3, Azure Data Lake Storage, Google Cloud Storage, and similar cloud object stores (Correct answer)
- Only Salesforce objects
- Only relational databases
Correct answer: Amazon S3, Azure Data Lake Storage, Google Cloud Storage, and similar cloud object stores
IICS Mass Ingestion Files can land data in major cloud object stores including Amazon S3, Azure Data Lake Storage Gen2, and Google Cloud Storage.
Question 6: In IICS Mass Ingestion, what does 'schema drift handling' allow?
- Automatically propagating source schema changes (new columns, type changes) to the target without manual intervention (Correct answer)
- Encrypting sensitive columns before loading to the target
- Reverting schema changes made to the target
- Alerting administrators when source schema changes occur
Correct answer: Automatically propagating source schema changes (new columns, type changes) to the target without manual intervention
Schema drift handling automatically detects and propagates structural changes in the source schema to the target, reducing manual reconfiguration.
