Database Management Systems

In a CICS BMS symbolic map, multiple variable levels are generated for each field: suffix L for length, A for attribute, F for flag/modified data, and I/O for input/output data. Since all these components are generated, 'All of the above' is the correct answer.

The Data Access Object (DAO) layer is specifically responsible for managing CRUD operations (Create, Read, Update, Delete) on stored data. It provides an abstraction interface between the application and persistent storage. Value Objects carry data, Presentation Layer handles display, and Deployment Layer manages infrastructure - only DAO handles data persistence operations.

Shared resources in Domino Designer contain various design elements that can be shared across databases, including images, files, applets, and style sheets. This allows for consistency and reusability across multiple applications within an organization. Option D correctly encompasses all the individual types of shared resources listed in options A, B, and C.

The statement as written is grammatically incorrect because it states 'Images are the central place' rather than identifying the shared resource container called 'Images' as the central place. While the Images shared resource is indeed where images are imported and stored for database-wide use, the phrasing makes the statement technically false as written.

All three methods are valid ways to create a database in Domino: using an existing template as a starting point, copying from an existing database, or creating a completely new blank database from scratch. Each approach serves different needs - templates provide pre-built structure, existing databases preserve design and data, and blank databases offer complete flexibility.

Siebel supports two primary types of data model extensions: 1) Extension tables that add columns to existing base tables, and 2) Custom extension tables (1:1 or 1:M) for new data. This is a fundamental Siebel architecture concept.

User data is stored in base tables. While complex entities may span multiple base tables joined by relationships, and extension tables store additional attributes, the fundamental storage unit is the base table. 'More than one base table' correctly reflects that user data can span multiple base tables for complex entities.

Interface tables (EIM tables) are designed to temporarily hold external data being imported into Siebel. They act as a staging area where external data is loaded before EIM processes and moves it into base tables. They don't store seed data (built-in reference data) or repository data (metadata).

In Siebel applications (or similar database systems), user data is stored across multiple base tables rather than a single table. This normalized database design allows efficient data management and relationships. Option D 'More than one base table' correctly represents this multi-table architecture.

A view in database systems (like Lotus Notes) displays a list of documents/records from the database. It serves as a placeholder/interface for viewing data. Option D combines both the definition (list of documents) and function (viewing data), making it the most complete answer.

A form serves as both the interface placeholder for entering information AND the structural framework for storing that information in a database. Option C correctly combines both aspects - it's where you enter data (placeholder) and the system that stores it (framework).