Database Management Systems

A logical configuration defines how system components are architecturally structured and connected, regardless of their hardware deployment. When the application and database servers are installed on the same physical machine, they are logically separated but physically shared, representing a logical configuration rather than a physical one.

The Usage property determines how a query item can be used in reports - as a fact, attribute, or identifier. This is the most critical setting to verify immediately after import because it affects how data can be aggregated and displayed. Format, Data Type, and Semi-Aggregate are important but secondary to Usage.

When importing metadata, Framework Manager can automatically generate relationships between query subjects based on existing primary key and foreign key relationships in the database. This saves significant modeling time and ensures referential integrity. Multiple connections must be defined separately, usage is set manually, and join types are not automatically converted.

In DataStage, when you configure a join stage without specifying the join type, it defaults to a Left Outer Join. This means all records from the left input link are included, and matching records from the right link are included where available. Equi-join requires exact matches on both sides, Full Outer includes all records from both sides, and Right Outer prioritizes the right input.

The DataStage Administrator role focuses on system-level management tasks including creating and deleting projects, managing users, and configuring system settings. Job design is done by developers, monitoring by operators, and import/export functions are available in Designer. The Administrator tool is specifically for project and user management.

Negative testing validates how the system handles error conditions, such as missing files, format errors, or oversized inputs. Ensuring the database table is accessible to the user is a baseline requirement for normal operations, making it a positive test scenario rather than a negative one.

An Oracle Database can have up to 8 control files. These are multiplexed copies for redundancy. The question asks for the maximum number, and 8 is the correct answer.

AWR (Automatic Workload Repository) data is stored in the SYSAUX tablespace in Oracle 10g and later. SYSAUX was introduced specifically to relieve the SYSTEM tablespace of auxiliary data like AWR statistics, making option C correct. SYSTEM is for core dictionary data, USERS for user objects.

Transparent tables in ABAP Dictionary have a 1:1 relationship with database tables - same name, same fields, same structure. Pooled and Cluster tables store multiple logical tables in fewer database tables. Views are virtual tables based on queries, not physical 1:1 mappings.

In ABAP Dictionary, standard data classes are Master Data (master records), Transaction Data (transactional documents), Organization Data (customizing/organizational units), and System Data (system configuration). 'Project Data' is not a standard data class, making option C the correct answer to the negative question.

In SAP ABAP, transparent tables are physically created in the underlying database when you activate them in the ABAP Dictionary. The activation process generates and executes the DDL statements that create the actual database table structure. Simply creating the table definition without activation does not create the physical table.