Get WGU Data Management - Foundations Exam Practice Questions - Real and Updated

Answer : D

A valid SELECT statement in SQL follows this basic syntax:

sql

SELECT column1, column2

FROM table_name

WHERE condition;

The correct option D follows this syntax correctly.

Why Other Options Are Incorrect:

Option A (Incorrect): SQL does not use double quotes (') around column/table names unless explicitly required in some databases.

Option B (Incorrect): The WHERE clause must appear after the FROM clause.

Option C (Incorrect): ALL is not a valid keyword in standard SQL queries.

Thus, Option D follows the correct SQL syntax.

Answer : A

In databases, primary keys are often set to auto-increment so that new rows automatically receive unique values. However, one common error is manually inserting a value into an auto-incremented primary key column, which overrides the automatic numbering and may cause conflicts.

Example of Auto-Increment Setup:

sql

CREATE TABLE Users (

UserID INT AUTO_INCREMENT PRIMARY KEY,

Username VARCHAR(50)

);

Incorrect Insert (Error-Prone Approach):

sql

INSERT INTO Users (UserID, Username) VALUES (100, 'Alice');

This manually overrides the auto-increment, which can lead to duplicate key errors.

Correct Insert (Avoiding Errors):

sql

INSERT INTO Users (Username) VALUES ('Alice');

The database assigns UserID automatically, preventing conflicts.

Why Other Options Are Incorrect:

Option B (Failing to set a numeric value) (Incorrect): The database automatically assigns values when AUTO_INCREMENT is used.

Option C (Designating multiple primary keys) (Incorrect): While incorrect, most databases will prevent this at creation time.

Option D (Forgetting to specify which is the auto-increment column) (Incorrect): If AUTO_INCREMENT is set, the database handles numbering automatically.

Thus, the most common error is Inserting a value and overriding auto-increment, which can cause duplicate key errors and data inconsistencies.

Answer : C

An intangible entity is an entity that does not have a physical presence but still holds meaning in a database. These entities represent concepts, relationships, or abstract data that exist in a logical sense.

Example Usage in Databases:

Customer Loyalty Status (Gold, Silver, Bronze)

The loyalty level is an intangible entity since it is derived from other data (purchase history).

Online User Sessions

A session ID exists logically in the system but does not have a tangible presence like a product or employee.

Why Other Options Are Incorrect:

Option A (Concrete entity) (Incorrect): No such formal term in database design.

Option B (Tangible entity) (Incorrect): Represents something physical, like an employee or product.

Option D (Physical entity) (Incorrect): Refers to data stored on disk, like database tables or indexes.

Thus, the correct answer is Intangible entity, as it only exists in a logical sense within the database.

Answer : C

The given diagram represents a unary relationship (also called a recursive relationship), which occurs when an entity is related to itself. In this case, salespersons back each other up, meaning a salesperson is associated with another salesperson from the same entity.

Key Observations from the Diagram:

Single Entity (Salesperson)

The table contains only one entity type, Salesperson, which has attributes such as Salesperson Number, Name, Commission, Percentage, and Year of Hire.

Self-Referencing Relationship (Backs-up and Backed-up by)

The diagram shows that a salesperson can back up another salesperson.

This means that the relationship exists within the same entity rather than between two different entities.

Cardinality (One-to-One Relationship in a Unary Form)

The notation ( |---| ) in the ER diagram indicates a one-to-one recursive relationship.

One salesperson can back up only one other salesperson, and each salesperson is backed up by only one.

Answer : B

The correct syntax for inserting a new row into a table follows this structure:

Standard SQL INSERT Syntax:

sql

INSERT INTO TableName (Column1, Column2, ...)

VALUES (Value1, Value2, ...);

For this scenario:

sql

INSERT INTO Employee (Name) VALUES ('John Doe');

Why Other Options Are Incorrect:

Option A (Incorrect): Uses incorrect syntax { ... }, which is not valid SQL syntax.

Option C (Incorrect): Does not specify the column name, which causes an error.

Option D (Incorrect): Misses the INTO keyword, which is required in standard SQL.

Thus, the correct syntax is Option B, ensuring a properly formatted insert statement.