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: *

If the "PageReference.setRedirect" Apex function is set to False, what type of request is made?

• A.Get request
• B.Postback request
• C.If PageReference points to the same controller and subset of extensions, postback request, otherwise get request

Comment: *

Name: *

Email: *

Verification: *

There are user complaints about slow render times of a custom data table within a Visualforce page that loads thousands of Account records at once. What can a developer do to help alleviate such issues?

• A.Upload a third-party data table library as a static resource.
• B.Use JavaScript remoting to query the accounts.
• C.Use the standard Account List controller and implement pagination.
• D.Use the transient keyword in the Apex code when querying the Account records.

Comment: *

Name: *

Email: *

Verification: *

A custom field Exec_Count_c of type Number is created on an Account object. An account record with value of "1" for a: Exec_Count_c is saved. A workflow field update is defined on the Exec_Count_c field, to increment its value every time an account record is created or updated. The following trigger is defined on the account:
trigger ExecOrderTrigger on Account (before insert, before update, after insert, after update){ for (Account accountInstance: Trigger.New){ if (Trigger
. isBefore){ accountInstance Exec_Count_c += 1; } System. debug
(accountInstance.Exec_Count_c); } }

• A.1, 2, 3, 3
• B.2, 2, 4, 4
• C.1, 2, 3, 4
• D.2, 2, 3, 3

Comment: *

Name: *

Email: *

Verification: *

An org has 2 requirement that addresses on Contacts and Accounts should be normalized to a company standard by Apex code any time that they are saved.
What is the optimal way to implement this?

• A.Apex trigger on Contact that calls the Account trigger to normalize the address
• B.Apex triggers on Contact and Account that call a helper class to normalize the address
• C.Apex trigger on Account that calls the Contact trigger to normalize the address
• D.Apex triggers on Contact and Account that normalize the address

Comment: *

Name: *

Email: *

Verification: *