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.

Creating a duplicate rule for account, lead, and contact, using standard matching rules for these objects, and setting the action to report and alert for both creates and edits can help UC fix the issue immediately by prompting users about a record that possibly exists in Salesforce. This can also generate a report regarding duplicate records that can be used for further analysis and resolution

Grouping batches by the AccountId field can improve the performance and avoid locking issues when loading Opportunity records using the Bulk API in parallel mode1. This is because the AccountId field is indexed and can be used to distribute the records evenly across batches

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.

The correct answer is A. To provide additional guidance for users when they enter information in a standard field, a data architect should provide custom help text under field properties. This will display a help icon next to the field label that users can hover over to see the help text. Option B is incorrect because creating a custom page with help text for user guidance will require additional development effort and may not be easily accessible by users. Option C is incorrect because adding custom help text in default value for the field will overwrite the actual default value of the field and may confuse users. Option D is incorrect because adding a label field with help text adjacent to the custom field will clutter the page layout and may not be visible to users.