Informatica ETL and Data Integration Quiz

Informatica PowerCenter supports heterogeneous sources and targets, meaning it can extract data from one type of system or format and load it into a completely different type. This includes different databases, file formats, and applications, making it a powerful ETL tool for data integration across diverse environments.

Repository Manager in Informatica provides capabilities for folder management, user administration with role assignment, and version control operations including folder comparison. However, taking repository backups is typically handled through the Informatica Administration console or database-level tools, not through Repository Manager itself.

PMCMD is the command-line utility in Informatica used to execute workflows from the command prompt or scripts. The Repository server admin console (A) is used for repository administration, not workflow execution. Repository Manager (C) is a client tool for managing repository objects. PMREP (D) is used for repository administration tasks, not workflow execution.

Mapping parameters retain constant values throughout a session once initialized - they don't change during execution. Mapping variables (not parameters) can change values and the server saves them for reuse. Parameters CAN be used in expressions within transformations. The value of a mapping parameter is set at session start and cannot be changed using functions during execution - that's what variables are for.

The Source Qualifier transformation is always required immediately after the source definition in a mapping. It represents the rows that the Integration Service reads from the source and allows you to filter rows or modify data type information. Expression (A), Filter (D), and Target (C) transformations come later in the data flow.

Informatica PowerCenter has its own native data type system that is independent of source or target database data types. The Integration Service transforms source data types to Informatica data types during mapping execution, and then transforms Informatica data types to target data types when writing. This abstraction allows Informatica to work with heterogeneous sources and targets seamlessly.

The Joiner transformation in Informatica does NOT support full outer join. It supports normal join, master outer join, detail outer join, and a few other variants, but not a true full outer join where all records from both sides are included regardless of matches. Left outer (A), right outer (B), and Cartesian product (D) can all be implemented using Joiner transformation with appropriate configuration.

Lookup transformations CAN be used in unconnected mode. In unconnected form, the lookup is called from another transformation using the :LKP expression, and it returns a single value. Connected lookups receive input values directly and return multiple output ports. The statement claiming lookup cannot be unconnected is false.

It IS possible to create header and footer records in target flat files in Informatica. This can be achieved using various methods: using the Union transformation to combine header, data, and footer records from different sources; using Java transformation; or employing target pre/post session SQL commands. The statement is true.

Multiple sessions CAN be executed in parallel in Informatica. You can run sessions concurrently within the same workflow or across different workflows. The Integration Service can handle multiple simultaneous session executions as long as sufficient resources are available. The statement that they cannot be executed in parallel is false.

The Informatica Repository contains metadata for transformations (A), which includes information about transformation logic, ports, properties, and relationships. While source and target schemas are stored in the repository, the option listing source schema alone (B) or target schema alone (C) is incomplete. Option D 'Transformations' is redundant because transformation metadata (A) encompasses the transformation objects themselves.

Informatica supports heterogeneous sources AND targets - meaning it can extract data from different types of source systems (Oracle, SQL Server, flat files, XML, etc.) and load into different types of targets in the same integration. This heterogeneity support is a core feature of Informatica PowerCenter. Options A and B are incorrect because they claim 'only' one side is heterogeneous. Option D is incorrect because it states homogeneous only.

The Stored Procedure transformation allows you to call stored procedures in the target database after the load process, which can include creating indexes. You can configure it to run post-session or on a row-by-row basis. Filter (A) is for conditional filtering. Aggregator (B) performs grouping and aggregation. Expression (D) performs row-level calculations. None of these can execute DDL commands like CREATE INDEX.

The Informatica Repository Server is identified by host name and port number. When connecting to a repository, you specify the machine (host) where the repository server runs and the port it listens on. The repository server NAME alone (B) is insufficient. Host name without port (C) is also insufficient. Repository server name with port (A) is incorrect because the identifying information is host+port, not the repository server's internal name.

Repository Manager in Informatica cannot take backups of the repository. Backup operations are handled through different administrative tools and procedures outside Repository Manager. Creating folders, managing users with roles, and comparing folders are all functions available within Repository Manager.

Repository Agent is a server component, not a client to the Repository Server. It manages repository connections for PowerCenter workflows. Mapping Designer, Informatica Server, and PMREP command all act as clients that connect to and interact with the Repository Server.

PMCMD is the command-line utility used to execute workflows in Informatica PowerCenter. Repository Server Admin Console is for repository administration, Repository Manager is for repository management, and PMREP is for repository administration - none of these execute workflows.

Mapping parameters have a constant value that does not change throughout the entire session execution. This is their defining characteristic - they are set before the session runs and remain fixed. Option B describes mapping variables (not parameters), option C is false (parameters can be used in expressions), and option D is false (parameter values cannot be changed using functions during session runtime).

Source Qualifier transformation must be the first transformation after the source definition when working with flat files in Informatica mappings. It represents the rows that the Integration Service reads from the source when it runs a session. Expression, Filter, and Target transformations come later in the data flow pipeline.

Variable ports in Informatica transformations can only be assigned to output ports within the same transformation. They cannot be assigned to input ports and cannot be directly connected to successive transformations. This is a key constraint of variable port usage and scoping.