Database Fundamentals: Oracle, PL/SQL, and SQL

Option A is incorrect: stored procedures are written in PL/SQL (not SQL). Option B is correct: stored procedures are named PL/SQL blocks that accept parameters. Option C is correct: stored procedures are PL/SQL subprograms that perform actions. Option D is incorrect: procedures have specification and body, not three parts. Option E is incorrect: the executable section does not return values to the calling environment.

Without seeing the scenario, this appears to be about choosing between database structures for a reporting/analysis need. A View is the best choice when you need to query data from multiple tables without duplicating data. Views provide a logical abstraction layer. Table filter and dynamic procedure are not standard SQL structures, while a cursor table would be inefficient.

Without the scenario context, this asks about ongoing operational processes in a database system. Performance monitoring is the only continuous operational activity listed - it runs regularly to check system health, query performance, and resource usage. OS requirements, user analysis, data dictionary specification, and system requirements are one-time or design-phase activities, not ongoing operations.

Without the full context, in data modeling, security review typically occurs during the design issue phase where access controls, privacy requirements, and security constraints are evaluated. Structure phase defines the model, data source phase identifies data origins, storage issue phase deals with physical storage, and operational process phase covers maintenance. Security considerations must be addressed during design.

Metadata is 'data about data' - it describes structure, format, relationships, and other characteristics of data. It supports its own structure, is self-describing, and describes what's in a data dictionary. What metadata does NOT include is the actual user data or business data itself - that's the content, not the description. Option D correctly identifies that user data is not metadata.

A column alias is specified by placing it immediately after the column name in the SELECT list, separated by white space (optionally using the AS keyword). Placing it at the beginning or end of the statement or using a comma separator is syntactically invalid for column aliasing.

RDBMS stands for Relational Database Management System. It organizes data into tables with relationships between them, based on the relational model proposed by E.F. Codd.

The domain of a column defines its set of all permissible values. A column for birth month allows integers from 1 to 12, whereas a column for birth day allows integers from 1 to 31. Because these sets and their semantic rules differ, their domains are distinct.

To solve this question, the user needs to know what a check constraint is and the concept of restricting the domain of a numeric column.

A check constraint is a rule that limits the values that can be inserted into a column. It ensures that the data is valid and meets certain criteria. Restricting the domain of a numeric column to non-negative values means that only values greater than or equal to zero can be inserted into the column.

Now, let's go through each option:

A. True: This option is correct. A check constraint can be used to restrict the domain of a numeric column to non-negative values. For example, the following SQL code creates a check constraint that restricts the values in the "age" column to be greater than or equal to zero:

ALTER TABLE students
ADD CONSTRAINT non_negative_age CHECK (age >= 0);

B. False: This option is incorrect. As explained above, a check constraint can be used to restrict the domain of a numeric column to non-negative values. Therefore, option A is the correct answer.

The Answer is: A

By definition, a primary key constraint uniquely identifies each record in a database table. Therefore, the column or set of columns designated as the primary key must contain unique values and cannot contain null values.

A view in a database is a virtual table based on the result-set of an SQL statement. It does not actually store data physically by itself in most standard configurations, but rather computes it dynamically on demand.

Stored procedures are indeed only executed when explicitly called by a user, application, or another procedure. They are not automatically triggered by data operations. Unlike triggers, which fire automatically on events, stored procedures must be invoked by name using EXECUTE or CALL statements.

Triggers can enforce referential integrity by executing custom logic before or after INSERT/UPDATE/DELETE operations. They can validate data, prevent invalid operations, or cascade changes similar to foreign key constraints. While foreign keys are declarative and preferred, triggers offer programmatic control for complex scenarios.

Chain is a physical storage structure used in older file systems and some database implementations, not a logical database model. The logical database models are Network (many-to-many relationships), Tree/Hierarchical (parent-child relationships), and Relational (tables with keys). Chain describes how data blocks are linked on disk.

Public synonyms are database objects that provide alternative names for tables/views, but they are NOT schema objects themselves. Schema objects are entities contained within a schema like indexes, triggers, packages, tables, and views. Synonyms are pointers/reference objects that exist outside the schema namespace.

RAISE_APPLICATION_ERROR in Oracle allows user-defined error numbers from -20000 to -20999, giving developers 1000 error codes for custom exceptions. This range is reserved specifically for application-defined errors. Error numbers outside this range are reserved for Oracle system errors.