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 2)

Questions 6–10

1. 6foundation · easy

   In a customer matching process, why would you assign a higher weight to the email address attribute than to the first name attribute?

   • AFirst name is less important for matching because it is not used in any business rules
   • BFirst name is more likely to contain errors than email address
   • CEmail address is generally a more unique and reliable identifier than first name
   • DEmail address is always required in all customer records
   Reveal Solution Discussion Select an answer first
2. 7application · medium

   A company has multiple Salesforce orgs that each define a 'Customer Status' field with different picklist values. The data architect is building a unified data model in Data Cloud. The business wants a single, standardized definition of 'Customer Status' that can be used consistently across all orgs. What is the best way to establish this common context?

   • ACreate a global picklist in Data Cloud that maps each org's local values to a standardized set of values, and document the mapping in a custom metadata type.
   • BUse the 'Customer Status' field from the org with the most records as the standard and ignore the others.
   • CStore the local values as-is in the unified profile and let each downstream report interpret them.
   • DCreate a new field in each org called 'Global Customer Status' and ask each admin to manually keep it in sync.
   Reveal Solution Discussion Select an answer first
4. 8application · medium

   A company has a Salesforce org with a custom metadata type that defines the weighting for a matching rule. Over time, the business has changed its priorities, and the weights have been updated multiple times. The data architect is concerned that the current weights may not reflect the latest business decisions. What is the most effective way to maintain the accuracy of this metadata?

   • ASet up an automated scheduled job that compares the current weights to a 'golden source' spreadsheet and alerts the admin if they differ.
   • BGrant all data stewards edit access to the custom metadata type so they can update the weights whenever they see fit.
   • CEstablish a quarterly review process where the business stakeholders formally approve any changes to the weight values, and record the approval in the change log of the custom metadata type.
   • DCreate a new custom metadata type each time the weights change and update the matching rule to reference the new type.
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   Why is it important to link customer metadata to the business rules that govern its use?

   • AIt allows metadata to be stored in a single field in the database
   • BIt ensures that metadata is automatically updated when business rules change
   • CIt reduces the need for data validation during integration
   • DIt allows stakeholders to understand how metadata is interpreted and applied in business processes
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   A healthcare organization is building a data warehouse on Salesforce Data Cloud. They ingest patient records, insurance claims, and provider information. The compliance team requires that any field containing personally identifiable information (PII) or protected health information (PHI) be flagged in the metadata so that downstream reports and integrations can apply appropriate security controls. The data architect must implement a classification scheme that is enforceable and discoverable. What should the architect do?

   • AMaintain a spreadsheet in Google Sheets that lists all sensitive fields and share it with the integration team.
   • BUse the field description on each sensitive field to prepend '[PII]' or '[PHI]' and instruct developers to read the description before using the field.
   • CAdd a custom field to every object called 'Is Sensitive' and set it to true for all PII and PHI fields.
   • DCreate a custom metadata type called 'Field Classification' with records for each sensitive field, storing the classification (e.g., PII, PHI, Public) and a reference to the source object and field API name.
   Reveal Solution Discussion Select an answer first