Rapid Recall Key 01–40

Do not use until you have attempted the prompt.

1. Metadata Management: planning, implementation, and control enabling processing, maintenance, integration, security, audit, and governance of other data.
2. It includes meaning, rules, ownership, systems, processes, quality, security, lineage, runtime status, and relationships—not only structural descriptions.
3. Information can exist but remain hard to find/use without a catalog; Metadata makes organizational data knowledge discoverable and understandable.
4. Manage business terminology; integrate diverse Metadata; assure quality/consistency/currency/security; provide standard access; enforce technical exchange standards.
5. Organizational Commitment; Strategy; Enterprise Perspective; Socialization; Access; Quality; Audit; Improvement.
6. Senior-management support/funding and recognition of Metadata as part of managing data as an enterprise asset.
7. Define how Metadata will be created, maintained, integrated, and accessed; align it to business priorities before evaluating products.
8. Design for enterprise extensibility while implementing iteratively/incrementally; enterprise perspective does not require big bang.
9. Explain Metadata value and encourage business participation/contribution of expertise.
10. Ensure consumers know how to find, access, and use Metadata.
11. Process owners are accountable for quality of Metadata produced through modeling, SDLC, integration, process definition, and similar work.
12. Audit: set/enforce/audit standards. Improvement: feedback mechanisms to identify/correct bad or stale Metadata.
13. Metadata has values, owners, quality, lifecycle, security, and use requirements and therefore should itself be managed as data.
14. Classification depends on context/abstraction: information describing one asset can be ordinary business data in another process.
15. Business Metadata = meaning, business rules, ownership, governance, standards, quality/security/privacy, and usage context.
16. Examples: definitions, business rules, calculations, DQ rules/results, SOR designation, valid values, Owner/Steward, security classification, known issues, usage notes.
17. Technical Metadata = physical/technical structures, systems, mappings, and processes that store/move data.
18. Examples: table/column names, datatypes, keys/indexes, schemas, source-target mappings, ETL details, application/program info, dependencies, technical lineage, access rights.
19. Operational Metadata = runtime processing and access evidence about data.
20. Examples: job logs, extract results, errors, schedule anomalies, query/report access/duration, SLA status, backup/DR status, volumes, retention/purge operations.
21. Business = meaning/governance; Technical = implementation/structure/movement.
22. Technical = design/implementation; Operational = actual execution/access state/evidence.
23. Descriptive identifies/retrieves resources; Structural describes parts/relationships; Administrative supports lifecycle management.
24. ISO/IEC 11179 provides a Metadata Registry framework for standardized data-element definitions/registration and Metadata-driven exchange.
25. Parts 1, 3, 4, 5, and 6 as listed in Chapter 12.
26. Less-structured content needs Metadata for discovery, classification, provenance, security, retention, and use.
27. Minimum examples: name, format, source, version, date received, plus organization-required attributes.
28. Application repositories; Business Glossary; BI tools; CMDB/configuration; Data Dictionaries; Integration tools; DBMS/system catalogs; Mapping tools; DQ tools; Directories/Catalogs; Event Messaging; Modeling tools/repositories; Reference Data repositories; Service Registries; Other Metadata stores.
29. Business concepts, terminology, definitions, relationships, ownership/status/workflow.
30. Data-set/data-element names, descriptions, characteristics, defaults, storage, relationships, uniqueness, and related detail.
31. Glossary = business concept/term meaning; Dictionary = detailed data-set/element structure/characteristics.
32. Dictionary = element/detail; Directory/Catalog = discover where systems/data/sources are located.
33. IT assets/configuration items, relationships, versions, implementation/change context.
34. Reports, calculations, filters, report fields/layouts, users, distribution information.
35. Mappings, transformations, transient-file details, lineage, job status/duration/last successful run.
36. Tables, columns, indexes, constraints, views, procedures, sizing, versions, deployment, availability information.
37. Validation rules, profiles, quality scores, observed patterns.
38. Conceptual/logical/physical model Metadata, entities, attributes, relationships, tables, keys, constraints.
39. Domains, coded values, descriptions, contextual use, mappings, relationships.
40. Service definitions, endpoints, interfaces, operations, parameters, policies, versions, availability, connection information.

← Prompts 01–40 · Key 41–80 →