PrepAway - Latest Free Exam Questions & Answers

which column in the Employee table should you a create a unique constraint?

You administer a Microsoft SQL Server 2012 database. The database contains a table
named Employee. Part of the Employee table is shown in the exhibit. (Click the Exhibit
button.)

Confidential information about the employees is stored in a separate table named
EmployeeData. One record exists within EmployeeData for each record in the Employee
table. You need to assign the appropriate constraints and table properties to ensure data

integrity and visibility. On which column in the Employee table should you a create a unique
constraint?

PrepAway - Latest Free Exam Questions & Answers

A.
DateHired

B.
DepartmentID

C.
EmployeelD

D.
EmployeeNum

E.
FirstName

F.
JobTitle

G.
LastName

H.
MiddleName

I.
ReportsToID

4 Comments on “which column in the Employee table should you a create a unique constraint?

  1. Henk says:

    C

    “One record exists within EmployeeData for each record in the Employee
    table.”

    This means that each unique row in Employee table is linked to a row in the EmployeeData table. This describes a UID, a PK.




    0



    0
    1. Milen says:

      No. D is correct – “On which column in the Employee table should you a create a unique
      constraint?” you need to define uniqueness not referential integrity between both tables.




      0



      0

Leave a Reply