Mixed Technology Quiz (Informatica, .NET, Unix)

DataReader is designed for fast, forward-only, read-only data retrieval - ideal for populating read-only UI controls like dropdowns. It streams data efficiently without caching. DataAdapter fills DataSets, Command executes queries, Connection manages the connection, and Recordset is from classic ADO.

Delegates in .NET are type-safe and can only reference methods that match their signature exactly (same return type and parameters). Option A is false because events are decoupled from handlers - they publish notifications without knowing subscribers. Option B is false because an event can have multiple subscribers through multicast delegates. Option C is false - delegates ARE type-safe by design. Option D is false because a class can define and raise multiple events.

Declarative security uses attributes to declare security requirements directly in code metadata, without writing imperative security checks. Options B through C are actual .NET security mechanisms but require imperative code logic - they don't rely solely on attributes. Declarative security is the ONLY approach where adding attributes alone provides security functionality.

PermView.exe is a .NET SDK utility that displays the permission requests (minimal, optional, refused) declared in an assembly's metadata. Options B through E describe unrelated functionality - PermView has nothing to do with Dataset views, heap management, or dynamic assemblies. It's specifically a security diagnostic tool for examining CAS (Code Access Security) permission requests.

The CLR enables language interoperability in .NET by allowing code compiled in one .NET language (like C#) to interact with code compiled in another .NET language (like VB.NET). This is possible because all .NET compilers compile to MSIL (Microsoft Intermediate Language), which the CLR executes, and the CLR implements a Common Type System (CTS) ensuring type compatibility across languages.

Web Services are designed to support interoperable machine-to-machine interaction over a network using standard protocols like HTTP and exchanging payloads in XML formats (such as SOAP). Windows GUI apps, Windows Services, and DCOM do not inherently fit this design pattern.

For an attribute class to be CLS-compliant, it must have the System.AttributeUsageAttribute applied to define its usage constraints. While inheriting from System.Attribute is required to define any custom attribute in .NET, applying AttributeUsageAttribute is the specific rule for CLS compliance.

This question refers to Informatica PowerCenter's environment architecture. The standard environment structure includes Development, Testing, User Acceptance Testing (UAT), and Production - totaling 4 environments. This is a common enterprise ETL/ data integration setup.

In Informatica PowerCenter, the Sorter transformation can be configured as either Active or Passive. By default, it's Active (changes row count), but setting properties like 'distinct' can make it Passive. Router, Filter, and Aggregator are always Active transformations.

In Informatica PowerCenter, the CUME() function calculates cumulative/running totals within a group. Unlike simple aggregation functions like SUM(), CUME maintains a running accumulation across rows, making it the correct choice for running total calculations.

Mapping parameters in Informatica PowerCenter are designed to hold values that change between sessions (like dates, file paths, or external values). They're set before session execution. Session variables are runtime-modifiable, while UDFs are for custom logic, making mapping parameters the best choice for frequently changing external values.

In Informatica Lookup transformations, the columns used in the lookup condition are cached in the index cache for fast searching. Other columns go to the data cache. This optimization improves lookup performance by indexing on the join/condition columns.

The 'LR' data is generated by executing SQL queries directly on the Data Warehouse (DWH) data, not through intermediate tools like Hyperion, Informatica, or Datastage. This direct SQL approach on consolidated warehouse data is the standard method for generating such reports.

Development is the environment where code/config changes are initially implemented and tested. Staging is for pre-production validation, and Production is the live environment. Making changes directly in Production is against standard practices, making Development the correct answer.

Informatica's built-in scheduler has limitations for very frequent intervals. A 5-second interval is too granular for standard scheduler configurations. Using an external batch script invoked from Informatica provides the needed flexibility for sub-minute scheduling.

The question refers to vi editor modes. In vi, you enter Insert mode (press 'i' or 'a') to make changes to text. Command mode is for navigation and commands, while Insert mode is specifically for editing/inserting content.

Email tasks in Informatica can be implemented either through the built-in Email task/command or by writing a batch script that sends emails and invoking that script from Informatica workflows. Both approaches are valid and commonly used depending on requirements.

ABE loads typically process data from the previous business day, not the current calendar date. The Run ID format must include yesterday's business date (which may differ from calendar date) to ensure correct data lineage and auditability.

In Unix/Linux and programming conventions, exit code 0 universally indicates successful execution. Any non-zero exit code (1-255) indicates various types of failures or errors. This is a standard across operating systems and programming languages.