The Data Management Fundamentals (DMF-1220)

A steward, in the context of data governance, is someone who manages assets on behalf of others. The DAMA-DMBOK states: “A steward is a person entrusted with the management of another’s property or assets, such as data, ensuring its proper use and quality” (DMBOK2, Chapter 3: Data Governance, p. 110).

Options A, B, D, and E do not align with this definition: sponsors fund, stakeholders have interests, trend-followers are unrelated, and employers hire.

A document management system relies on metadata to enable effective search and retrieval of documents. If the search function fails to return known artefacts, it indicates a failure in maintaining appropriate metadata, such as tags, descriptions, or indexing attributes. The DAMA-DMBOK states: “Metadata is critical for enabling findability, accessibility, and usability of data assets. In document management systems, metadata such as document titles, keywords, or categories must be consistently maintained to support search functionality” (DMBOK2, Chapter 11: Metadata Management, p. 441).

Other options are less relevant: data quality metrics (A) focus on data accuracy, not search functionality; business intelligence (B) relates to analytics, not document retrieval; public access (C) is unrelated to search failures; and privacy procedures (E) address security, not search performance.

Data lakes require data management, particularly metadata, to ensure usability. The DAMA-DMBOK states: “Data lakes need data management, including metadata to create an inventory of ingested data, enabling discovery, governance, and quality control” (DMBOK2, Chapter 4: Data Architecture, p. 161). Option C aligns with this. Options A, D, and E dismiss the need for management, and B is inaccurate about synchronization.

A database growing at 100% per annum compound doubles in size each year, following the formula for compound growth: Size = Initial Size × (1 + Growth Rate)^Years. For a 100% growth rate (1.0), after 2 years: Size = Initial Size × (1 + 1)^2 = Initial Size × 2^2 = 4 times the original size. The DAMA-DMBOK discusses capacity planning, noting that “data growth projections, including compound growth, are critical for planning storage and performance requirements” (DMBOK2, Chapter 10: Data Storage and Operations, p. 391).

Calculating for other options: After 3 years, the size is 2^3 = 8 times (not 6, so B is incorrect); after 5 years, it’s 2^5 = 32 times (not 2, so C is incorrect); after 2 years, it’s not 3 times (D) or half (E). Thus, A is correct.

Capturing synonyms in a data repository aids search and integration across diverse naming conventions. The DAMA-DMBOK states: “Synonyms in a data repository enable effective data searches by accommodating different naming conventions across the organization, improving findability and integration” (DMBOK2, Chapter 11: Metadata Management, p. 447). Option D is the most accurate.

In application migration projects, enterprise data architects focus on aligning data with business processes to ensure the new system supports organizational goals. The DAMA-DMBOK states: “Data architects are responsible for mapping data to business processes to ensure that data structures support business capabilities during system migrations” (DMBOK2, Chapter 4: Data Architecture, p. 141).

Options B, C, D, and E are secondary: B involves process owners, C and E are vague, and D is a tactical task, not the primary concern.

A DMZ (Demilitarized Zone) is a network segment that acts as a buffer between the public internet and an organization’s internal systems, protected by two firewalls. The DAMA-DMBOK explains: “A DMZ is typically configured with two firewalls: one between the DMZ and the external internet, and another between the DMZ and the internal network, to secure internal systems from external threats” (DMBOK2, Chapter 8: Data Security, p. 303).

Options A, B, C, and E are incorrect: A is nonsensical; B is vague; C includes the extranet, which is not standard; and E uses “intranet,” which is less precise than “internal systems.”

Ethical responsibility for data is shared across the organization, as all users must adhere to ethical principles. The DAMA-DMBOK states: “Ethical data management is a collective responsibility, where everyone who uses or handles data within the organization is accountable for ensuring its ethical use to prevent misrepresentation, misuse, or misunderstanding” (DMBOK2, Chapter 14: Data Handling Ethics, p. 561). Options A, C, D, and E assign responsibility too narrowly to specific roles or groups.

An effective data governance function must be embedded in organizational processes, systematic in its approach, and sustainable over time. The DAMA-DMBOK states: “Effective data governance is embedded within business processes, systematic in its application of policies and standards, and sustainable to support long-term organizational goals” (DMBOK2, Chapter 3: Data Governance, p. 107).

Other options include qualities like “measured” or “objective,” but DMBOK emphasizes embedded, systematic, and sustainable as the core triad.