A developer needs test data for Apex test classes.
What can the developer use to provide test data to the test methods? (Choose two.)

• A.List<sObject> Is = Test.loadDat (Lead.sObjectType, $Resource + 'myTestLeads');
• B.List<sObject> Is = Test.loadData (Lead.sObjectType, 'myTestLeads');
• C.myDataFactory.createTestRecords (10)
• D.Database.createTestRecords (10)

Comment: *

Name: *

Email: *

Verification: *

Universal Containers develops a Salesforce application that requires frequent interaction with an external REST API.
To avoid duplicating code and improve maintainability, how should they implement the APL integration for code reuse?

• A.Use a separate Apex class for each API endpoint to encapsulate the integration logic,
• B.Include the API integration code directly in each Apex class that requires it.
• C.Create a reusable Apex class for the AFL integration and invoke it from the relevant Apex classes.
• D.Store the APT integration code as a static resource and reference it in each Apex class.

Comment: *

Name: *

Email: *

Verification: *

Which of the follow be used together in DML operations (transaction)? (Choose two.)

• A.Account - Order
• B.Case - CaseComment
• C.Opportunity - User
• D.Acco u nt - Acco u ntS ha re

Comment: *

Name: *

Email: *

Verification: *

An org has a requirement that an Account must always have one and only one Contact listed as Primary. So selecting one Contact will de-select any others. The client wants a checkbox on the Contact called 'Is Primary' to control this feature.
The client also wants to ensure that the last name of every Contact is stored entirely in uppercase characters.
What is the optimal way to implement these requirements?

• A.Write a Validation Rule on the Contact for the Is Primary logic and a before update trigger on Contact for the last name logic.
• B.Write an after update trigger on Contact for the Is Primary logic and a separate before update trigger on Contact for the last name logic.
• C.Write a single trigger on Contact for both after update and before update and callout to helper classes to handle each set of logic.
• D.Write an after update trigger on Account for the Is Primary logic and a before update trigger on Contact for the last name logic.

Comment: *

Name: *

Email: *

Verification: *

A developer is working with existing functionality that tracks how many times a stage has changed for an Opportunity. When the opportunity's stage is changed, a workflow rule is fired to increase the value of a filed by one. The developer wrote an after trigger to create a child record when the field changes from 4 to 5.
A user changes the stage of an Opportunities and manually sets the count field to 4. The count field updates to 5, but the child record is not created.
What is the reason this is happening?

• A.After triggers fire before workflow rules.
• B.Trigger .old does not contain the updated value of the count field.
• C.Trigger .new does not change after a field update.
• D.After triggers are not fired after field updates.

Comment: *

Name: *

Email: *

Verification: *