Authentic Salesforce Certification Exam Development-Lifecycle-and-Deployment-Architect Questions Answers

 The best option for UC given the scenario is to opt for a multi-org strategy, where each org can have its own sales process, common rules, and operate in locale. A multi-org strategy can accommodate the different languages, sales processes, and legal requirements of the two business units. A multi-org strategy can also allow for more innovation and flexibility, as each org can customize and optimize its own functionality. A single-org strategy may not be able to support the different languages, sales processes, and legal requirements of the two business units. A single-org strategy may also limit the innovation and flexibility, as the org has to follow a standardized and consistent approach.

The most challenging factor to consider in merging the two Salesforce.com orgs into a single org is the customer data, as it may contain duplicates, inconsistencies, and conflicts. Option D suggests using standardization and de-duplication tools to merge the customer data, which is a reasonable approach. Option A is not true, as transactional sales data may have different formats, fields, and values in the two orgs. Option B is not necessary, as salespersons selling both product lines can use a single login in the merged org. Option C is not true, as business processes on standard objects may have different workflows, validation rules, and triggers in the two orgs.

 Extracting each permission set, committing and merging to source control, and running through CI checks is the best strategy to bring the issue of failing SOQL statements to the developer’s attention earlier. This way, the developers can review the changes made by the administrators, and ensure that they do not break any existing functionality or security rules. Asking administrators to only make changes to profiles instead would not solve the problem, as profiles can also affect SOQL queries. Creating a sandbox refresh strategy to ensure each sandbox is refreshed every day would not prevent the issue from happening, as the changes made by the administrators would still be propagated to the sandboxes. Advising developers to switch to SOSL queries that are more robust instead would not address the root cause of the issue, which is the lack of visibility and control over the permission sets.