Free Data-Architect Exam Braindumps (page: 4)

Page 3 of 65

Universal Containers (UC) management has identified a total of ten text fields on the Contact object as important to capture any changes made to these fields, such as who made the change, when they made the change, what is the old value, and what is the new value. UC needs to be able to report on these field data changes within Salesforce for the past 3 months.
What are two approaches that will meet this requirement? Choose 2 answers

  1. Create a workflow to evaluate the rule when a record is created and use field update actions to store previous values for these ten fields in ten new fields.
  2. Write an Apex trigger on Contact after insert event and after update events and store the old values in another custom object.
  3. Turn on field Contact object history tracking for these ten fields, then create reports on contact history.
  4. Create a Contact report including these ten fields and Salesforce Id, then schedule the report to run once a day and send email to the admin.

Answer(s): B,C



Universal Containers (UC) has an open sharing model for its Salesforce users to allow all its Salesforce internal users to edit all contacts, regardless of who owns the contact. However, UC management wants to allow only the owner of a contact record to delete that contact. If a user does not own the contact, then the user should not be allowed to delete the record. How should the architect approach the project so that the requirements are met?

  1. Create a "before delete" trigger to check if the current user is not the owner.
  2. Set the Sharing settings as Public Read Only for the Contact object.
  3. Set the profile of the users to remove delete permission from the Contact object.
  4. Create a validation rule on the Contact object to check if the current user is not the owner.

Answer(s): A



Universal Containers (UC) uses Salesforce for tracking opportunities (Opportunity). UC uses an internal ERP system for tracking deliveries and invoicing. The ERP system supports SOAP API and OData for bi-directional integration between Salesforce and the ERP system. UC has about one million opportunities. For each opportunity, UC sends 12 invoices, one per month. UC sales reps have requirements to view current invoice status and invoice amount from the opportunity page.
When creating an object to model invoices, what should the architect recommend, considering performance and data storage space?

  1. Use Streaming API to get the current status from the ERP and display on the Opportunity page.
  2. Create an external object Invoice _x with a Lookup relationship with Opportunity.
  3. Create a custom object Invoice _c with a master -detail relationship with Opportunity.
  4. Create a custom object Invoice _c with a Lookup relationship with Opportunity.

Answer(s): B



Universal Containers has a large number of Opportunity fields (100) that they want to track field history on.
Which two actions should an architect perform in order to meet this requirement? Choose 2 answers

  1. Create a custom object to store a copy of the record when changed.
  2. Create a custom object to store the previous and new field values.
  3. Use Analytic Snapshots to store a copy of the record when changed.
  4. Select the 100 fields in the Opportunity Set History Tracking page.

Answer(s): A,B






Post your Comments and Discuss Salesforce Data-Architect exam with other Community members:

Data-Architect Discussions & Posts