DATA-ARCHITECT practice question 19 of 35

Universal Containers (UC) is a major supplier of office supplies. Some products are produced by UC and some by other manufacturers. Recently, a…

Full set: 257 questions
Universal Containers (UC) is a major supplier of office supplies. Some products are produced by UC and some by other manufacturers. Recently, a number of customers have complained that product descriptions on the invoices do not match the descriptions in the online catalog and on some of the order confirmations (e.g., "ballpoint pen" in the catalog and "pen" on the invoice, and item color labels are inconsistent: "what vs. "White" or "blk" vs. "Black"). All product data is consolidated in the company data warehouse and pushed to Salesforce to generate quotes and invoices. The online catalog and webshop is a Salesforce Customer Community solution. What is a correct technique UC should use to solve the data inconsistency?
Answer options
A: Change integration to let product master systems update product data directly in Salesforce via the Salesforce API.
B: Add custom fields to the Product standard object in Salesforce to store data from the different source systems.
C: Define a data taxonomy for product data and apply the taxonomy to the product data in the data warehouse. Correct answer
D: Build Apex Triggers in Salesforce that ensure products have the correct names and labels after data is loaded into salesforce.
Correct Answer:
C. Define a data taxonomy for product data and apply the taxonomy to the product data in the data warehouse.
Explanation

The root cause of the problem is a lack of standardized data definitions across different systems before consolidation. A data taxonomy provides a formal classification system, defining standard values, formats, and hierarchies for data elements like product names and attributes (e.g., color). By defining and applying this taxonomy within the data warehouse—the central point of data consolidation—Universal Containers can enforce consistency. This ensures that all downstream systems, including Salesforce, receive clean, standardized data, resolving inconsistencies in catalogs, invoices, and confirmations. This is a proactive, architectural solution.

Why Incorrect

A. Changing the integration path does not solve the underlying problem of inconsistent source data; it just moves the problem.
B. Adding custom fields to store different versions of the data in Salesforce would institutionalize the inconsistency, not resolve it.
D. Using Apex Triggers is a reactive approach to clean data after it's already loaded. The best practice is to cleanse and standardize data upstream.

References

1. DAMA International, DAMA-DMBOK: Data Management Body of Knowledge (2nd Edition). Chapter 3, "Data Governance," discusses the importance of establishing common data definitions and standards (a taxonomy) to ensure data consistency and quality across an organization.

2. Kimball, R., & Ross, M. (2013). The Data Warehouse Toolkit: The Definitive Guide to Dimensional Modeling (3rd ed.). Chapter 5, "Conformed Dimensions," explains the necessity of creating standardized, shared dimensions (master data like 'Product') to ensure data can be integrated and analyzed consistently across different business processes. This is achieved by establishing a data taxonomy.

Scroll to Top