Database Management Systems

SessionFactory is a thread-safe, immutable object that is created once during application initialization and shared across all threads. It is heavyweight and maintains the configuration, mappings, and connection pool. Session objects are not thread-safe and should be created per thread/request.

Automatic dirty checking is a Hibernate feature that automatically detects changes made to persistent objects within a transaction and synchronizes them with the database during flush/commit. You do not need to call update() or save() explicitly; Hibernate tracks object state automatically.

Hibernate initializes when the SessionFactory is created, typically via Configuration.buildSessionFactory(). This is when Hibernate reads configuration files, builds mappings, and creates the connection pool. Creating individual Sessions happens after initialization, not during it.

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.

The statement is incorrect because it says 'Files are the central place' rather than 'The Files resource is the central place.' Files themselves are not the central place - the shared resource container called 'Files' is where you import and store files like HTML documents for use throughout your applications. The distinction is between the storage mechanism (the resource) and the stored items.

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.

Creating a new database via File, Database, New opens a dialog box that presents a list of available templates to base the new database on.

The .NSF extension stands for 'Notes Storage Facility' and is used for standard database files in Lotus Notes/Domino. These files store both the application design elements and user data. Option B is incorrect because .NTF is the extension for template files, not regular databases. NSF files are the runtime databases that users interact with.

The .NTF extension specifically stands for 'Notes Template Facility' and is used for template database files in Lotus Notes/Domino. Templates serve as blueprints for creating new databases - they contain design elements but no user data. Option A is incorrect because NSF refers to regular storage facility databases, not templates. NTF files are the master templates from which NSF databases are created.

Design Synopsis in Domino Designer aggregates database component details into a single location, allowing developers to search and review code logic and design elements easily.

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.