Why a primary key should contain only one attribute?
Why a primary key should contain only one attribute? A. Easy for Indexing and connecting to a foreign key B. Easy for documentation C. Increase security D. None correct Answer: Option A
Why a primary key should contain only one attribute? A. Easy for Indexing and connecting to a foreign key B. Easy for documentation C. Increase security D. None correct Answer: Option A
Why they say a composite attribute is not good for a database? A. Difficult to do a documentation B. Not good for security C. Difficult to do search, sort and format D. All correct Answer: Option D
If you develop a desktop app, which methodology is wrong for that? A. Waterfall B. Rapid App Development C. Agile D. All correct Answer: Option A
Which project is suitable for Agile model? A. Hardware software B. Embedded Firmware C. Fast changing app D. All correct Answer: Option C
What skill is mostly likely to get the benefit from this subject? A. 3D Graphics B. Web Programming C. CCNA D. All correct Answer: Option B
If having a primary key of {A} but C depends on B, which normalization needs to use? A. 1NF B. 2NF C. 3NF D. None correct Answer: Option C
If having a composite key of {A, B} but C depends on D, which normalization needs to use? A. 1NF B. 2NF C. 3NF D. None correct Answer: Option C
If having a composite key of {A, B} but C depends on B, which normalization needs to use? A. 1NF B. 2NF C. 3NF D. None correct Answer: Option C
If having a composite key of {A, B} but C depends on A, which normalization needs to use? A. 1NF B. 2NF C. 3NF D. None correct Answer: Option B
Which normalization that does not set a foreign key? A. 1NF B. 2NF C. 3NF D. None correct Answer: Option B