Online Access Free PDII Practice Test

A developer created a class that implements the Queueable Interface, as follows:
Java
public class without sharing OrderQueueableJob implements Queueable {
public void execute(QueueableContext context) {
// implementation logic
System.enqueueJob(new FollowUpJob());
}
}
As part of the deployment process, the developer is asked to create a corresponding test class. Which two actions should the developer take to successfully execute the test class?1

• A.Implement seeAllData=true to ensure the Queueable job is able to run in bulk mode.2
• B.Ensure the running user of the test class has, at least, the View All permission on the Order object.
• C.Enclose System.enqueueJob(new OrderQueueableJob()) within Test.startTest and Test.stopTest().
• D.Implement Te3st.isRunningTest() to prevent chaining jobs during test execution.

Universal Containers has an Apex trigger on Account that creates an Account Plan record when an Account is marked as a Customer. Recently a record-triggered flow was added to update a date field. Since the addition of the flow, two Account Plan records are created. What might cause this to happen?

• A.The Apex trigger is not bulk safe and calls insert inside of a for loop.
• B.The Apex trigger does not use a static variable to ensure it only fires once.
• C.The flow is configured to use an 'Update Records' element.
• D.The flow is configured to evaluate when a record is created and every time it is edited.

A query using OR between a Date and a RecordType is performing poorly in a Large Data Volume environment. How can the developer optimize this?

• A.Use the Database.querySelector method to retrieve the accounts.
• B.Create a formula field to combine the CreatedDate and RecordType value, then filter based on the formula.
• C.Break down the query into two individual queries and join the two result sets.
• D.Annotate the method with the @Future annotation.

Salesforce users consistently receive a "Maximum trigger depth exceeded" error when saving an Account.
How can a developer fix this error?

• A.Use a helper class to set a Boolean to TRUE the first time a trigger is fired, and then modify the trigger to only fire when the Boolean is FALSE.
• B.Split the trigger logic into two separate triggers.
• C.Modify the trigger to use the isMultiThread=true annotation.
• D.Convert the trigger to use the @future annotation, and chain any subsequent trigger invocations to the Account object.

Which code snippet represents the optimal Apex trigger logic for assigning a Lead's Region based on its PostalCode, using a custom Region__c object?

• A.Region__c = r.Region_Name__c;
  }
  }
  }
• B.Region__c = reg.Region_Name__c;
  }
• C.Java
  Set<String> zips = new Set<String>();
  for(Lead l : Trigger.new) {
  if(l.PostalCode != Null) {
  zips.add(l.PostalCode);
  }
  }
  for(Lead l : Trigger.new) {
  List<Region__c> regions = [SELECT Zip_Code__c, Region_Name__c FROM Region__c WHERE Zip_Code__c IN :zips]; for(Region__c r : regions) { if(l.PostalCode == r.Zip_Code__c) {
• D.Java
  Set<String> zips = new Set<String>();
  for(Lead l : Trigger.new) {
  if(l.PostalCode != Null) {
  zips.add(l.PostalCode);
  }
  }
  List<Region__c> regions = [SELECT Zip_Code__c, Region_Name__c FROM Region__c WHERE Zip_Code__c IN :zips]; Map<String, String> zipMap = new Map<String, String>(); for(Region__c r : regions) { zipMap.put(r.Zip_Code__c, r.Region_Name__c);
  }
  for(Lead l : Trigger.new) {
  if(l.PostalCode != Null) {
• E.Java
  for (Lead l : Trigger.new) {
  Region__c reg = [SELECT Region_Name__c FROM Region__c WHERE Zip_Code__c = :l.
  PostalCode];
• F.Region__c = r.Region_Name__c;
  }
  }
  }
• G.Region__c = zipMap.get(l.PostalCode);
  }
  }
• H.Java
  Set<String> zips = new Set<String>();
  for(Lead l : Trigger.new) {
  if(l.PostalCode != Null) {
  zips.add(l.PostalCode);
  }
  }
  for (Lead l : Trigger.new) {
  List<Region__c> regions = [SELECT Zip_Code__c, Region_Name__c FROM Region__c WHERE Zip_Code__c IN :zips]; for (Region__c r : regions) { if(l.PostalCode == r.Zip_Code__c) {