[03/Charles/03]

Attribute level

Logical

To capture historical changes

False

False

True

Hubs = Contain business keys Links = Connect Hubs and Satellites Satellites = Contain historical data Classification = Based on the attribute level

Logical identifiers = Used instead of physical entity names Entities = Represented as tables or views Satellites = Do not split the data No satellite splits = Classification is on the attribute level

Hubs = Contain business keys Links = Connect Hubs and Satellites Satellites = Contain historical data Entities = Represented as tables or views

To provide a conceptual representation of the data needed to support business processes

Fundamental objects or concepts that the organization needs to track

Characteristics of entities

Connections between entities

Entity-relationship diagrams (ERDs) and Unified Modeling Language (UML) diagrams

Simplify data integration

Data silos

How the data will be stored and organized in the database

Logical data models are used to create physical data models

True

True

False

False

True

True

False

True

False

Entities = Fundamental objects or concepts that the organization needs to track Attributes = Characteristics of entities Relationships = Define the connections between entities Modeling Techniques = Used to create logical data models, such as ERDs and UML diagrams

Understand data needs = Identify and eliminate data silos Improve data quality and consistency = Simplify data integration Facilitate data governance = Create physical data models specific to a DBMS

Logical data models are created independently of any specific DBMS or physical data storage technology = True Logical data models are used to create physical data models = True Logical data models help organizations to identify and eliminate data silos = True Logical data models are specific to a particular DBMS = False

Entity-relationship diagrams (ERDs) = Used to create logical data models Unified Modeling Language (UML) diagrams = Used to create logical data models Data Vault 2.0 Hubs contain business keys = Not related to creating logical data models Satellites in Data Vault 2.0 always split the data into different tables = Not related to creating logical data models

Entities = Fundamental objects or concepts that the organization needs to track Attributes = Characteristics of entities Relationships = Define the connections between entities Logical data models = Created independently of any specific DBMS or physical data storage technology

Logical data models help organizations to identify and eliminate data silos = True Relationships in a logical data model define the connections between attributes = False Attributes in a logical data model are the characteristics of relationships = False Entities in a logical data model are the fundamental objects or concepts that the organization needs to track = True

Understand their data needs = Purpose of logical data models Identify and eliminate data silos = Purpose of logical data models Improve data quality and consistency = Purpose of logical data models Create physical data models specific to a DBMS = Not a purpose of logical data models

Entities = Fundamental objects or concepts that the organization needs to track Attributes = Characteristics of entities Relationships = Define the connections between entities Modeling Techniques = Used to create logical data models, such as ERDs and UML diagrams

Logical data models help organizations to understand their data needs = Important Logical data models are specific to a particular DBMS = Not important Logical data models are used to create physical data models = Important Logical data models are created using a variety of modeling techniques = Important