What is a potential design issue with the following code?
trigger accountTrigger on Account (before update){ Boolean processOpportunity
= false; List<opportunity> opptysClosedLost = new List<opportunity>()
List<opportunity> IstAllOpp = [select StageName from Opportunity where
accountId IN :Trigger.newMap.keySet()]; if(!IstAllOpp.isEmpty())
processOpportunity = true; while(processOpportunity){ for(opportunity o :
IstAllOpp) if(o.StageName == 'Closed - Lost') opptysClosedLost.add(o);
processOpportunity = false; if(!opptysClosedLost.isEmpty()) delete
opptysClosedLost;

• A.SOQL could be avoided by creating a formula field for StageName in Account from the related Opportunity
• B.The code will result in a System.DmlException:Entity_is_Deleted error
• C.The code will result in a System.LimitException : Too many script statements error
• D.The code will result in a System.LimitException: Apex CPU time limit exceeded error

Comment: *

Name: *

Email: *

Verification: *

The Account edit button must be overridden in an org where a subset of users still use Salesforce Classic. The org already has a Lightning Component that will do the work necessary for the override, and the client wants to be able to reuse it,
How should a developer implement this?

• A.the edit button for both Lightning and Classic with a new Visualforce page.
• B.Override the edit button for Lightning with a Lightning Component; and for Classic, override the edit button with a Visualforce page that contains the Lightning Component.
• C.Override the edit button for both Lightning and Classic with a Lightning Component.
• D.Override the edit button for Lightning with a Lightning Page; and for Classic, override the edit button with a Visualforce pag That contains the Lightning Component.

Comment: *

Name: *

Email: *

Verification: *

A developer is writing a Visualforce page that queries accounts in the system and presents a data table with the results. The users want to be able to filter the results based on up to five fields. However, the users want to pick the five fields to use as filter fields when they run the page. Which feature of Apex code is required to facilitate this solution?

• A.Dynamic Schema binding
• B.describeSObjects()
• C.REST API
• D.SOSL queries

Comment: *

Name: *

Email: *

Verification: *

A developer is asked to update data in an org based on new business rules. The new rules state that Accounts with the type set to 'Customer' should have a status of 'Active', and Accounts with the type set to 'Prospect' should have a status of 'Pending'. No other changes to data should be made.
Which code block will accurately meet the business requirements?
Map<String, String> statusMap = new Map<String, String>{'Customer'=>'Active',

• A.'Prospect'=>'Pending'}
  List<Account> accountUpdates = new List<Account>();
  for ( Account a : [SELECT Id, Type FROM Account]){
  if ( statusMap.containsKey(a.Type) ) {
  a.Status = a.Type == 'Customer' ? 'Active' : 'Pending';
  }
  accountUpdates.add(a);
  }
  update accountUpdates;
  Map<String, String> statusMap = new Map<String, String>{'Customer'=>'Active',
• B.for ( Account a : [SELECT Id, Type FROM Account]){
  if ( String.isNotBlank(a.Type) && a.Type == 'Customer' ){
  a.Status = 'Active';
  }
  if ( String.isNotBlank(a.Type) && a.Type == 'Prospect' ){
  a.Status = 'Pending';
  }
  accountUpdates.add(a);
  }
  update accountUpdades;
  List<Account> accountUpdates = new List<Account>();
• C.'Prospect'=>'Pending'}
  List<Account> accountUpdates = new List<Account>();
  for ( Account a : [SELECT Id, Type FROM Account WHERE Status IN
  :statusMap.keySet()]){
  a.Status = statusMap.get(a.Type);
  accountUpdates.add(a);
  }
  update accountUpdates;
  List<Account> accountUpdates = new List<Account>();
• D.for ( Account a : [SELECT Id, Type FROM Account]){
  a.Status = a.Type == 'Customer' ? 'Active' : 'Pending';
  accountUpdates.add(a);
  }
  update accountUpdates;

Comment: *

Name: *

Email: *

Verification: *

A developer writes the following Apex trigger so that when a Case is closed, a single Survey record is created for that Case. The issue is that multiple Survey_c records are being created per Case.

What could be the cause of this issue?

• A.A workflow rule is firing with a Field Update action
• B.A user is editing the record multiple times
• C.A workflow rule is firing with a Create Task action
• D.A user is creating the record as Closed

Comment: *

Name: *

Email: *

Verification: *