1D0-541 Sample Questions Answers

The intersection oftwo relations

ACartesian product of two relations

Arestricted Cartesian product of two relations

The Cartesian product oftwo union-compatible relations

Logical

Physical

Conceptual

Implementation

Entity integrity

Necessary data

Referential integrity

Referential foreign integrity

Data Query Language

Database Entity Language

Data Definition Language

Data Manipulation Language

File locking

User authorization

Parity checks

Integrity controls

There is no relationship between changes in STUDENT(Student_Number) and HOUSING(Student_Number).

When STUDENT(Student_Number) is changed or deleted, this modification or deletion will automatically be reflected in HOUSING(Student_Number).

Modifications to HOUSING(Student_Number) are automatically reflected in changes to STUDENT(Student_Number), but deletions are not permitted.

Modifications to STUDENT(Student_Number) are automatically reflected in changes to HOUSING(Student_Number). For a deletion to occur fromSTUDENT(Student_Number), it must first occur in HOUSING(Student_Number).

Union

Intersection

Natural join

Cartesian product

Two-tier using thin client

Three-tier using fat client

Three-tier using thin client

Centralized mainframe with terminal client

SELECT * FROM

Registration WHERE

Course_Code = #

SELECT * FROM

Registration WHERE

Course_Code LIKE _

SELECT* FROM

Registration WHERE

Course_Code LIKE %

SELECT * FROM

Registration WHERE

Course Code = %

Durability

Consistency

Isolation

Atomicity

Only an update anomaly would occur.

An insertion anomaly would occur.

A deletion anomaly would occur.

An update anomaly and a deletion anomaly would occur.

Option A

Option B

Option C

Option D

SELECT *

FROM Orders

WHERE Order_Date LIKE _02

ORDER BY Amount;

SELECT (Order_Date, Amount)

FROM Orders

WHERE Order_Date LIKE %02

ORDER BY Amount;

SELECT *

FROM Orders

WHERE Order_Date LIKE _02

ORDER BY Order_No;

SELECT *

FROM Orders

WHERE Order_Date LIKE %02

ORDER BY Amount;

If a parent key is deleted, any child keys referenced by the parent key are automatically deleted.

If a parent key is deleted, no test is made for referential integrity.

If any child key references a parent key, the record containing the parent key cannot be deleted.

If a parent key is deleted, all child keys are automatically set to a specified value.

CREATE VIEW Emp_Dept AS SELECT

Last_Name, First_Name, Dept_ID FROM

Employee;

UPDATE VIEW Emp_Dept

AS SELECT * FROM

Employee;

UPDATE VIEW Emp_Dept AS SELECT

Last_Name, First_Name, Dept_ID FROM

Employee;

CREATE VIEW Emp_Dept

AS SELECT * FROM

Employee WHERE ID = 0001

AND ID = 0002 AND ID =

0003 AND ID = 0004;

Rollback

Deadlock

Dirty read

No problem has occurred.

Option A

Option B

Option C

Option D

1NF

1NFand2NF

1NF,2NFand3NF

1NF,2NF,3NFandBCNF

UPDATE Sales_Rep_No

IN Orders

SET(Sales_Rep_No = 110

WHERE Sales_Rep_No = 108);

UPDATE Orders

SET Sales_Rep_No = 110

WHERE Sales_Rep_No = 108;

UPDATE Orders

SET Sales_Rep_No = 110;

UPDATE Orders

WHERE Sales_Rep_No = 108

SET Sales_Rep_No = 110;

Fat client

Enterprise client

Thin client

Terminal client

View

Data dictionary

Database control language

Database management system

Option A

Option B

Option C

Option D

UPDATE Recreation SET Activity,

Activity_Fee (‘Tennis’,100) WHERE

Student_ID = 1003;

UPDATE TABLE Recreation ALTER COLUMN ACTIVITY

SET ACTIVITY =‘Tennis', Activity_Fee = 100 WHERE

Student__ID = 1003 AND Activity = wimming?AND Activity=

?wimming?

UPDATE Recreation SET Activity =

‘Tennis', Activity_Fee = 100 WHERE

Student_ID = 1003 AND Activity =

'Swimming';

DELETE Activity FROM

Recreation WHERE

Student_ID = 1003; INSERT

INTO Recreation VALUES (1003,‘Tennis', 100);

1 = attribute, 2 = entity, 3 = relationship

1 = entity, 2 = relationship, 3 = attribute

1 = relationship, 2 = entity, 3 = attribute

1 = relationship, 2 = attribute, 3 = entity

INSERT INTO Employee

VALUES(0005, Tim, Bogart, 03-15-77);

INSERT INTO Employee(Emp_ID, First_Name, Last_Name, Birth_Date)

VALUES(0004, Tim, Bogart, 03-15-77);

INSERT INTO Employee(Emp_ID, First_Name, Last_Name, Birth_Date)

VALUES(0005, Tim, Bogart, 03-05-77);

INSERT INTO Employee(Emp_ID, First_Name, Last_Name, Birth_Date)

VALUES(0005, Tim, Bogart, 03-05-77);

One-to-many and recursive

Complex, recursive, and many-to-many

Redundant, recursive, and one-to-many

One-to-many and one-to-one

If a parent key is deleted, any child keys referenced by the parent key are automatically deleted.

If any child key references a parent key, the record containing the parent key cannot be deleted.

If a parent key is deleted,all child keys are automatically set to a specified value.

If a parent key is deleted, no test is made for referential integrity.

Management of data redundancy, increased data integrity, increased data dependence, and increased application program flexibility.

Consistency of data, adherence to standards, managed concurrency, and increased software complexity.

Increased data access, increased data backup and recovery, data sharing, and consistency of data.

Increased datasecurity, increased data integrity, increased data independence, and decreased data separation.

SELECT *

FROM Dept1_Parts

EXCEPT

(SELECT Part_ID

FROM Dept2_Parts);

SELECT *

FROM Dept1_Parts

MINUS

(SELECT Part_ID

FROM Dept2_Parts);

SELECT *

FROM Dept1_Parts

DIFFERENCE

(SELECT Part_ID

FROM Dept2_Parts);

SELECT *

FROM Dept1_Parts

DIFFERENCE

(SELECT Part_ID

FROM Dept2_Parts);

Entity integrity

Domain constraint

Referential integrity

Enterprise constraint

Union

Difference

Projection

Intersection

BUILDING(Building_ID, Bldg_Name, Location, Room_Count)

Primary Key Building_ID RESIDENT(R_ID, Room_Num,

Res_Name, Building_ID) Primary Key R_ID

BUILDING(Building_ID, Bldg_Name, Location, Room_Count)

Primary Key BUILDING RESIDENT(R_ID, Room_Num,

Res_Name, Building_ID) Primary Key RESIDENT

BUILDING(Building_ID, Bldg_Name, Location, Room_Count) Primary Key BUILDING ForeignKey BUILDING(Building_ID) references RESIDENT(Building_ID) RESIDENT(R_ID, Room_Num, Res_Name, Building_ID) Primary Key RESIDENT

BUILDING(Building_ID, Bldg_Name, Location, Room_Count)

Primary Key Building_ID RESIDENT(R_ID, Room_Num,

Res_Name, Building_ID) Primary Key R_ID Foreign Key

Building_ID references BUILDING(Building_ID)

Data that is stored as tables

Software that manipulates data

Data that is stored in a structured manner

Data records that are stored sequentially in a file

STUDENT(

Student_Number: integer NOT NULL

Name: variable length character string length 20 NOT NULL)

Primary Key Student_Number

CLASS(

Class_Num: integer NOT NULL

Class_Name: integer NOT NULL)

Primary Key Class_Num

STUDENT(

Student_Number: integer NOT NULL

Name: variable length character string length 20 NOT NULL)

Primary Key Student_Number

CLASS(

Class_Num: integer NOT NULL

Class_Name: integer NOT NULL)

Primary Key Class_Num

Foreign Key Class_Num References STUDENT

STUDENT(

Student_Number: integer NOT NULL

Name: variable length character string length 20 NOT NULL)

Primary Key Student_Number

STU_CLASS(

Student_Number: integer NOT NULL

Class_Num: integer NOT NULL)

Primary Key Student_Number

CLASS(

Class_Num: integer NOT NULL

Class_Name: integer NOT NULL)

Primary Key Class_Num

STUDENT(

Student_Number: integer NOT NULL

Name: variable length character string length 20 NOT NULL)

Primary Key Student_Number

STU_CLASS(

Student_Number: integer NOT NULL

Class_Num: integer NOT NULL)

Primary Key Student_Number, Class_Num

CLASS(

Class_Num: integer NOT NULL

Class_Name: integer NOT NULL)

Primary Key Class_Num