Informatica PowerCenter and Programming Quiz

In Informatica Workflow Manager, Email, Session, and Timer are all valid task types. Workflow itself is not a task - it is the container that holds and orchestrates tasks. Therefore, 'Workflow' is the correct answer as it is not a task type.

In Informatica, an Active transformation changes the number of rows passing through it. The Sorter transformation is active because it can change the row order and, based on configuration, can filter rows (like using 'distinct' sort which removes duplicates). Lookup (both connected and unconnected) and Expression are passive transformations as they maintain the same number of rows.

The Source Qualifier transformation in Informatica PowerCenter can read data from relational databases, flat files, COBOL files, and certified external ERP sources like SAP R/3 and PeopleSoft.

Designer in Informatica PowerCenter allows you to run the Debugger to validate mappings and mapplets, and import source definitions from various sources. Creating and deleting folders is a Repository Manager function, not Designer. Creating target tables is typically done in the Target Designer or Warehouse Builder tool, not the main Designer interface.

Expression transformation is a passive transformation that only has input and output ports - no input/output or output/input ports like Active transformations. Router has input, output, and input/output ports for routing data. Lookup has input/output and output ports for returning lookup results. Aggregator has input/output and output ports for group calculations.

Joiner transformation is specifically used to join data from heterogeneous sources like a table and a flat file, or two different database systems. If both tables are in the same database, it's more efficient to use a SQL Join with Source Qualifier rather than Joiner transformation. Joiner adds overhead and should be avoided when database-level joins are possible.

Joiner transformation can join exactly two sources - designated as master and detail. It has two input groups and cannot join more than two sources. For joining multiple sources, you need to use multiple Joiner transformations in sequence or use other strategies like SQL overrides. This is a fundamental limitation of the Joiner transformation.

Lookup transformation supports three cache types: Persistent cache (saved to disk and reused across sessions), Dynamic cache (refreshed during session execution), and Static cache (loaded once and remains unchanged). The default is static cache. 'All of the above' is correct because all three types are valid lookup cache options in Informatica.

Normalizer transformation in Informatica is specifically designed to read and normalize data from COBOL files, which often contain OCCURS clauses and complex hierarchical structures. Source Qualifier is for relational sources, and Source Definition is just metadata. Normalizer can parse the complex COBOL copybook structures and denormalize them into relational format.

Lookups in Informatica are classified into two types: Connected lookup (part of the data flow pipeline, receives input rows directly) and Unconnected lookup (called from within another transformation using :LKP reference, not directly in data flow). Active and passive refer to transformation types, not lookup categories. Connected vs unconnected determines how the lookup is invoked and whether it's part of the main flow.

Workflow Monitor primarily provides two views: Task View (shows task execution details, status, and timing) and Gantt Chart View (graphical timeline representation of workflow execution). While other options mention additional views, the core Workflow Monitor interface centers on these two views for monitoring workflow execution. 'Gnatt' is a typo for 'Gantt' but doesn't change the answer.

In older versions of Informatica PowerCenter, both the Informatica Server (which executes sessions) and the Repository Server (which manages metadata) are core server-side components.

RAW datatype in Informatica represents binary data and cannot be implicitly or explicitly converted to other datatypes like string, number, or date. RAW data must be handled as binary - attempting conversion will cause errors. Character, Date, and Integer can all be converted to each other using appropriate conversion functions like TO_CHAR, TO_DATE, or TO_INTEGER.

Expression transformation performs row-level calculations and transformations using input values to create output values, but does not require any caching. Aggregator uses index and data cache for grouping and aggregation. Lookup uses index and data cache to store lookup data. Joiner uses index and data cache for the join operation. Expression is the only one that processes each row independently without needing to cache data for comparisons or lookups.

Repository Manager is the administrative tool in Informatica that manages users, creates and organizes folders, and assigns security privileges. All these functions are performed through Repository Manager - user creation and management, folder structure management, and access control through privilege assignment. The Designer and Workflow Manager tools focus on different aspects (mapping design and workflow execution) and don't handle these administrative tasks.

The error occurs because the code attempts to use $fsex. as an informat in the input statement, but it was defined as a format using proc format. SAS expects informats for reading data, causing the compilation to fail.

Pointer p is assigned address of i. Then p++ increments p by one integer (4 bytes on most systems). The expression (p - &i) calculates the offset between the new pointer address and original address, which is 1 integer - not 1 byte. The difference is measured in the pointer's data type units, so it equals 1.

In the IDEAL language, ADD and SUBTRACT are valid statements while ADDITION and SUB are not. ADD is used for addition operations, and SUBTRACT is used for subtraction operations. The language requires these specific keywords rather than variants like ADDITION or SUB.

A long pointer on most systems is 8 bytes (or 4, depending on architecture), while int is 4 bytes. When you assign &i (int pointer) to long* pointer p, there's a type mismatch. After p++, the difference p - &i is calculated as pointer arithmetic: p advances by sizeof(long) bytes, &i is the original address. The difference is the number of long-sized steps between them, which is 1.

The code attempts to assign the address of an integer variable to a long pointer without an explicit cast, and furthermore tries to subtract pointers of different sizes. This causes a compile-time error in standard C.