Practice Free Plat-Arch-201 Exam Online Questions
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.
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.
A custom pricing engine for a Salesforce customer has to be decided by factors with the following hierarchy:
State in which the customer is located
City in which the customer is located if available
Zip code in which the customer is located if available
Changes to this information should have minimum code changes
What should a data architect recommend to maintain this information for the custom pricing engine that is to be built in Salesforce?
- A . Create a custom object to maintain the pricing criteria.
- B . Assign the pricing criteria within customer pricing engine.
- C . Maintain require pricing criteria in custom metadata types.
- D . Configure the pricing criteria in price books.
C
Explanation:
According to the Get Started with Custom Metadata Types unit on Trailhead, one of the use cases for custom metadata types is to define custom charges for an accounting app. The unit states that “Say that your org uses a standard accounting app. You can create a custom metadata type that defines custom charges, like duties and VAT rates. Then you can write some Apex code that calculates the total amount due for each invoice by using the metadata from your custom metadata type.” Therefore, a similar approach can be used to maintain the pricing criteria for a custom pricing engine in Salesforce.
A custom pricing engine for a Salesforce customer has to be decided by factors with the following hierarchy:
State in which the customer is located
City in which the customer is located if available
Zip code in which the customer is located if available
Changes to this information should have minimum code changes
What should a data architect recommend to maintain this information for the custom pricing engine that is to be built in Salesforce?
- A . Create a custom object to maintain the pricing criteria.
- B . Assign the pricing criteria within customer pricing engine.
- C . Maintain require pricing criteria in custom metadata types.
- D . Configure the pricing criteria in price books.
C
Explanation:
According to the Get Started with Custom Metadata Types unit on Trailhead, one of the use cases for custom metadata types is to define custom charges for an accounting app. The unit states that “Say that your org uses a standard accounting app. You can create a custom metadata type that defines custom charges, like duties and VAT rates. Then you can write some Apex code that calculates the total amount due for each invoice by using the metadata from your custom metadata type.” Therefore, a similar approach can be used to maintain the pricing criteria for a custom pricing engine in Salesforce.
A custom pricing engine for a Salesforce customer has to be decided by factors with the following hierarchy:
State in which the customer is located
City in which the customer is located if available
Zip code in which the customer is located if available
Changes to this information should have minimum code changes
What should a data architect recommend to maintain this information for the custom pricing engine that is to be built in Salesforce?
- A . Create a custom object to maintain the pricing criteria.
- B . Assign the pricing criteria within customer pricing engine.
- C . Maintain require pricing criteria in custom metadata types.
- D . Configure the pricing criteria in price books.
C
Explanation:
According to the Get Started with Custom Metadata Types unit on Trailhead, one of the use cases for custom metadata types is to define custom charges for an accounting app. The unit states that “Say that your org uses a standard accounting app. You can create a custom metadata type that defines custom charges, like duties and VAT rates. Then you can write some Apex code that calculates the total amount due for each invoice by using the metadata from your custom metadata type.” Therefore, a similar approach can be used to maintain the pricing criteria for a custom pricing engine in Salesforce.
A custom pricing engine for a Salesforce customer has to be decided by factors with the following hierarchy:
State in which the customer is located
City in which the customer is located if available
Zip code in which the customer is located if available
Changes to this information should have minimum code changes
What should a data architect recommend to maintain this information for the custom pricing engine that is to be built in Salesforce?
- A . Create a custom object to maintain the pricing criteria.
- B . Assign the pricing criteria within customer pricing engine.
- C . Maintain require pricing criteria in custom metadata types.
- D . Configure the pricing criteria in price books.
C
Explanation:
According to the Get Started with Custom Metadata Types unit on Trailhead, one of the use cases for custom metadata types is to define custom charges for an accounting app. The unit states that “Say that your org uses a standard accounting app. You can create a custom metadata type that defines custom charges, like duties and VAT rates. Then you can write some Apex code that calculates the total amount due for each invoice by using the metadata from your custom metadata type.” Therefore, a similar approach can be used to maintain the pricing criteria for a custom pricing engine in Salesforce.
Universal Containers (UC) has a data model as shown in the image. The Project object has a private sharing model, and it has Roll -Up summary fields to calculate the number of resources assigned to the project, total hours for the project, and the number of work items associated to the project.
What should the architect consider, knowing there will be a large amount of time entry records to be loaded regularly from an external system into Salesforce.com?
- A . Load all data using external IDs to link to parent records.
- B . Use workflow to calculate summary values instead of Roll -Up.
- C . Use triggers to calculate summary values instead of Roll -Up.
- D . Load all data after deferring sharing calculations.
D
Explanation:
Loading all data after deferring sharing calculations can improve the performance and avoid locking issues when loading a large amount of time entry records into Salesforce.com. This is because deferring sharing calculations can temporarily suspend the calculation of sharing rules until all the data is loaded, and then recalculate them in one operation
As part of a phased Salesforce rollout. there will be 3 deployments spread out over the year. The requirements have been carefully documented.
Which two methods should an architect use to trace back configuration changes to the detailed requirements? Choose 2 answers
- A . Review the setup audit trail for configuration changes.
- B . Put the business purpose in the Description of each field.
- C . Maintain a data dictionary with the justification for each field.
- D . Use the Force.com IDE to save the metadata files in source control.
B, D
Explanation:
Option B is correct because putting the business purpose in the Description of each field is a method that an architect can use to trace back configuration changes to the detailed requirements1. The Description of each field provides a brief explanation of what the field is used for and why it is needed2.
Option D is correct because using the Force.com IDE to save the metadata files in source control is another method that an architect can use to trace back configuration changes to the detailed requirements1. The Force.com IDE is an integrated development environment that allows developers to work with Salesforce metadata files and Apex code3. Source control is a system that tracks and manages changes to code and configuration files4.
Option A is not correct because reviewing the setup audit trail for configuration changes is not a method to trace back configuration changes to the detailed requirements, but a way to monitor and audit the changes made in the setup area.
Option C is not correct because maintaining a data dictionary with the justification for each field is not a method to trace back configuration changes to the detailed requirements, but a document that provides information about the data entities and attributes in a system.
Universal Containers (UC) provides shipping services to its customers. They use Opportunities to track customer shipments. At any given time, shipping status can be one of the 10 values. UC has 200,000 Opportunity records.
When creating a new field to track shipping status on opportunity, what should the architect do to improve data quality and avoid data skew?
- A . Create a picklist field, values sorted alphabetically.
- B . Create a Master -Detail to custom object ShippingStatus c.
- C . Create a Lookup to custom object ShippingStatus c.
- D . Create a text field and make it an external ID.
A
Explanation:
To improve data quality and avoid data skew, the data architect should create a picklist field with values sorted alphabetically for tracking shipping status on opportunity. A picklist field ensures that only valid values are entered and prevents typos or variations in spelling. Sorting the values alphabetically makes it easier for users to find and select the correct value. Data skew occurs when a large number of records are owned by a single user or have a single value for a field. Creating a picklist field with a limited number of values does not cause data skew, as long as the distribution of values is balanced and not skewed towards one value.
Cloud Kicks needs to purge detailed transactional records from Salesforce. The data should be aggregated at a summary level and available in Salesforce.
What are two automated approaches to fulfill this goal? (Choose two.)
- A . Third-party Integration Tool (ETL)
- B . Schedulable Batch Apex
- C . Third-party Business Intelligence system
- D . Apex Triggers
A, B
Explanation:
Both A and B are automated approaches to purge detailed transactional records from Salesforce and aggregate them at a summary level1. You can use a third-party integration tool (ETL) or schedulable batch Apex to perform these tasks.
Option C is not correct because a third-party business intelligence system does not purge data from Salesforce, but only analyzes it.
Option D is not correct because Apex triggers are not automated, but execute when a record is inserted, updated, deleted, or undeleted.
Cloud Kicks needs to purge detailed transactional records from Salesforce. The data should be aggregated at a summary level and available in Salesforce.
What are two automated approaches to fulfill this goal? (Choose two.)
- A . Third-party Integration Tool (ETL)
- B . Schedulable Batch Apex
- C . Third-party Business Intelligence system
- D . Apex Triggers
A, B
Explanation:
Both A and B are automated approaches to purge detailed transactional records from Salesforce and aggregate them at a summary level1. You can use a third-party integration tool (ETL) or schedulable batch Apex to perform these tasks.
Option C is not correct because a third-party business intelligence system does not purge data from Salesforce, but only analyzes it.
Option D is not correct because Apex triggers are not automated, but execute when a record is inserted, updated, deleted, or undeleted.