Database Management Systems

Enabling sessions in WCF requires both: (1) marking the service contract with SessionMode.Required, and (2) setting InstanceContextMode to PerSession in the ServiceBehavior. Option A shows the contract requirement, Option B shows the service behavior - both are necessary.

WCF REST services are created by adding WebGet (for HTTP GET) or WebInvoke (for other HTTP methods) attributes to operation contracts. Both approaches are valid for creating RESTful services.

WSFederationHttpBinding with Message security is the correct choice for STS-based token authentication when SSL/TLS is not available. This binding is specifically designed for federated security scenarios where a Security Token Service issues tokens. TransportWithMessageCredential requires SSL transport security, which the scenario explicitly states clients cannot use.

Delegation is required when the WCF service needs to access remote resources on behalf of the client (multi-hop scenario). Impersonation only allows accessing local resources on the service machine. Identification allows the service to identify the client but cannot impersonate at all.

In Windows Communication Foundation (WCF), the wsDualHttpBinding is designed specifically to support dual-way communication, which inherently requires and supports reliable sessions by default. BasicHttpBinding does not support reliable messaging by default, and netTcpBinding supports reliable sessions but requires explicit configuration or different defaults depending on context.

wsDualHttpBinding does not support streaming because it uses HTTP for both request and response channels, and HTTP is inherently message-based (no streaming). TCP and named pipe protocols (netTcpBinding, netNamedPipeBinding) support streaming. basicHttpBinding can support streaming with appropriate transferMode settings.

The System.ServiceModel namespace contains the core classes, interfaces, and structures required to build and consume WCF service clients and hosts. Namespaces like System.Web, System.Data, and System.Service do not contain these WCF-specific constructs.

IDispatchMessageInspector is the service-side interface for message inspection and logging. It provides AfterReceiveRequest (inspect incoming messages) and BeforeSendReply (inspect outgoing responses) methods. IClientMessageInspector is the client-side equivalent.

Complex server topology in TFS uses multiple servers configured in clusters or failover arrangements to host both the data tier (databases) and application tier (TFS application servers). This provides high availability and redundancy - if one server fails, another takes over. Simple topology uses a single server, while moderate separates data and application tiers without clustering.

In a Teradata database system, parsing SQL, verifying validity, and optimization are done by the Parsing Engine (PE), not the Access Module Processor (AMP). The AMP is responsible for database operations like storing, retrieving, sorting, and formatting data on its own disk.

Perm space in database systems has four key characteristics: (1) it can be dynamically modified to accommodate growing data needs, (2) specifications are subtracted from the immediate parent/owner in the space hierarchy, (3) unused perm space is available for spool or temp operations, and (4) it's used for permanent objects like tables and stored procedures. Volatile tables use temp space, not perm space.

DB2 is IBM's proprietary relational database management system, designed specifically to exploit IBM hardware and system architectures. While Oracle can run on IBM systems, DB2 is optimized for and integrated with IBM's hardware platforms like mainframes (z/OS), Power Systems, and AIX. The other options are variants of DB2 on IBM systems, but the general answer is DB2 itself.

A mapping in Informatica PowerCenter must include transformations to process and route data from sources to targets. Transformations define the data manipulation logic (filtering, joining, aggregating, etc.). Mapplets are optional reusable components, while Sessions and Workflows are execution components that manage runtime - they are not part of the mapping structure itself.

WSS 3.0 hierarchy is: Farms (top-level server grouping) → Web Applications (IIS websites) → Site Collections (logical grouping) → Sites (actual team sites). 'Web parts' are components placed on pages, not a hierarchy level. 'Web sites' (option E) is ambiguous - the correct term in the hierarchy is 'sites' (option F), and web applications already represent the IIS web site level.

MOSS 2007 (Microsoft Office SharePoint Server) provides Document Libraries, Webparts, Lists, Workflows, and Business Data Applications as core application services. These are all valid components of SharePoint's service architecture. Farms (option C) refer to the deployment topology, not an application service - it's the infrastructure level, not a user-facing service.