BIS 245 Week 2 Lab - Skills Development in Visio
Questions and Answers with Complete Solutions
Keller Graduate School of Management • DeVry University • 2026/2027 Updated • A+ Verified Grade
Lab Examination • 90 Multiple-Choice Questions • Cognitive Levels: 35% Recall, 45% Application, 20%
Analysis
Total Questions 90
6 (Database Fundamentals, Visio Intro, ERD Fundamentals, ERD Creation,
Sections
Cardinality, Documentation)
70% application-based (Visio procedures and ERD construction), 30% direct
Question Style
recall
Format Multiple choice, 4 options (A-D), ONE correct answer
Database and Visio-specific reasoning with Keller lab alignment and A+ quality
Rationale
criteria
Section 1: Database Fundamentals and Data Modeling Concepts (Entities, Attributes,
Relationships, & Business Rules)
Q1: A graduate business student is explaining database fundamentals to a peer. Which
statement BEST distinguishes data from information in a business context?
A. Data is processed output; information is raw input
B. Data consists of raw, unprocessed facts; information is data that has been processed, organized, or
structured to provide meaning for decision-making [CORRECT]
C. Data and information are interchangeable terms referring to stored records
D. Information refers to numeric values; data refers to text values
Correct Answer: B
Rationale: Data are raw, unprocessed facts (e.g., '47', 'Phoenix', '2024') lacking context. Information is data that has
been processed, organized, or interpreted to be useful for decision-making (e.g., '47 employees in the Phoenix office as
of 2024'). Understanding this distinction is foundational to the BIS 245 data modeling unit, as the database lifecycle
transforms data into information through structured storage, retrieval, and presentation layers.
Q2: A database administrator (DBA) is configuring permissions, security, backup scheduling,
and concurrent access control for a corporate relational database. Which software system is the
DBA primarily managing?
A. Database Management System (DBMS) [CORRECT]
B. Microsoft Excel
C. Entity-Relationship Diagram (ERD)
D. Standalone text file storage system
Correct Answer: A
Rationale: A Database Management System (DBMS) is software that enables users to define, create, maintain, and
control access to a database, providing features such as data definition, data manipulation, security, backup/recovery,
concurrency control, and integrity enforcement. Examples include Microsoft SQL Server, Oracle, MySQL, PostgreSQL,
and Microsoft Access. An ERD is a design artifact, not software; Excel is a spreadsheet, not a true DBMS; text files lack
DBMS functionality.
Page 1
,BIS 245 Week 2 Lab - Skills Development in Visio | Keller Graduate School 2026/2027 Updated | A+ Verified Grade
Q3: A business analyst is designing a relational database for a retail inventory system. In the
relational model, data is organized into two-dimensional structures consisting of columns
(attributes) and rows (tuples). What is the correct terminology for these structures?
A. Files and records
B. Tables (relations), with columns as attributes and rows as tuples (records) [CORRECT]
C. Spreadsheets and cells
D. Hierarchical trees and branches
Correct Answer: B
Rationale: In the relational model proposed by E.F. Codd, data is organized into relations (tables) consisting of
attributes (columns) and tuples (rows/records). Each relation has a unique name, each attribute has a domain (set of
allowable values), and each tuple represents a single occurrence of the entity. Tables provide logical structure
independent of physical storage, supporting data independence, normalization, and SQL querying. Keller BIS 245
emphasizes this terminology as the foundation for entity-relationship modeling in Visio.
Q4: A student is completing the three-stage data modeling process for a Keller BIS 245 lab
assignment. Which sequence represents the correct progression from conceptual to physical
model?
A. Physical model, Logical model, Conceptual model
B. Conceptual model (high-level, entities and relationships) then Logical model (attributes, keys,
normalization) then Physical model (table definitions, data types, DBMS implementation) [CORRECT]
C. Logical model, Conceptual model, Physical model
D. All three models are created simultaneously with no particular order
Correct Answer: B
Rationale: Data modeling follows a progressive refinement sequence: Conceptual (high-level entity-relationship
diagram with no attributes, focusing on what data is needed), Logical (adds attributes, primary/foreign keys,
normalization, includes relationships and cardinality, independent of specific DBMS), then Physical (defines tables,
columns with data types, constraints, indexes for a specific DBMS like SQL Server or Oracle). This progression aligns
with the BIS 245 Week 2 Visio lab where students create logical-level ERDs using Crow's Foot notation.
Q5: When creating an ERD for a hospital database, a designer identifies ENTITIES such as
Patient, Doctor, Appointment, and Prescription. Which statement BEST describes an entity in
data modeling?
A. A single property of an object, such as a name or date
B. A person, place, object, event, or concept about which the organization wants to collect and store data
[CORRECT]
C. A specific value of an attribute, such as 'John Smith'
D. A connection between two unrelated tables
Correct Answer: B
Rationale: An entity is a person, place, object, event, or concept of interest to the organization that the database should
track. Entities become tables in the physical database, with each instance (row) representing one occurrence. Examples:
Patient entity, Doctor entity, Appointment entity. Entities are nouns, identified during requirements gathering, and
named in singular form (Patient, not Patients). Distinguishing entities from attributes and relationships is essential for
correct ERD construction in Visio.
Page 2
,BIS 245 Week 2 Lab - Skills Development in Visio | Keller Graduate School 2026/2027 Updated | A+ Verified Grade
Q6: A database designer is determining whether an entity should be classified as a STRONG
entity or a WEAK entity. Which characteristic distinguishes a weak entity from a strong entity?
A. A weak entity has many attributes; a strong entity has few
B. A weak entity cannot be uniquely identified by its own attributes alone and depends on a parent (strong)
entity through an identifying relationship; a strong entity has its own primary key [CORRECT]
C. A weak entity is one with weak data types; a strong entity uses strong data types
D. A strong entity must always have a foreign key; a weak entity does not
Correct Answer: B
Rationale: A strong entity is independent, with its own primary key attributes (e.g., Customer with CustomerID). A weak
entity depends on a parent entity for identification through an identifying relationship; its primary key incorporates the
parent's primary key (e.g., Dependent entity whose PK includes EmployeeID FK). Weak entities are depicted with
double rectangle in Chen notation and as an entity with a parent connector in Visio Crow's Foot notation. They cannot
exist without their parent entity.
Q7: A student is naming entities and attributes for an ERD in a Visio lab. Which naming
convention represents the recommended Keller BIS 245 standard for entity names?
A. Plural nouns (Customers, Orders, Products) to represent the table collection
B. Singular nouns in title case (Customer, Order, Product) representing one instance of the entity
[CORRECT]
C. Verbs (Purchase, Sell, Ship) representing the action
D. Abbreviations (CUST, ORD, PROD) to save diagram space
Correct Answer: B
Rationale: Best practice for entity naming in ERDs is singular nouns in title case (Customer, Order, Product,
Employee). Singular nouns represent one instance of the entity, not the entire collection. This convention improves
clarity, aligns with object-oriented design, and translates cleanly to physical tables. Plural names cause ambiguity in
relationships ('A Customers places many Orders' is grammatically incorrect). Verbs represent relationships, not entities.
Abbreviations reduce readability and are not appropriate for professional ERDs.
Q8: When designing an entity in a Visio ERD, a student must classify attributes such as
First_Name, Last_Name, Date_of_Birth, and Full_Name. The Full_Name attribute is generated by
concatenating First_Name and Last_Name, so it is not stored in the database. What type of
attribute is Full_Name?
A. Simple attribute
B. Composite attribute
C. Derived attribute [CORRECT]
D. Multivalued attribute
Correct Answer: C
Rationale: A derived attribute is calculated or computed from other attributes and is not stored in the database to avoid
data redundancy. In this case, Full_Name can be derived from First_Name + Last_Name at query time. Storing derived
attributes risks inconsistency when source attributes change. In Visio, derived attributes are sometimes marked with an
asterisk or noted in the documentation. Simple attributes are atomic (cannot be divided); composite attributes can be
divided into sub-parts (e.g., Address); multivalued attributes can have multiple values (e.g., Phone_Number).
Page 3
, BIS 245 Week 2 Lab - Skills Development in Visio | Keller Graduate School 2026/2027 Updated | A+ Verified Grade
Q9: A student is designing a Customer entity and considers storing Address as a single field.
However, the address has multiple components (Street, City, State, ZIP code) that the business
wants to query independently. Which type of attribute is Address in this case?
A. Simple attribute (atomic)
B. Composite attribute (can be divided into sub-attributes) [CORRECT]
C. Derived attribute (computed)
D. Multivalued attribute (multiple values per entity)
Correct Answer: B
Rationale: A composite attribute can be divided into smaller sub-attributes (e.g., Address = Street + City + State +
ZIP). In relational database design, composite attributes are typically split into separate columns for query efficiency
and atomicity (1NF). In Visio ERD, composite attributes can be shown hierarchically. A simple attribute is atomic; a
derived attribute is computed from other attributes; a multivalued attribute has multiple values (e.g., a person with
multiple phone numbers, which would be resolved into a separate entity in 1NF).
Q10: An employee entity has a Phone_Number attribute where one employee can have multiple
phone numbers (Home, Mobile, Work). What type of attribute is Phone_Number, and how should
it be resolved in a normalized relational design?
A. Simple attribute; keep as single column
B. Multivalued attribute; resolve by creating a separate entity (e.g., Employee_Phone) with a 1:M
relationship to Employee, ensuring first normal form (1NF) compliance [CORRECT]
C. Composite attribute; combine with address
D. Derived attribute; compute from email
Correct Answer: B
Rationale: A multivalued attribute can hold multiple values for a single entity instance, which violates first normal form
(1NF) requiring atomic values. To normalize, create a separate entity (e.g., Employee_Phone) with its own primary key
(or composite key using EmployeeID + Phone_Type), connected to Employee via a 1:M relationship. In Visio,
multivalued attributes may be shown with a double oval (Chen notation) or as a separate related entity. Resolving
multivalued attributes is essential for A+ quality ERD design.
Q11: A database designer is identifying candidate keys for a Student entity, considering
Student_ID, SSN, and Email_Address as potential unique identifiers. What is the definition of a
candidate key?
A. Any attribute that may be repeated in the table
B. An attribute or minimal combination of attributes that uniquely identifies each row (tuple) in a table
[CORRECT]
C. An attribute that is always null
D. A foreign key referencing another table
Correct Answer: B
Rationale: A candidate key is an attribute (or minimal combination of attributes) that uniquely identifies each row in a
table and cannot be null (entity integrity). Multiple candidate keys may exist (e.g., Student_ID, SSN, Email). One
candidate key is selected as the primary key (PK); the others become alternate keys. Surrogate keys are artificial (e.g.,
auto-increment integers) when no natural unique identifier exists or for performance/privacy. Understanding candidate
keys is essential for selecting appropriate primary keys in Visio ERD design.
Page 4
Questions and Answers with Complete Solutions
Keller Graduate School of Management • DeVry University • 2026/2027 Updated • A+ Verified Grade
Lab Examination • 90 Multiple-Choice Questions • Cognitive Levels: 35% Recall, 45% Application, 20%
Analysis
Total Questions 90
6 (Database Fundamentals, Visio Intro, ERD Fundamentals, ERD Creation,
Sections
Cardinality, Documentation)
70% application-based (Visio procedures and ERD construction), 30% direct
Question Style
recall
Format Multiple choice, 4 options (A-D), ONE correct answer
Database and Visio-specific reasoning with Keller lab alignment and A+ quality
Rationale
criteria
Section 1: Database Fundamentals and Data Modeling Concepts (Entities, Attributes,
Relationships, & Business Rules)
Q1: A graduate business student is explaining database fundamentals to a peer. Which
statement BEST distinguishes data from information in a business context?
A. Data is processed output; information is raw input
B. Data consists of raw, unprocessed facts; information is data that has been processed, organized, or
structured to provide meaning for decision-making [CORRECT]
C. Data and information are interchangeable terms referring to stored records
D. Information refers to numeric values; data refers to text values
Correct Answer: B
Rationale: Data are raw, unprocessed facts (e.g., '47', 'Phoenix', '2024') lacking context. Information is data that has
been processed, organized, or interpreted to be useful for decision-making (e.g., '47 employees in the Phoenix office as
of 2024'). Understanding this distinction is foundational to the BIS 245 data modeling unit, as the database lifecycle
transforms data into information through structured storage, retrieval, and presentation layers.
Q2: A database administrator (DBA) is configuring permissions, security, backup scheduling,
and concurrent access control for a corporate relational database. Which software system is the
DBA primarily managing?
A. Database Management System (DBMS) [CORRECT]
B. Microsoft Excel
C. Entity-Relationship Diagram (ERD)
D. Standalone text file storage system
Correct Answer: A
Rationale: A Database Management System (DBMS) is software that enables users to define, create, maintain, and
control access to a database, providing features such as data definition, data manipulation, security, backup/recovery,
concurrency control, and integrity enforcement. Examples include Microsoft SQL Server, Oracle, MySQL, PostgreSQL,
and Microsoft Access. An ERD is a design artifact, not software; Excel is a spreadsheet, not a true DBMS; text files lack
DBMS functionality.
Page 1
,BIS 245 Week 2 Lab - Skills Development in Visio | Keller Graduate School 2026/2027 Updated | A+ Verified Grade
Q3: A business analyst is designing a relational database for a retail inventory system. In the
relational model, data is organized into two-dimensional structures consisting of columns
(attributes) and rows (tuples). What is the correct terminology for these structures?
A. Files and records
B. Tables (relations), with columns as attributes and rows as tuples (records) [CORRECT]
C. Spreadsheets and cells
D. Hierarchical trees and branches
Correct Answer: B
Rationale: In the relational model proposed by E.F. Codd, data is organized into relations (tables) consisting of
attributes (columns) and tuples (rows/records). Each relation has a unique name, each attribute has a domain (set of
allowable values), and each tuple represents a single occurrence of the entity. Tables provide logical structure
independent of physical storage, supporting data independence, normalization, and SQL querying. Keller BIS 245
emphasizes this terminology as the foundation for entity-relationship modeling in Visio.
Q4: A student is completing the three-stage data modeling process for a Keller BIS 245 lab
assignment. Which sequence represents the correct progression from conceptual to physical
model?
A. Physical model, Logical model, Conceptual model
B. Conceptual model (high-level, entities and relationships) then Logical model (attributes, keys,
normalization) then Physical model (table definitions, data types, DBMS implementation) [CORRECT]
C. Logical model, Conceptual model, Physical model
D. All three models are created simultaneously with no particular order
Correct Answer: B
Rationale: Data modeling follows a progressive refinement sequence: Conceptual (high-level entity-relationship
diagram with no attributes, focusing on what data is needed), Logical (adds attributes, primary/foreign keys,
normalization, includes relationships and cardinality, independent of specific DBMS), then Physical (defines tables,
columns with data types, constraints, indexes for a specific DBMS like SQL Server or Oracle). This progression aligns
with the BIS 245 Week 2 Visio lab where students create logical-level ERDs using Crow's Foot notation.
Q5: When creating an ERD for a hospital database, a designer identifies ENTITIES such as
Patient, Doctor, Appointment, and Prescription. Which statement BEST describes an entity in
data modeling?
A. A single property of an object, such as a name or date
B. A person, place, object, event, or concept about which the organization wants to collect and store data
[CORRECT]
C. A specific value of an attribute, such as 'John Smith'
D. A connection between two unrelated tables
Correct Answer: B
Rationale: An entity is a person, place, object, event, or concept of interest to the organization that the database should
track. Entities become tables in the physical database, with each instance (row) representing one occurrence. Examples:
Patient entity, Doctor entity, Appointment entity. Entities are nouns, identified during requirements gathering, and
named in singular form (Patient, not Patients). Distinguishing entities from attributes and relationships is essential for
correct ERD construction in Visio.
Page 2
,BIS 245 Week 2 Lab - Skills Development in Visio | Keller Graduate School 2026/2027 Updated | A+ Verified Grade
Q6: A database designer is determining whether an entity should be classified as a STRONG
entity or a WEAK entity. Which characteristic distinguishes a weak entity from a strong entity?
A. A weak entity has many attributes; a strong entity has few
B. A weak entity cannot be uniquely identified by its own attributes alone and depends on a parent (strong)
entity through an identifying relationship; a strong entity has its own primary key [CORRECT]
C. A weak entity is one with weak data types; a strong entity uses strong data types
D. A strong entity must always have a foreign key; a weak entity does not
Correct Answer: B
Rationale: A strong entity is independent, with its own primary key attributes (e.g., Customer with CustomerID). A weak
entity depends on a parent entity for identification through an identifying relationship; its primary key incorporates the
parent's primary key (e.g., Dependent entity whose PK includes EmployeeID FK). Weak entities are depicted with
double rectangle in Chen notation and as an entity with a parent connector in Visio Crow's Foot notation. They cannot
exist without their parent entity.
Q7: A student is naming entities and attributes for an ERD in a Visio lab. Which naming
convention represents the recommended Keller BIS 245 standard for entity names?
A. Plural nouns (Customers, Orders, Products) to represent the table collection
B. Singular nouns in title case (Customer, Order, Product) representing one instance of the entity
[CORRECT]
C. Verbs (Purchase, Sell, Ship) representing the action
D. Abbreviations (CUST, ORD, PROD) to save diagram space
Correct Answer: B
Rationale: Best practice for entity naming in ERDs is singular nouns in title case (Customer, Order, Product,
Employee). Singular nouns represent one instance of the entity, not the entire collection. This convention improves
clarity, aligns with object-oriented design, and translates cleanly to physical tables. Plural names cause ambiguity in
relationships ('A Customers places many Orders' is grammatically incorrect). Verbs represent relationships, not entities.
Abbreviations reduce readability and are not appropriate for professional ERDs.
Q8: When designing an entity in a Visio ERD, a student must classify attributes such as
First_Name, Last_Name, Date_of_Birth, and Full_Name. The Full_Name attribute is generated by
concatenating First_Name and Last_Name, so it is not stored in the database. What type of
attribute is Full_Name?
A. Simple attribute
B. Composite attribute
C. Derived attribute [CORRECT]
D. Multivalued attribute
Correct Answer: C
Rationale: A derived attribute is calculated or computed from other attributes and is not stored in the database to avoid
data redundancy. In this case, Full_Name can be derived from First_Name + Last_Name at query time. Storing derived
attributes risks inconsistency when source attributes change. In Visio, derived attributes are sometimes marked with an
asterisk or noted in the documentation. Simple attributes are atomic (cannot be divided); composite attributes can be
divided into sub-parts (e.g., Address); multivalued attributes can have multiple values (e.g., Phone_Number).
Page 3
, BIS 245 Week 2 Lab - Skills Development in Visio | Keller Graduate School 2026/2027 Updated | A+ Verified Grade
Q9: A student is designing a Customer entity and considers storing Address as a single field.
However, the address has multiple components (Street, City, State, ZIP code) that the business
wants to query independently. Which type of attribute is Address in this case?
A. Simple attribute (atomic)
B. Composite attribute (can be divided into sub-attributes) [CORRECT]
C. Derived attribute (computed)
D. Multivalued attribute (multiple values per entity)
Correct Answer: B
Rationale: A composite attribute can be divided into smaller sub-attributes (e.g., Address = Street + City + State +
ZIP). In relational database design, composite attributes are typically split into separate columns for query efficiency
and atomicity (1NF). In Visio ERD, composite attributes can be shown hierarchically. A simple attribute is atomic; a
derived attribute is computed from other attributes; a multivalued attribute has multiple values (e.g., a person with
multiple phone numbers, which would be resolved into a separate entity in 1NF).
Q10: An employee entity has a Phone_Number attribute where one employee can have multiple
phone numbers (Home, Mobile, Work). What type of attribute is Phone_Number, and how should
it be resolved in a normalized relational design?
A. Simple attribute; keep as single column
B. Multivalued attribute; resolve by creating a separate entity (e.g., Employee_Phone) with a 1:M
relationship to Employee, ensuring first normal form (1NF) compliance [CORRECT]
C. Composite attribute; combine with address
D. Derived attribute; compute from email
Correct Answer: B
Rationale: A multivalued attribute can hold multiple values for a single entity instance, which violates first normal form
(1NF) requiring atomic values. To normalize, create a separate entity (e.g., Employee_Phone) with its own primary key
(or composite key using EmployeeID + Phone_Type), connected to Employee via a 1:M relationship. In Visio,
multivalued attributes may be shown with a double oval (Chen notation) or as a separate related entity. Resolving
multivalued attributes is essential for A+ quality ERD design.
Q11: A database designer is identifying candidate keys for a Student entity, considering
Student_ID, SSN, and Email_Address as potential unique identifiers. What is the definition of a
candidate key?
A. Any attribute that may be repeated in the table
B. An attribute or minimal combination of attributes that uniquely identifies each row (tuple) in a table
[CORRECT]
C. An attribute that is always null
D. A foreign key referencing another table
Correct Answer: B
Rationale: A candidate key is an attribute (or minimal combination of attributes) that uniquely identifies each row in a
table and cannot be null (entity integrity). Multiple candidate keys may exist (e.g., Student_ID, SSN, Email). One
candidate key is selected as the primary key (PK); the others become alternate keys. Surrogate keys are artificial (e.g.,
auto-increment integers) when no natural unique identifier exists or for performance/privacy. Understanding candidate
keys is essential for selecting appropriate primary keys in Visio ERD design.
Page 4
