Database Management Systems

The NBT Application uses three databases. This multi-database architecture likely separates concerns such as user authentication, business data, and reporting/analytics. Using multiple databases improves performance, security, and maintainability by isolating different data domains.

ADO.NET DataSets and classic ADO RecordSets are fundamentally different technologies that cannot be directly synchronized. DataSets are XML-based, disconnected data containers from .NET, while RecordSets are COM-based objects from classic ADO. You can sync DataSets with databases, convert them to XML, and infer schemas, but there's no direct DataSet-to-RecordSet synchronization mechanism.

The Data Access Object (DAO) pattern encapsulates all data access logic, providing a clean separation between business logic and data persistence. It enables loose coupling by abstracting the underlying data source and providing CRUD operations. Service Activator enables async processing, Domain Store handles transparent persistence, and Business Object represents business entities.

When you create an object without specifying a TABLESPACE clause, Oracle automatically stores it in that user's default tablespace. This default tablespace is assigned when the user account is created. The system tablespace is reserved for data dictionary objects, not user data.

FS-LDM (Financial Services Logical Data Model) is Teradata's industry data model for financial services. While it serves as a reference framework, organizations typically customize and adapt it rather than using it as a strict guideline. The statement's absolute wording 'would be used' makes False the correct answer - EDW architecture requires customization.

BusinessObjects (BO) is the reporting tool integrated into the FASTTRACK system for generating user-facing reports. Cognos BI and MicroStrategy are distractors, while SQL Assistant is a query tool, not a reporting platform.

Internal LOBs (Large Objects like CLOB, BLOB) are stored directly inside the database files, whereas external LOBs (BFILEs) reside in external operating system files pointed to by a database column.

When JDBC connection creation fails during WebLogic server startup, WebLogic logs this as an ERROR level message because it represents a critical failure that prevents the server from functioning properly. ERROR level indicates a serious problem that requires immediate attention. WARNING is for potential issues that don't stop operation. INFO is for informational messages. CRITICAL is not a standard WebLogic logging level (the levels are ERROR, WARNING, INFO, DEBUG, TRACE).

Garbage collection monitoring is done at the JVM level by starting with the -verbose:gc flag (or -XX:+PrintGCDetails in newer JVMs). This prints GC activity to stdout. The weblogic.Admin utility doesn't have a GC parameter, and examining logs shows results but doesn't actively monitor.

In production mode, WebLogic's default connection pool size is 25 connections. In development mode, the default is lower at 15 connections. Option A (15) is the development mode default, and -1 would mean unlimited which is not the default.

A report purge removes all the data rows that were fetched by running the query, while keeping the report structure intact. This allows you to clear the data without deleting the report definition, essentially resetting it to an empty state ready for refresh.

Query synchronization is a WebIntelligence feature available in XIR2 and XI 3.x, allowing data from multiple queries to be combined in a single report. Crystal Reports does not have this specific query sync capability.

An instance in Business Objects terminology refers to a specific scheduled run of a report, stored as a static snapshot at the scheduled time. The report definition itself is not an instance - instances are the results of scheduled executions.

Averages should be calculated at the report level where they can be dynamically computed based on current data filters and query context. Universe-level aggregation is less flexible and database-level aggregation doesn't adapt to report-level conditions.

SQL Server 2005 had multiple editions to serve different use cases. Developer Edition is for development/testing, Express is a free lightweight version, Enterprise is for large-scale mission-critical workloads, and Standard is for moderate-scale departmental applications. Integration Edition was not a SQL Server 2005 edition.