Database Management Systems

DBA stands for Database Administrator, the person responsible for managing database systems. Option A correctly uses 'Database' and 'Administrator'. Option B incorrectly uses 'Device' and 'Base'. Option C is nonsensical. Option D has a typo 'Datebase' instead of 'Database'.

DFD stands for Data Flow Diagram, used to visualize the flow of data through a system. Option D correctly uses 'Data Flow' twice - data flowing through processes. Options A, B, and C incorrectly use variations like 'Fnd' (typo) and 'Fast' which are not part of the term.

Teradata provides multiple mechanisms to enable joins to occur on the same AMP: identical primary indexes naturally distribute matching rows to the same AMP; dynamic redistribution can rehash tables during query processing; and duplicating small tables across all AMPs eliminates data movement. All three are valid join optimization strategies.

Date and Datetime types in Ab Initio are stored in binary form for efficiency in calculations and comparisons. While integers are also stored in binary, the question specifically asks about types known for binary storage of temporal data. Decimal stores as packed decimal, and string stores as character data. Date/Datetime is the best answer for binary-encoded temporal data.

Data skew is an uneven distribution of data across processing units (SPUs). When some SPUs receive significantly more data than others, they become bottlenecks while other SPUs sit idle. This defeats the purpose of parallel processing and severely degrades query performance. It's typically caused by poor distribution key choice in MPP databases.

nzload is transactional - if it fails mid-operation, all partially loaded records are rolled back to maintain data integrity. This rollback is typically implemented by logically deleting the records (marking them as deleted). They remain on disk temporarily but are invisible to users and will be cleaned up by maintenance processes.

Zonemaps in Netezza are automatically created and maintained by the system as metadata structures that track min/max values per data slice. Unlike indexes, users do not need to manually create or maintain zonemaps - they are built automatically during data loads.

JDBC classes are distributed across java.sql (core JDBC API including Connection, Statement, ResultSet) and javax.sql (optional package including DataSource, ConnectionPool, RowSet). Options A and B incorrectly use 'jdbc' instead of 'sql', and option D invents non-existent 'rdb' packages.

Transactions require auto-commit to be disabled BEFORE starting transactional operations. This allows multiple statements to be grouped together and either committed (all succeed) or rolled back (all fail) as a unit. Option C is false because auto-commit must be turned off before, not after, the transaction begins.

ServerName is the correct parameter in tm1s.cfg that uniquely identifies the TM1 application server. DataBaseDirectory specifies where data is stored, AdminHost is for administration, and PortNumber defines the communication port.

Creating multiple hierarchies within a single dimension reduces the total number of dimensions needed in a cube, which consequently reduces the number of empty cells. Using separate dimensions for each hierarchy would dramatically increase sparsity.

When loading data into a cube, each dimension must be mapped to a simple (leaf-level) element to identify the specific cell where data should be written. Consolidations and attributes are not used for data loading.

A reporting cube and lookup cube can share data even with zero common dimensions. TM1's ability to reference cells across cubes doesn't require dimensional overlap - it uses cube-level references and dimension mappings.

MigrateFileStorage Utility is the specific tool for migrating from file-based to database-based domain data repository storage. The domain utility is general-purpose, TIBCO Administrator doesn't perform migrations, and MigrateDomainStorage is not the correct utility name.

JDBC core classes are in java.sql package. Extended JDBC API (for connection pooling, distributed transactions) is in javax.sql. There are no java.jdbc or java.rdb packages.