A short guide to the most asked Top Basic IICS CDI Interview Questions and answers.
1. What is Difference Between Informatica PowerCenter (PC) and Informatica Cloud (IICS)?
Informatica PowerCenter is an on-premises ETL tool designed for batch data integration, whereas
Informatica Cloud (IICS) is a cloud-native integration platform that supports data integration, application integration, and API management.
IICS uses Secure Agents to connect on-prem and cloud systems securely, while PowerCenter relies on local servers.
Key Features:
IICS: Cloud-based, subscription model, supports real-time integration, REST/SOAP APIs, and hybrid environments.
PowerCenter: On-prem, license-based, strong for large-scale batch ETL, but lacks native cloud connectors.
2. Where does metadata get stored in IICS?
What is Metadata?
Metadata is a data about data—it describes the structure, properties, and rules of your integration objects. For example, in a mapping, metadata includes source/target definitions, transformation logic, and connection details.
Example:
If you create a mapping to load data from Salesforce to Snowflake, the metadata will store details like field names, data types, transformation rules, and connection parameters.
Why do we really required Metadata if we already have Information about Database?
Database metadata only describes tables and columns inside that database, but IICS needs metadata for integration objects like mappings, taskflows, transformations, and connections across multiple systems.
Example: If you integrate Salesforce with Oracle, IICS must know both schemas, transformation rules, and runtime configurations—not just one database structure
Answer:
In IICS, metadata is stored in the Informatica Cloud repository, which is hosted on Informatica’s cloud servers. This repository maintains all design-time objects like mappings, taskflows, connections, and runtime configurations. Secure Agent only executes jobs—it does not store metadata permanently.
Key Features:
Centralized cloud repository for all integration assets.
Versioning and object history supported.
Accessible via web UI and REST APIs for automation.
3. What system variables are available in IICS to perform Incremental Loading?
In Informatica Intelligent Cloud Services (IICS), use $LastRunTime and $LastRunDate to perform incremental loads using DSS task
$LastRunDate – The last date in GMT time zone when the task runs successfully.
$LastRunTime – The last date and time in GMT time zone when the task runs successfully.
The values of $LastRunDate and $LastRunTime get stored in Informatica Cloud Repository/ Server and we cannot override this values by using Parameters.
Key Features:
Automatically updated by IICS after each successful run.
Useful for CDC (Change Data Capture) and incremental loads without manual tracking.
Can be combined with parameter files for dynamic filtering.
4. What is Secure Agent in IICS?
Secure Agent is a lightweight runtime component installed on your local machine, server, or cloud VM that acts as a bridge between Informatica Intelligent Cloud Services (IICS) and your on-premise or cloud data sources. It ensures secure communication and executes all integration tasks.
✅ Why do we need Secure Agent?
1. IICS is cloud-based, but your data might be on-premises or in private networks.
2. Secure Agent allows IICS to access local data securely without exposing it directly to the internet.
✅ How it works Internally?
Design-time: You create mappings and taskflows in IICS (cloud).
Execution-time: Secure Agent downloads metadata and instructions from IICS.
It runs the job locally, connects to your source/target systems, and sends results back to IICS.
✅Key Features:
Automatic Updates: Always stays in sync with IICS.
Supports Hybrid Integration: Works with both cloud and on-prem systems.
5. Difference between Mapping and Taskflow in IICS?
A Mapping which defines the data flow and transformation logic between source and target systems. Also It includes source objects, transformations (like Expression, Filter, Joiner), and target objects.
Example:
You create a mapping to extract customer data from Database, apply a filter or logic for active customers, and load it into Target System .
And a Taskflow is an orchestration tool that runs one or more tasks (like mappings, data synchronization, scripts) in a sequence or based on conditions. It supports conditional branching, loops, and parallel execution
6. What are the different services available in IICS?
IICS offers multiple services like Cloud Data Integration (CDI) for ETL, Application Integration(CAI) for real-time APIs, API Manager, Data Quality, and Mass Ingestion. Each service addresses different integration needs.
1. Cloud Data Integration (CDI)
Purpose: ETL (Extract, Transform, Load) for batch and real-time data.
Use Case: Move data from flat file/Database to different Target systems with transformations.
Features: Mappings, Taskflows, parameterization, pushdown optimization.
2. Application Integration
Purpose: Real-time integration between applications using APIs.
Use Case: Trigger a workflow when an order is placed in an e-commerce app.
Features: Process Designer, event-driven flows, REST/SOAP connectors.
3. API Manager
Purpose: Manage and monitor APIs created in Application Integration.
Use Case: Secure and publish APIs for external consumption.
4. Data Quality
Purpose: Cleanse, standardize, and validate data before loading.
Features: Profiling, cleansing rules
5. Mass Ingestion
Purpose: High-volume data ingestion from files, databases, or streaming sources.
Use Case: Load millions of records from log files into a data lake.
Features: Batch and streaming ingestion, minimal transformation.
6. Monitor Service
Real-time monitoring of jobs, logs, and resources. Power Center Equivalent: Workflow Monitor.
7. Administrator Console
Manages users, connections, schedules, and runtime environments. PowerCenter Equivalent: Admin Console and Repository Manager.
7. What is the role of Secure Agent services in IICS?
What is Secure Agent?
Secure Agent is the runtime engine installed on your local machine, server, or cloud VM that executes tasks created in IICS. It acts as a bridge between IICS (cloud) and your on-premise or private systems, ensuring secure communication.
For Data Integration Service it Executes mappings and taskflows for ETL jobs. And it Handles transformations and data movement between source and target.
For Process Server it Runs Application Integration processes for real-time workflows and APIs.
For File Transfer Service Manages secure file transfers between systems.
For Mass Ingestion Service it Handles high-volume data ingestion tasks (batch or streaming).
8. Explain the difference between system variables and user-defined parameters in IICS.
System variables are predefined by IICS. They automatically store runtime and additional system variable information about your job or session. You don’t create them, and you can’t edit them—they’re built into the platform.
Why Do We Need System Variable?
It help you access details like Workflowname, CurrentMappingName, CurrentRunId, CurrentTaskId, CurrentTaskName, SESSSTARTTIME, SYSDATE
Key Point: System variables are read-only and populated by IICS during execution.
User-defined parameters are custom variables created by developers. They make your mappings and tasks dynamic and reusable by avoiding hardcoding values.
Why Do We Need user-defined Variable?
Imagine we have multiple environments (Dev, QA, Prod). Instead of changing file paths or table names manually, you can use parameters.
Key Point: You define these in parameter files or at runtime.
9. What are parameter files in IICS and why are they used?
Parameter file is a simple text file that stores values for parameters and variables used in your mappings, tasks, or workflows. Instead of hardcoding values like file paths, table names, or connection details, you define them in this file.
It Store values in key-value pairs as below
| $$Source_File_Path=/data/input/customers.csv $$Target_Table_Name=Customer_Staging |
So why do we use Parameter Files?
1. Parameter files allow you to change values without editing the mapping. For example:
| Move from Dev → QA → Prod by just switching the parameter file. |
2. Reusability
One mapping can work for multiple environments or scenarios by using different parameter files.
3. Easy Maintenance
Instead of searching through mappings for hardcoded values, you update a single file.
10. How to Pass data from one Mapping to Other Mapping in IICS?
When working with Informatica Intelligent Cloud Services (IICS), we often need to design workflows where data processed in one mapping is used by another mapping. This is a common requirement in multi-step ETL processes. So, how we can achieve?
1 . The Mapping Task which passes the data should have in-out parameters defined using SetVariable function in first Mapping
2. The Mapping Task which receives the data should have either an input or in-out parameters defined in other mapping to read the data from upstream task
3. In the advanced task flow, the IO parameter from the second Mapping Task can be set to the value passed by the first Tasks’ IO parameter using an assignment step or by setting the Input fields in the Data Step which triggers the second task.
