Siebel and Lotus Notes Database Technologies

Report generation tools typically allow users to define input data sources and select desired output formats, such as PDF, Excel, or HTML.

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.

CTRL+O is the universal keyboard shortcut for 'Open' across Windows applications, including database systems. CTRL+V is for paste, and CTRL+N creates new files/databases. This shortcut works consistently in Microsoft Access, FileMaker Pro, and most database management tools.

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.

Design Synopsis outputs comprehensive metadata and structural information about every application component, making it highly useful for documentation and archival tasks.

The Design Synopsis feature provides a dedicated dialog box specifically designed to generate detailed structural reports on a selected database.

Shared fields in FileMaker Pro act as reusable field definitions: they behave like regular fields (A), changes propagate to all occurrences (B), and deletion removes them from all forms (C). Since all three statements are true, 'All of these' is the correct answer.

Actions in FileMaker Pro are indeed shortcuts for tasks (A), specifically one-click shortcuts for routine operations (B), work on views/subforms/forms (C), and can use @commands/LotusScript/JavaScript (D). All four statements are correct.

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.

EIM tables require ROW_ID (unique identifier), IF_ROW_BATCH_NUM (batch tracking), and IF_ROW_STAT (status tracking like 0=success). These are mandatory columns for EIM processing. CONFLICT_ID is optional.

EIM (Enterprise Integration Manager) performs four core operations: Insert new records, Delete existing records, Merge records, and Update records. 'Upsert' is not a standard EIM operation term; the combination of Update and Insert is covered by the individual operations.

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).

A single EIM interface table is configured to populate a specific base table or a set of related base tables in a controlled manner. EIM doesn't simultaneously populate arbitrary multiple base tables from one interface table; the mapping is specific and controlled. The statement is false.

EIM (Enterprise Integration Manager) is Siebel's native tool for populating interface tables, not a third-party tool. The statement incorrectly suggests that external tools are required for this standard Siebel integration process.

Siebel installation populates seed data (reference data like picklists, LOVs) and repository data (metadata, schema definitions, object definitions). User data is created post-installation through application use, not during the installation process.