A business requires that every parent record must have a child record. A developer writes an Apex method with two DML statements to insert a parent record and a child record.
A validation rule blocks child records from being created. The method uses a try/catch block to handle the DML exception.
What should the developer do to ensure the parent always has a child record?

• A. Delete the parent record in the catch statement when an error occurs on the child record DML operation.
• B. Set a database savepoint to rollback if there are errors.
• C. Use addExror() on the parent record if an error occurs on the child record.
• D. Use Catabase.inserc() and set the all = parameter to true,

A developer wrote a class named asccuntRisteryManager that relies on field history tracking. The class has a static method called getaccountHistory that Lakes in an Account as a parameter and returns a list of associated accountHistory object records.
The following test fails:

What should be done to make this test pass?

• A. Use Test. isRunningTest (] in getAccountHistory() to conditionally return fake AccountHistory records.
• B. The tact method should he delated since this code cannat be tested
• C. Create Accountdistory records manually in the test setup and write a query to get them.
• D. Use @isTest (SeeAllData=true] to see historical data from the org and query for Accountdistory records.

Just prior to a new deployment the Salesforce administrator, who configured a new order fulfillment process feature in a developer sandbox, suddenly left the company.
Ag part of the UAT cycle, the users had fully tested all of the changes in the sandbox and signed off on them; making the Order fulfillment feature ready for its go-live in the production environment.
Unfortunately, although a Change Set was started, it was not completed by the former administrator.
A developer is brought in to finish the deployment.
What should the developer do to identify the configuration changes that need to be moved into production?

• A. Set up Continuous Integration and a Git repository to automatically merge all changes from the sandbox metadata with the production metadata.
• B. Use the Metadata API and a supported development IDE to push all of the configuration from the sandbox into production to ensure no changes are lost.
• C. In Salesforce setup, look at the last modified date for every object to determine which should be added to the Change Set.
• D. Leverage the Setup Audit Trail to review the changes made by the departed Administrator and identify which changes should be added to the Change Set.

A developer wrote a trigger on Opportunity that will update a custom Last Sold Date field on the Opportunity's Account whenever an Opportunity is closed. In the test class for the trigger, the assertion to validate the Last Sold Date field fails.
What might be causing the failed assertion?

• A. The test class has not re-queried the Account record after updating the Opportunity.
• B. The test class has not implemented seealldata=true in the test method.
• C. The test class has not defined an Account owner when inserting the test data.
• D. The test class is not using System. runs () to run tests as a Salesforce administrator.