Web Technologies: Backend & CSS

The CSS property 'text-transform: capitalize' capitalizes the first letter of each word. 'text-transform: capital' is invalid - no such value exists. 'uppercase' would make ALL letters uppercase, not just the first. CSS can definitely do this.

In CSS, multiple element type selectors can be grouped together by separating them with commas to apply the same style rules to all of them.

An ID selector in CSS targets a single, unique element on a page based on its id attribute, as IDs must be unique within a document.

CSS rules follow the syntax 'selector { property: value }' where the selector is followed by curly braces containing the property and value separated by a colon. The property: value pair uses a colon, not an equals sign. Options B and D incorrectly use '=' and parentheses instead of braces.

Valid CSS syntax uses the selector followed by curly braces: selector { property: value }. Option A correctly shows 'body {color: black}' with proper syntax. Options B and D use incorrect brace placement, option C uses colon incorrectly and equals sign instead of braces.

CSS supports three color specification methods: common names (red, blue), RGB values (rgb(255, 0, 0)), and hexadecimal notation (#FF0000). Option B is correct, though it says 'RBG' instead of 'RGB' - a typo but the intended meaning is clear. Hex-only or name-only are incomplete options.

In CSS, the text-decoration property controls underlines. To remove underlines from hyperlinks, use text-decoration: none. Option A uses the wrong property name, B uses underline which isn't a valid property, and D uses no underline instead of the keyword none.

The correct CSS property to change text weight and make it bold is font-weight set to bold.

Hibernate ORM (Object-Relational Mapping) maps Java classes to database tables, and Java data types to SQL data types. The mapping allows developers to work with objects in Java while Hibernate handles the underlying database operations.

Hibernate is indeed an Object-Relational Mapping (ORM) framework for Java that provides a bridge between object-oriented domain models and relational databases. It allows developers to work with Java objects instead of writing raw SQL queries, automatically handling the translation between objects and database records.

Hibernate uses POJO (Plain Old Java Objects) classes for mapping Java objects to database tables. The mapping is typically done through XML mapping files or Java annotations on POJO classes. Utility classes are not the primary mapping mechanism in Hibernate.

'Pure relational' is the odd one out because it refers to a pure database approach without ORM, while the other options (caching, outer join fetching, lazy collection initialization) are all Hibernate ORM performance optimization techniques. Hibernate is specifically about bridging the gap between objects and relational databases, not staying purely relational.

Hibernate automatically generates unique identifiers for entities based on the configured generator strategy (like 'increment', 'native', 'uuid', etc.). This is a core feature of Hibernate - you don't need to manually generate or manage primary keys. The framework handles this through the element in mapping files or annotations.

Hibernate Types are indeed used to map Java property types to JDBC types, enabling the translation between Java objects and database columns. Each Java type (String, Integer, Date, etc.) has a corresponding Hibernate Type that knows how to convert to and from appropriate JDBC types for database operations.

The Hibernate mapping configuration with automatically generates incrementing numeric IDs for new entities. When you save a new object, Hibernate reads the next ID value from the database and assigns it. This is a built-in ID generation strategy that requires no manual intervention.

QUIESCE is a DB2 utility that forces all pending changes from the buffer pool to be written to disk, ensuring data consistency. It's particularly important before operations like backups, COPY, or LOAD to guarantee that all data is safely stored on disk. QUIESCE essentially does a checkpoint - it flushes all modified pages from memory to disk and records a point of consistency. FREEPAGE and PCTFREE are storage parameters controlling how much free space is reserved in table spaces for future inserts/updates. TABLESPACE is a container for tables, not a command or utility.

Index cardinality refers to the number of distinct (unique) values in an indexed column. A high cardinality index has many unique values (like a primary key), making it very selective and efficient for queries. A low cardinality index has many duplicate values (like a gender column with only 'M' and 'F'), making it less selective. Cardinality helps the query optimizer choose the best execution plan - high cardinality indexes are preferred for filtering and joins. Option A (duplicate values) is the opposite of cardinality. Option C (null values) is unrelated to cardinality definition.

.NET Framework data providers have four core components: Connection (establishes database connection), Command (executes SQL), DataReader (forward-only read access), and DataAdapter (fills DataSet). DataSet itself is a separate object, not a provider component.

ADO.NET's fundamental objects are DataReader (connected, forward-only read) and Dataset (disconnected, in-memory cache). DataAdapter and DataRelation are supporting objects, while DataTable and DataRow are Dataset contents.