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

Questions 16–20

1. 16foundation · easy

   What is the primary purpose of enabling field audit trails in Salesforce?

   • ATo automatically correct data errors in fields
   • BTo track changes to field values, including who made the change and when
   • CTo improve field-level security
   • DTo prevent users from editing fields
   Reveal Solution Discussion Select an answer first
2. 17foundation · easy

   Which compliance requirement is directly supported by enabling field audit trails on customer metadata fields?

   • APreventing unauthorized access to customer data
   • BDemonstrating a history of changes to sensitive customer data
   • CGuaranteeing that customer data is accurate
   • DEnsuring that customer data is encrypted at rest
   Reveal Solution Discussion Select an answer first
4. 18foundation · easy

   When should a customer attribute be defined as a local attribute rather than a global one?

   • AWhen its format, meaning, or allowed values differ by region or country
   • BWhen it is not required for matching
   • CWhen it is used in only one business process
   • DWhen it is stored in a custom object
   Reveal Solution Discussion Select an answer first
5. 19foundation · easy

   In a multi-region Salesforce architecture, which type of customer attribute is best suited for a global definition?

   • ACustomer email address
   • BCustomer language preference
   • CCustomer phone number format
   • DCustomer address fields
   Reveal Solution Discussion Select an answer first
6. 20foundation · easy

   Which technique is most effective for keeping customer metadata current and consistent over time?

   • APerforming a one-time comprehensive metadata capture and then freezing the repository
   • BUsing the same metadata for all projects without reviewing for changes
   • CRelying on data stewards to manually update metadata whenever they notice changes
   • DScheduling periodic automated scans of source systems and comparing them with the current metadata repository
   Reveal Solution Discussion Select an answer first