Practice Free Plat-Arch-201 Exam Online Questions
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.
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
As part of addressing general data protection regulation (GDPR) requirements, UC plans to implement a data classification policy for all its internal systems that stores customer information including salesforce.
What should a data architect recommend so that UC can easily classify consumer information maintained in salesforce under both standard and custom objects?
- A . Use App Exchange products to classify fields based on policy.
- B . Use data classification metadata fields available in field definition.
- C . Create a custom picklist field to capture classification of information on customer.
- D . Build reports for customer information and validate.
B
Explanation:
The correct answer is B, use data classification metadata fields available in field definition. Data classification metadata fields are standard fields that allow you to classify the sensitivity level of your data based on your organization’s policies. You can use these fields to indicate whether a field contains confidential, restricted, or general data. These fields are available for both standard and custom objects in Salesforce. Using app exchange products, creating a custom picklist field, or building reports would not be as effective or consistent as using data classification metadata fields.
Ursa Major Solar’s legacy system has a quarterly accounts receivable report that compiles data from the following:
– Accounts
– Contacts
– Opportunities
– Orders
– Order Line Items
Which issue will an architect have when implemented this in Salesforce?
- A . Custom report types CANNOT contain Opportunity data.
- B . Salesforce does NOT support Orders or Order Line Items.
- C . Salesforce does NOT allow more than four objects in a single report type.
- D . A report CANNOT contain data from Accounts and Contacts.
C
Explanation:
The issue that an architect will have when implementing the quarterly accounts receivable report in Salesforce is that Salesforce does not allow more than four objects in a single report type. A report type defines the set of records and fields available to a report based on the relationships between a primary object and up to four related objects.
A report type has the following limitations:
It cannot include more than four objects in a single report type, which means that the report cannot compile data from five objects (Accounts, Contacts, Opportunities, Orders, and Order Line Items) at once.
It cannot include objects that are more than two relationships away from each other, which means that the report cannot access fields from Order Line Items through Opportunities and Orders.
It cannot include objects that have a many-to-many relationship with each other, which means that the report cannot access fields from Contacts and Opportunities through the junction object Opportunity Contact Role.
Universal Containers (UC) has implemented Salesforce, UC is running out of storage and needs to have an archiving solution, UC would like to maintain two years of data in Saleforce and archive older data out of Salesforce.
Which solution should a data architect recommend as an archiving solution?
- A . Use a third-party backup solution to backup all data off platform.
- B . Build a batch join move all records off platform, and delete all records from Salesforce.
- C . Build a batch join to move two-year-old records off platform, and delete records from Salesforce.
- D . Build a batch job to move all restore off platform, and delete old records from Salesforce.
C
Explanation:
The data architect should recommend building a batch job to move two-year-old records off platform, and delete records from Salesforce as an archiving solution. A batch job is a process that runs in the background and performs operations on large volumes of data in Salesforce. By building a batch job that moves two-year-old records off platform to an external storage system, such as Amazon S3 or Google Cloud Storage, and deletes them from Salesforce, the data architect can reduce the storage consumption and improve the performance of Salesforce org.
Option A is incorrect because using a third-party backup solution to backup all data off platform will not free up any storage space in Salesforce, unless the data is also deleted from Salesforce after backup.
Option B is incorrect because building a batch job to move all records off platform, and delete all records from Salesforce will result in losing all the current data in Salesforce, which may not be desirable or feasible.
Option D is incorrect because building a batch job to move all restore off platform, and delete old records from Salesforce does not make sense, as restore implies restoring data back to Salesforce, not moving it off platform.
Universal Containers (UC) is concerned about the accuracy of their Customer information in Salesforce. They have recently created an enterprise-wide trusted source MDM for Customer data which they have certified to be accurate. UC has over 20 million unique customer records in the trusted source and Salesforce.
What should an Architect recommend to ensure the data in Salesforce is identical to the MDM?
- A . Extract the Salesforce data into Excel and manually compare this against the trusted source.
- B . Load the Trusted Source data into Salesforce and run an Apex Batch job to find difference.
- C . Use an AppExchange package for Data Quality to match Salesforce data against the Trusted source.
- D . Leave the data in Salesforce alone and assume that it will auto-correct itself over time.
C
Explanation:
Using an AppExchange package for Data Quality is a good way to match Salesforce data against a trusted source, such as an MDM system. You can use tools like Cloudingo, Dupe Catcher, or Demand Tools to identify and merge duplicate records, standardize data formats, and enrich data with external sources
Northern Trail Outfitters (NTO) has the following systems:
Customer master-source of truth for customer information
Service cloud-customer support
Marketing cloud-marketing support
Enterprise data warehouse―business reporting
The customer data is duplicated across all these systems and are not kept in sync. Customers are also complaining that they get repeated marketing emails and have to call into update their information.
NTO is planning to implement master data management (MDM) solution across the enterprise.
Which three data will an MDM tool solve? Choose 3 answers
- A . Data completeness
- B . Data loss and recovery
- C . Data duplication
- D . Data accuracy and quality
- E . Data standardization
C, D, E
Explanation:
According to the.
What is Master Data Management (MDM)? article, some of the data challenges that an MDM tool can solve are data duplication, data accuracy and quality, and data standardization. The article states that “MDM solutions comprise a broad range of data cleansing, transformation, and integration practices. As data sources are added to the system, MDM initiates processes to identify, collect, transform, and repair data. Once the data meets the quality thresholds, schemas and taxonomies are created to help maintain a high-quality master reference.” Therefore, an MDM tool can help NTO eliminate data duplication across different systems, improve data accuracy and quality by removing errors and inconsistencies, and standardize data formats and definitions for better integration and analysis.
Universal Containers has a requirement to store more than 100 million records in salesforce and needs to create a custom big object to support this business requirement.
Which two tools should a data architect use to build custom object?
- A . Use DX to create big object.
- B . Use Metadata API to create big object.
- C . Go to Big Object in setup select new to create big object.
- D . Go to Object Manager in setup and select new to create big object.
B, C
Explanation:
To build a custom big object to support storing more than 100 million records in Salesforce, a data architect should use Metadata API or Big Object in setup. Metadata API is an API that allows developers to create, retrieve, update, or delete metadata components in Salesforce programmatically. Big Object in setup is a user interface that allows admins to create big objects declaratively without writing code. Both tools can be used to define custom big objects and their fields, indexes, and relationships in Salesforce.
Option A is incorrect because DX (Developer Experience) is a set of tools that allows developers to create and manage applications on Salesforce Platform, but it does not support creating big objects directly.
Option D is incorrect because Object Manager in setup is a user interface that allows admins to create and manage standard and custom objects in Salesforce, but it does not support creating big objects declaratively.
Universal Containers (UC) has a multi-level master-detail relationship for opportunities, a custom opportunity line item object, and a custom discount request. UC has opportunity as master and custom line item object as detail in master-detail relationship. UC also has a custom line item object as master and a custom discount request object as detail in another master-detail relationship. UC has a requirement to show all sums of discounts across line items at an opportunity level.
What is the recommended solution to address these requirements?
- A . Use roll-up for the line-item-level summary and a trigger for the opportunity amount summary, as only one level roll-up is allowed.
- B . Update the master-detail relationships to lookup relationships in order to allow the discount amount to roll up.
- C . Remove the master-detail relationships and rely completely on workflow/triggers to summarize the discount amount.
- D . Roll-up discount request amount at the line-item-level and line-item-level summary discount at the opportunity level.
D
Explanation:
The recommended solution to address the requirements of Universal Containers (UC) is to roll-up discount request amount at the line-item-level and line-item-level summary discount at the opportunity level. This solution would allow UC to show all sums of discounts across line items at an opportunity level using standard roll-up summary fields. Since UC has a multi-level master-detail relationship for opportunities, a custom opportunity line item object, and a custom discount request object, they can use two levels of roll-up summary fields to aggregate the discount amounts from the child objects to the parent objects. For example, they can create a roll-up summary field on the custom line item object to sum up the discount request amounts from the custom discount request object. Then, they can create another roll-up summary field on the opportunity object to sum up the line-item-level summary discounts from the custom line item object.
Universal Containers has successfully migrated 50 million records into five different objects multiple times in a full copy sandbox. The Integration Engineer wants to re-run the test again a month before it goes live into Production.
What is the recommended approach to re-run the test?
- A . Truncate all 5 objects quickly and re-run the data migration test.
- B . Refresh the full copy sandbox and re-run the data migration test.
- C . Hard delete all 5 objects’ data and re-run the data migration test.
- D . Truncate all 5 objects and hard delete before running the migration test.
B
Explanation:
The recommended approach to re-run the test is to refresh the full copy sandbox and re-run the data migration test. A full copy sandbox is a replica of the production Org, including all data, metadata, and attachments. Refreshing a full copy sandbox means creating a new copy of the production Org and replacing the existing sandbox. This would ensure that the test is run on a clean and up-to-date environment, without any leftover data or configuration from previous tests. Truncating or hard deleting objects would not be sufficient, because they would not remove all the data or metadata from the sandbox, and they could also affect other dependent objects or processes.
NTO uses opportunity forecast for its sales planning and management.
Sales users have noticed that their updates to the opportunity amount field are overwritten when PPS updates their opportunities.
How should a data architect address this overriding issue?
- A . Create a custom field for opportunity amount that sales users update separating the fields that PPS updates.
- B . Create a custom field for opportunity amount that PPS updates separating the field that sales user updates.
- C . Change opportunity amount field access to read only for sales users using field level security.
- D . Change PPS integration to update only opportunity amount fields when values is NULL.
C
Explanation:
Changing the opportunity amount field access to read only for sales users using field level security is the best way to address the overriding issue. This way, the sales users can still view the opportunity amount field but cannot edit it, and PPS can update it as the trusted source