The EDM can be a stand-alone artifact, or it can be comprised of
the overall set of models created by the enterprise.
Different types of models â at different levels of abstraction â
must be related to each other.
Conceptual models are ultimately linkable to physical application
data models
The diagram shows:
⢠A conceptual overview over the enterpriseâs subject areas
⢠Views of entities and relationships for each subject area
⢠Detailed, partially attributed logical views of these same
subject areas
⢠Logical and physical models specific to an application or
project
An Enterprise Data Model (EDM) typically includes three core levels of abstraction:
Conceptual Data Model â High-level representation focused on business entities and their relationships. Itâs technology-agnostic and aimed at understanding the business.
Logical Data Model â Adds more detail, such as attributes, data types, and normalization, but still independent of any specific database technology.
Physical Data Model â Represents how the data is actually stored in the database, including tables, indexes, columns, data types, and relationships adapted to a specific DBMS (e.g., Oracle, SQL Server).
According to DAMAâDMBOK2 (see especially the discussion in Chapter 4 on Data Architecture and the sections on Enterprise Data Models around p.âŻ106), an Enterprise Data Model typically breaks the organizationâs data into topâlevel groups (subject areas), defines conceptualâlevel entities for each subject area, and often includes at least some logicalâlevel detail. A full physical design is usually not part of the highâlevel EDM.
Hence, among the options given, the correct match with DMBOK2 is:
C) Conceptual models, subject area models, and logical models.
An Enterprise Data Model (EDM) is a high-level representation of an organizationâs data, typically consisting of three levels of abstraction:
Conceptual Model â Defines high-level entities and relationships without technical details.
Logical Model â Provides detailed structure, including attributes, keys, and relationships, independent of technology.
Physical Model â Implements the logical model with database-specific structures, such as tables, indexes, and constraints.
B. Conceptual models, star schema models, and interface models â Incorrect, as star schema models are specific to data warehousing.
C. Conceptual models, subject area models, and logical models â Incorrect, as subject area models are a subset of conceptual models.
D. Logical models, physical models, and infrastructure models â Incorrect, as infrastructure models focus on hardware and network architecture.
E. Enterprise models, data models, and compositional models â Incorrect, as enterprise models and compositional models are not standard data model categories.
This section is not available anymore. Please use the main Exam Page.DMF Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Remee_2023
1Â day, 19Â hours agoShpaq
2Â weeks, 5Â days agoFMORADELL
1Â month, 3Â weeks agoIhueghian
4Â months, 2Â weeks agoHosna2023
4Â months, 2Â weeks agoHosna2023
4Â months, 3Â weeks agoaljegoram
5Â months, 3Â weeks agohavik
8Â months, 2Â weeks agoAyblaq
11Â months, 2Â weeks agoMrWood47
6Â months, 2Â weeks ago