Informatica PowerCenter Data Integration

Workflows and tasks in Informatica have specific status states during their lifecycle. 'Succeeded' indicates completion, 'Scheduled' means waiting for execution time, and 'Suspending' is a valid transitional state when a workflow is being paused. 'Unknown status' is also a documented state when the Workflow Manager cannot determine the current status. Option C incorrectly uses 'unscheduled', 'Scheduling', and 'stopping' which are not standard status display values.

The 'Maximum automatic recovery attempts' workflow property controls how many times the Integration Service will automatically try to recover a failed task before giving up. The default setting is 5 attempts. This is different from the retry-on-failure setting for individual tasks. The automatic recovery feature helps handle transient failures without manual intervention.

The infacmd ping command is used to verify connectivity and availability of Informatica domain components. It checks the Domain gateway (which handles client connections), the Domain host (primary server), and the node (where services run). It does not ping individual sessions or workflows directly - those are managed by the Integration Service, not checked via ping command.

The infacmd command-line tool uses specific return codes to indicate execution results. A return code of 0 indicates successful completion. A return code of -1 indicates failure or error. This convention follows Unix-style exit codes where 0 means success and non-zero means error. Understanding these codes is essential for scripting and automation with infacmd.

When session tracing level is set, it takes precedence over any tracing levels configured at the individual transformation level within the mapping. This hierarchy means the session-level setting is the controlling parameter for logging verbosity. For example, if session is set to Normal but a transformation has Verbose Data, only Normal logging will occur.

In high-availability configurations, when a node running a service process becomes unavailable, the service automatically migrates to another available node. This process is called failover - it's distinct from recovery (retrying on same node) and resilience (general ability to withstand failures). Failover ensures continuous service availability despite node failures.

In Informatica PowerCenter domain architecture, a node represents the logical representation of a machine. A grid consists of multiple nodes, Service Manager manages domain services, and Administration Console is the web interface - none of these represent the machine itself.

SQL transformation in Informatica can operate in Script mode (executes SQL scripts) or Query mode (executes single queries). Bulk mode and Normal mode are not valid execution modes for SQL transformation.

XML Generator and XML Parser are both active connected transformations. Parser reads XML from one input port and writes to multiple output ports (passive parsing behavior). Generator accepts data from multiple ports and writes XML through a single output port. Both being active transformations contradicts option D.

Repository service manages metadata storage and retrieval. Integration service handles job execution and scheduling. Mappings cannot be created without repository service because metadata access is required. Option D contradicts this fundamental dependency.

In Normalizer transformation for COBOL files, a Generated Key port is created for each REDEFINES clause (identifies which redefinition is active). A Generated Column ID is created for each OCCURS clause (identifies the occurrence position). The reverse mappings in options B and D are incorrect.

Unconnected stored procedures require: input/output parameters in expressions to match the transformation ports exactly (A), use PROC_RESULT variable to return a single output parameter (B), and cannot mix connected/unconnected modes for the same transformation instance in a mapping (C). Nested stored procedures are allowed at multiple levels.

Source Analyzer can import: relational objects (tables, views, synonyms), COBOL files, XML files, and data models. It cannot import flat files containing binary data - only text-based delimited or fixed-width files are supported for flat file sources.

Transaction Control Transformation in Informatica PowerCenter is specifically designed to manage commit and rollback operations for various target types including relational databases, XML sources, and IBM MQSeries targets. It allows you to define conditions that determine when to commit or rollback transactions based on business logic or data conditions. The other transformations listed serve different purposes - Stored Procedures execute database procedures, XML handles XML data, and HTTP makes web service calls.

When using an unconnected transformation in Informatica (such as an unconnected Lookup transformation marked as :LKP), you must use a reference qualifier in the expression to call it. The reference qualifier provides the necessary context and input values to the unconnected transformation. This is different from connected transformations, which are part of the data flow and don't require explicit calling syntax.

Private IP ranges are 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. The address 169.254.0.200 falls in the APIPA (169.254.0.0/16) range, which is link-local and not considered a private IP address for internal network use.

The Network layer (Layer 3) uses packets as its data unit. Frames are Layer 2 (Data Link), segments are Layer 4 (Transport), and bits are Layer 1 (Physical).

DNS (Domain Name System) uses port 53 for both UDP and TCP communication. Port 23 is used by Telnet, port 80 by HTTP, and port 110 by POP3 email protocol.

Lotus Notes (IBM Notes) uses port 1352 for client-server communication. Port 1433 is for SQL Server, 443 is for HTTPS, and 1533 is not a standard well-known port.