Salesforce Salesforce Certifications DATA-ARCHITECT Questions & Answers

• Question 171:

  What makes Skinny tables fast? Choose three answers.

  A. They do not include soft-deleted records

  B. They avoid resource intensive joins

  C. Their tables are kept in sync with their source tables when the source tables are modified

  D. They can contain fields from other objects

  E. They support up to a max of 100 of columns

  Correct Answer: ABC

  Explanation: Skinny tables are custom tables that contain frequently used fields from a standard or custom object. They are used to improve performance by reducing the number of database joins required for queries. Skinny tables have the

  following characteristics1:

  They do not include soft-deleted records, which means they only contain active records and save space.

  They avoid resource intensive joins by storing data from multiple objects in one table, which reduces the query time and complexity. Their tables are kept in sync with their source tables when the source tables are modified, which ensures

  data consistency and accuracy.

• Question 172:

  Universal Containers (UC) has a requirement to create an Account plan object that is related to the Account object. Each Account plan needs to have an Account object, but the accessibility requirement of the Account plan is different from the Account object. What should an Architect recommend?

  A. Create a custom account plan object as detail with Account as mater in a master-detail relationship.

  B. Create a custom account plan object as detail with Account as master with additional sharing rules to allow access.

  C. Create an account plan object with a lookup relations to Account without any validation rules to enforce the Account association.

  D. Create an account plan object with a lookup relationship to Account with validation rules to enforce the Account association.

  Correct Answer: D

  Explanation: Creating an account plan object with a lookup relationship to Account with validation rules to enforce the Account association can help UC meet their requirement. A lookup relationship allows different accessibility requirements for the account plan object and the account object, as well as different ownership and sharing settings. A validation rule can ensure that each account plan has an account associated with it.

• Question 173:

  DreamHouse Realty has an integration that creates records in a Salesforce Custom Object. The Custom Object has a field marked as required on the page layout. DreamHouse Realty has noticed that many of the records coming from the external system are missing data in this field.

  The Architect needs to ensure this field always contains data coming from the source system.

  Which two approaches should the Architect take? Choose 2 answers

  A. Set up a Validation Rule to prevent blank values.

  B. Create a Workflow to default a value into this field.

  C. Mark the field required in setup at the field level.

  D. Blame the customer's external system for bad data.

  Correct Answer: AC

  Explanation: Setting up a Validation Rule to prevent blank values and marking the field required in setup at the field level are two approaches that the Architect should take to ensure that the field always contains data coming from the source system. A Validation Rule can display an error message when a record is created or edited with a blank value for the field, and prevent it from being saved. Marking the field required in setup at the field level can enforce the requirement for all records, regardless of the page layout or the source system. The other options are not effective or recommended for ensuring data quality, as they would either not prevent blank values, not apply to all records, or not address the root cause of the problem

• Question 174:

  Universal Containers (UC) needs to run monthly and yearly reports on opportunities and orders for sales reporting. There are 5 million opportunities and 10 million orders. Sales users are complaining that the report will regularly timeout.

  What is the fastest and most effective way for a data architect to solve the time-out issue?

  A. Create custom fields on opportunity, and copy data from order into those custom fields and run all reports on Opportunity object.

  B. Extract opportunity and order data from Salesforce, and use a third-party reporting tool to run reports outside of Salesforce.

  C. Create a skinny table in Salesforce, and copy order and opportunity fields into the skinny table and create the required reports on It.

  D. Create an aggregate custom object that summarizes the monthly and yearly values into the required format for the required reports.

  Correct Answer: D

  Explanation: Creating an aggregate custom object that summarizes the monthly and yearly values into the required format for the required reports (option D) is the fastest and most effective way for a data architect to solve the time-out issue, as it reduces the amount of data that needs to be queried and processed by the reports. Creating custom fields on opportunity and copying data from order into those custom fields (option A) is not a good solution, as it may create data redundancy and inconsistency, and it does not address the large volume of data. Extracting opportunity and order data from Salesforce and using a third-party reporting tool (option B) is also not a good solution, as it may introduce additional complexity and cost, and it does not leverage the native reporting features of Salesforce. Creating a skinny table in Salesforce and copying order and opportunity fields into it (option C) is also not a good solution, as it may not support all the reporting requirements, and it does not reduce the number of records.

• Question 175:

  Ursa Major Solar has defined a new Data Quality Plan for their Salesforce data.

  Which two approaches should an Architect recommend to enforce the plan throughout the organization? (Choose two.)

  A. Ensure all data is stored in an external system and set up an integration to Salesforce for view-only access.

  B. Schedule reports that will automatically catch duplicates and merge or delete the records every week.

  C. Enforce critical business processes by using Workflow, Validation Rules, and Apex code.

  D. Schedule a weekly dashboard displaying records that are missing information to be sent to managers for review.

  Correct Answer: CD

  Explanation: Enforcing critical business processes by using Workflow, Validation Rules, and Apex code can help ensure data quality and consistency by applying rules and logic to the data entry and update3. Scheduling a weekly dashboard displaying records that are missing information to be sent to managers for review can help identify and fix data quality issues by providing visibility and accountability4.

• Question 176:

  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?

  A. Use Streaming API to get the current status from the ERP and display on the Opportunity page.

  B. Create an external object Invoice _x with a Lookup relationship with Opportunity.

  C. Create a custom object Invoice _c with a master -detail relationship with Opportunity.

  D. Create a custom object Invoice _c with a Lookup relationship with Opportunity.

  Correct Answer: B

  Explanation: Creating an external object Invoice_x with a Lookup relationship with Opportunity is the best option for modeling invoices, considering performance and data storage space. An external object allows the data to be stored in the ERP system and accessed via OData in Salesforce. This reduces the data storage consumption in Salesforce and improves the performance of queries and reports. A Lookup relationship allows the sales reps to view the invoice status and amount from the opportunity page. The other options would either consume more data storage space, require additional customization, or not provide real-time data access

• Question 177:

  Universal Containers has been a customer of Salesforce for 10 years. Currently they have 2 million accounts in the system. Due to an erroneous integration built 3 years ago, it is estimated there are 500,000 duplicates in the system.

  Which solution should a data architect recommend to remediate the duplication issue?

  A. Develop an ETL process that utilizers the merge API to merge the duplicate records

  B. Utilize a data warehouse as the system of truth

  C. Extract the data using data loader and use excel to merge the duplicate records

  D. Implement duplicate rules

  Correct Answer: D

  Explanation: Implementing duplicate rules (option D) is the best solution to remediate the duplication issue, as it allows the data architect to identify and merge duplicate accounts in Salesforce using native features and tools. Developing an ETL process that utilizes the merge API to merge the duplicate records (option A) is not a good solution, as it may require more coding and testing effort, and it does not prevent duplicates from being created in Salesforce. Utilizing a data warehouse as the system of truth (option B) is also not a good solution, as it may introduce additional complexity and cost, and it does not address the duplication issue in Salesforce. Extracting the data using data loader and using excel to merge the duplicate records (option C) is also not a good solution, as it may be time-consuming and error-prone, and it does not prevent duplicates from being created in Salesforce.

• Question 178:

  Northern Trail outfitters in migrating to salesforce from a legacy CRM system that identifies the agent relationships in a look-up table.

  What should the data architect do in order to migrate the data to Salesfoce?

  A. Create custom objects to store agent relationships.

  B. Migrate to Salesforce without a record owner.

  C. Assign record owner based on relationship.

  D. Migrate the data and assign to a non-person system user.

  Correct Answer: A

  Explanation: The correct answer is A. To migrate the data to Salesforce, the data architect should create custom objects to store agent relationships. This will allow the data architect to replicate the look-up table structure from the legacy CRM system and maintain the relationship data in Salesforce. Option B is incorrect because migrating to Salesforce without a record owner will cause errors and prevent the data from being imported. Option C is incorrect because assigning record owner based on relationship will not preserve the agent relationships from the legacy CRM system. Option D is incorrect because migrating the data and assigning to a non-person system user will not allow the users to access and modify the data.

• Question 179:

  The head of sales at Get Cloudy Consulting wants to understand key relevant performance figures and help managers take corrective actions where appropriate.

  What is one reporting option Get Cloudy Consulting should consider?

  A. Case SLA performance report

  B. Sales KPI Dashboard

  C. Opportunity analytic snapshot

  D. Lead conversion rate report

  Correct Answer: B

  Explanation: A Sales KPI Dashboard is one reporting option that Get Cloudy Consulting should consider to understand key relevant performance figures and help managers take corrective actions where appropriate. A Sales KPI Dashboard can display various metrics that indicate the health and effectiveness of the sales team, such as quota attainment, pipeline value, win rate, average deal size, sales cycle length, and more. A Sales KPI Dashboard can also help identify trends, patterns, and areas for improvement.

• Question 180:

  A large multinational B2C Salesforce customer is looking to implement their distributor management application is Salesforce. the application has the following capabilities:

  1.Distributor create sales order in salesforce

  2.Sales order are based on product prices applicable to their region

  3.

  Sales order are closed once they are fulfilled

  4.

  It is decided to maintain the order in opportunity object

  How should the data architect model this requirement?

  A. Create lookup to Custom Price object and share with distributors.

  B. Configure price Books for each region and share with distributors.

  C. Manually update Opportunities with Prices application to distributors.

  D. Add custom fields in Opportunity and use triggers to update prices.

  Correct Answer: B

  Explanation: According to the Salesforce documentation, an opportunity is a standard object that represents a potential sale or deal with an account or contact. An opportunity can have products and prices associated with it using price books.

  A price book is a standard object that contains a list of products and their prices for different regions, currencies, segments, etc. A price book can be shared with different users or groups based on their visibility and access settings.

  To model the requirement of implementing a distributor management application in Salesforce, where distributors create sales orders based on product prices applicable to their region, and sales orders are closed once they are fulfilled, a

  data architect should:

  Configure price books for each region and share with distributors (option B). This means creating different price books for different regions with the appropriate products and prices, and sharing them with the distributors who belong to those

  regions. This way, distributors can create sales orders (opportunities) using the price books that are relevant to their region.

  Creating a lookup to Custom Price object and sharing with distributors (option A) is not a good solution, as it can introduce unnecessary complexity and redundancy to the data model. It is better to use standard objects and features that are

  designed for managing products and prices in Salesforce. Manually updating opportunities with prices applicable to distributors (option C) is also not a good solution, as it can be time-consuming, error-prone, and inefficient. It is better to use

  automation tools or features that can update prices based on predefined criteria or logic. Adding custom fields in opportunity and using triggers to update prices (option D) is also not a good solution, as it can be complex, costly, and difficult to

  maintain. It is better to use standard fields and features that can handle prices more effectively.