Given a Customer Scenario, Recommend Appropriate Approaches and Techniques to Capture and Maintain Customer Metadata to Preserve Traceability and Establish a Common Context for Business Rules (e.g., Applying Weights to Attributes Used in Matching Process by Their Importance, Data Classification, Global/local Attributes, Field Audit Trails, Etc.). DATA-ARCHITECT Practice Questions (Page 5)

Questions 21–24

1. 21foundation · easy

   Which metadata capture method is best suited for capturing business-level metadata such as data definitions, ownership, and usage rules?

   • AAutomated schema extraction from the database catalog
   • BCollaborative data dictionary tools that allow business users to document definitions and rules
   • CReviewing ETL job logs to understand data flows
   • DProfiling data values to infer patterns and relationships
   Reveal Solution Discussion Select an answer first
2. 22application · medium

   A data architect is designing a Customer 360 solution that ingests data from a legacy CRM, a marketing automation platform, and a customer support system. The business needs to understand the origin of each field in the unified profile and how it was transformed. Which metadata capture approach best supports this requirement?

   • AUse Data Cloud's data mapping and transformation features to document the source object, source field, and transformation logic for each target field in the unified profile.
   • BCreate a custom object called 'Data Lineage' and manually populate it with records describing each source-to-target mapping.
   • CStore the source system name in a custom field on every record in the unified profile.
   • DExport the Data Cloud mapping configuration to a PDF and store it in a shared drive for reference.
   Reveal Solution Discussion Select an answer first
4. 23application · medium

   A data architect is building a unified customer profile in Data Cloud. The business has a requirement that the definition of 'High Value Customer' must be consistent across all regions. Currently, each region has its own definition. What is the best way to establish a common context for this business rule?

   • AUse the definition from the region with the highest revenue as the standard.
   • BCreate a picklist field on the customer record called 'High Value Customer' and let each region set it based on their local rules.
   • CCreate a custom metadata type called 'Business Rule Definition' that stores the standardized definition of 'High Value Customer' and reference it from the unified data model.
   • DLet each region keep its own definition and document the differences in a shared document.
   Reveal Solution Discussion Select an answer first
5. 24foundation · easy

   Which practice best preserves traceability of customer metadata from source to consumption?

   • AOverwriting historical metadata with current values to keep the repository clean
   • BUsing generic field names that do not indicate their source or purpose
   • CStoring metadata in a separate repository without any reference to source systems
   • DRecording lineage information that maps each metadata element to its source system, transformations, and business rules
   Reveal Solution Discussion Select an answer first