DMF Practice Test

DMF Practice Test practice questions, page 3 of 12, with answer review and explanations.

Question 11

Which of the following activities is NOT a way that enterprise data architecture influences the scope boundaries of projects?

  1. Ensuring enterprise business processes are effectively documented
  2. Performing design reviews to ensure support of long-term organisational strategy
  3. Providing enterprise data requirement for projects
  4. Enforcing data architecture standards
  5. Ensuring sufficient data replication controls are in place

Question 12

Data flows can be represented by:

  1. Two dimensional matrices showing the relationships between data users and business processes
  2. Two dimensional matrices showing the relationships between data entities and business processes
  3. Two dimensional matrices showing the relationships between data facts and data dimensions
  4. Two dimensional matrices showing the relationships between data entities and data quality
  5. Two dimensional matrices showing the relationships between data users and data consumers

Question 13

The key architecture domains include:

  1. Business, strategy, application and technology architectures
  2. Zachmann, TOGAF, Cobit, and Heath architectures
  3. Business, data, infrastructure and technology architectures
  4. Business, data, application and technology architectures
  5. Process, database, software and technology architectures

Question 14

An enterprise data model would be composed of:

  1. Conceptual models, logical models and physical models
  2. Conceptual models, star schema models and interface models
  3. Conceptual models, subject area models and logical models
  4. Logical models, physical models and infrastructure models
  5. Enterprise models, data models and compositional models

Question 15

A relationship that allows an address to be used by multiple people, and each person can have multiple addresses, can be resolved:

  1. With an additional relationship describing the address usage
  2. By changing the primary keys on Person and Address to ensure referential integrity
  3. With an associative entity called Person Address Usage and two, 'one to many' relationships
  4. With a partnership entity called Person Address Usage and two, 'one to many' relationships
  5. By changing the role names of the foreign keys on Person and Address to ensure referential integrity