Informatica Cloud DI Foundation flashcards
Informatica Cloud DI Foundation · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Secure Agent
- A lightweight Java runtime installed on customer infrastructure that executes Informatica Cloud mappings, tasks, and workflows; the cloud service schedules and monitors but does not execute the job itself.
- Agent group
- A logical set of Secure Agents; a task assigned to a group is dispatched to one member, enabling load balancing and high availability across multiple agents.
- Mapping task
- A runnable object that executes a mapping with its own schedule, parameters, and source/target connections; parameters can be overridden at task level without editing the mapping.
- Replication task
- A task that copies objects from source to target without transformation logic; supports full and incremental load and is used when only data movement is required.
- Synchronization task
- A template-based task that loads a single source object into a target using insert, update, upsert, or delete modes, requiring a key field for update and upsert operations.
- Upsert load mode
- A load operation that inserts new rows and updates existing rows based on a primary key or user-defined key field; the key must be unique in the source to avoid ambiguous updates.
- Taskflow
- An orchestration object that runs multiple tasks in sequence or along conditional paths, with optional notification and assignment steps; a linear taskflow runs steps one after another.
- Elastic mapping
- A mapping whose transformation logic is pushed to a supported database engine such as Snowflake or Redshift, reducing data movement; unsupported functions execute on the Secure Agent.
- Connection object
- A reusable definition holding endpoint, credentials, and Secure Agent group; connections can be parameterized so one mapping targets different environments at runtime.
- Mapping parameter
- A named value referenced in a mapping and supplied at task runtime; it can be a source, target, lookup, or expression parameter, allowing environment-independent mappings.
- Expression transformation
- A transformation that calculates new port values row by row using functions and expressions; it does not change the number of rows passing through.
- Lookup transformation
- A transformation that retrieves values from a lookup source or relational table and returns them to the pipeline; it supports connected and unconnected modes and cached lookup strategies.
- Router transformation
- A transformation that routes rows into multiple output groups based on conditions; rows matching no group go to the default group if one is defined.
- Joiner transformation
- A transformation that joins two pipelines using master and detail sources; supported join types include inner, left outer, right outer, and full outer joins.
- Aggregator transformation
- A transformation that groups rows and computes aggregate values such as sum, count, and average; it requires a group-by port and processes sorted or unsorted input.
- Update strategy transformation
- A transformation that flags each row for insert, update, delete, or reject by setting a numeric code, controlling how the target loading logic treats the row.
- Sequence generator
- A transformation that produces sequential numeric values for a port; it can generate values per mapping run or continue from the current target maximum.
- Rejected rows
- Rows that fail target constraints or transformation errors; they are captured only when a reject file or error-handling target is configured, otherwise the task fails.
- Incremental load
- A load pattern that moves only new or changed records since the last run, typically using a timestamp or change-capture column to filter the source.
- Full load
- A load pattern that reads and writes all source rows on each run; it is simpler but more expensive than incremental load for large tables.
- Pre-session and post-session
- Commands or SQL run before and after the main data flow of a task; used for staging cleanup, index management, or status updates.
- Pushdown optimization
- A technique that converts mapping logic into SQL executed by the source or target database, reducing rows transferred to the Secure Agent.
- Parameter file
- A file that supplies values for mapping parameters and variables at runtime, allowing one task definition to run against different environments or date ranges.
- Mapping variable
- A value stored in the repository that persists across runs and can be used to track high-water marks for incremental loads.
- Source qualifier
- A transformation that represents the source data read by the mapping; it can apply SQL overrides, filters, joins, and sorting before data enters the pipeline.
- Sorter transformation
- A transformation that orders rows by one or more ports; sorted input is required for certain aggregator and joiner configurations to produce correct results.
- Union transformation
- A transformation that merges multiple input pipelines into one output pipeline; all input ports must be compatible in data type and position.
- Normalizer transformation
- A transformation that converts one input row with repeating columns into multiple output rows, commonly used to flatten pivoted or denormalized source data.
- Data type compatibility
- Source and target port data types must be compatible; implicit conversion may occur, but mismatches such as string to date can cause rejected rows or task failure.
- Runtime environment
- The Secure Agent group that executes a task; the connection and runtime environment must reference a group that contains a running agent.
- Task schedule
- A time-based trigger that runs a task or taskflow at defined intervals; schedules are stored in the cloud repository and executed through the assigned agent group.
- Mapping validation
- A check performed before saving or running a mapping that verifies port connectivity, expression syntax, and data type consistency; unresolved errors block task execution.