Informatica PowerCenter ETL Basics

$PMRootDir IS a root directory used by Informatica server variables - it points to the Integration Service installation directory and is referenced by other server variables like $PMSourceFileDir and $PMTargetFileDir. The statement incorrectly claims it is not a root directory.

Command line programs in Informatica (pmcmd, infacmd) provide MORE functionality than what's available in the Administration Console or Workflow Manager - they allow additional tasks like command-based workflow execution, service management, and batch operations not possible through the GUI tools.

Mapplet input and output ports are created, configured, and viewed in the Mapplet Designer. This is the dedicated development environment for mapplets where you define input/output ports similar to transformations. Repository Manager manages repository objects, Workflow Manager handles workflows and sessions, and Workflow Monitor is for runtime monitoring.

In Informatica mappings, connections must follow the data flow: output ports connect to input ports. Connecting output-to-output or input-to-input violates this flow principle and is invalid. The Designer will not allow such connections, making the statement false.

Informatica transformations have five port types: Input (receive data), Output (pass transformed data), Input/Output (pass through unchanged), Variable (internal temporary storage), and group ports (for aggregator/normalizer). The question lists the four main port types.

In ETL tools like Informatica, a Router transformation is classified as an active transformation because it can change the number of data rows passed through it, specifically by routing rows into multiple target groups based on specified filter conditions.

A Filter transformation evaluates each incoming row against a user-defined condition. If the row satisfies the condition, it is passed through; if not, the row is dropped, meaning it filters out unwanted records from the data flow.

Informatica allows nesting of aggregate functions (like SUM(MAX(salary))) but does NOT allow one aggregate function directly inside another aggregate function - you must use group by ports appropriately. The restriction is on direct nesting, not on using multiple aggregate functions in the same expression.

In Joiner transformation with sorted input, the order of ports in the join condition MUST match the order they were sorted on at the sort origin. If you sorted on port A then port B, your join condition must reference ports in that same sequence (A=B). This is critical for the Joiner to correctly process sorted data.

$PMRootDir IS a root directory used by Informatica server variables - it points to the Integration Service installation directory and is referenced by other server variables like $PMSourceFileDir and $PMTargetFileDir. The statement incorrectly claims it is not a root directory.

Mapplet Designer is the tool where you create, edit, and view mapplets including their input and output ports. Repository Manager manages repository folders, Workflow Manager handles workflows/sessions, and Workflow Monitor monitors execution - none of these show mapplet structure.

In Informatica mappings, data flows from transformations' output ports to downstream transformations' input ports. Connecting output-to-output or input-to-input is invalid because data must flow FROM an output TO an input. Only output-to-input connections are valid.

SQL allows nesting of aggregate functions within aggregate functions, though database engines vary in support. For example, SUM(AVG(column)) is syntactically valid even if not always practical. The statement that only ONE can be nested is incorrect.