IICS Certification Mass Ingestion and Data Synchronization 2 — Questions and Answers
Question 1: What is 'Data Synchronization' in IICS, and how does it differ from Data Integration mappings?
- Data Synchronization is a wizard-driven task for simple source-to-target sync without coding; Data Integration uses full mapping design (Correct answer)
- Data Synchronization only works with files; Data Integration works with databases
- Data Synchronization runs in real time; Data Integration is batch only
- They are identical features with different names
Correct answer: Data Synchronization is a wizard-driven task for simple source-to-target sync without coding; Data Integration uses full mapping design
Data Synchronization tasks use a simplified wizard interface for straightforward data sync scenarios, while Data Integration provides a full mapping canvas for complex transformations.
Question 2: In IICS Mass Ingestion, what is a 'deployment' and why is it needed?
- A code release of the IICS platform itself
- The step that activates and persists a Mass Ingestion task configuration, making it ready to run (Correct answer)
- A backup of the IICS organization settings
- A test run of the task in sandbox mode
Correct answer: The step that activates and persists a Mass Ingestion task configuration, making it ready to run
Deploying a Mass Ingestion task activates its configuration, creates necessary objects at the target, and prepares it for execution.
Question 3: Which IICS Mass Ingestion option allows you to select specific tables from a source database rather than ingesting all tables?
- Table filters / table selection in the task configuration (Correct answer)
- Custom SQL in the Source transformation
- Schema-level inclusion rules only
- You must ingest all tables and filter at the target
Correct answer: Table filters / table selection in the task configuration
The Mass Ingestion task configuration includes a table selection panel where you can include or exclude specific tables for ingestion.
Question 4: In IICS Mass Ingestion Databases with CDC, what is 'Apply latency'?
- The delay between when a change occurs at the source and when it appears in the target (Correct answer)
- The time it takes to deploy a Mass Ingestion task
- The lag between IICS cloud polling and Secure Agent response
- The timeout for stale connection handling
Correct answer: The delay between when a change occurs at the source and when it appears in the target
Apply latency measures how long it takes for changes captured from the source transaction log to be applied to the target, indicating near-real-time lag.
Question 5: In IICS, what file formats are typically supported for Mass Ingestion Files source inputs?
- Only XML files
- Delimited (CSV), fixed-width, JSON, Parquet, and Avro formats (Correct answer)
- Only Excel spreadsheets (.xlsx)
- Only JSON and YAML
Correct answer: Delimited (CSV), fixed-width, JSON, Parquet, and Avro formats
Mass Ingestion Files supports a range of formats including delimited (CSV), fixed-width, JSON, Parquet, and Avro for source file ingestion.
Question 6: What is the purpose of 'partitioning' in IICS Mass Ingestion for large tables?
- Splitting source data into parallel chunks to improve ingestion throughput (Correct answer)
- Dividing the target table into physical partitions for storage
- Creating backup copies of data at different time points
- Restricting which rows are visible to each user
Correct answer: Splitting source data into parallel chunks to improve ingestion throughput
Partitioning the source table into chunks allows Mass Ingestion to process multiple partitions in parallel, significantly improving throughput for large tables.
IICS Certification Mass Ingestion and Data Synchronization 2
What is 'Data Synchronization' in IICS, and how does it differ from Data Integration mappings?