Describe When and How to Use Various Sources of Test Data. PLATFORM-DEVELOPER-I Practice Questions (Page 3)

Questions 11–15

1. 11foundation · easy

   What is the primary purpose of a test data factory in Salesforce?

   • ATo automatically generate test classes
   • BTo load data from external systems into Salesforce
   • CTo generate random data for performance testing
   • DTo create reusable and maintainable test data setup
   Reveal Solution Discussion Select an answer first
2. 12application · medium

   A developer needs to test a batch class that processes Account records. The test requires a large number of Account records with specific field values. To avoid writing hundreds of lines of Apex code, the developer decides to use a static resource. What is the correct way to load this data in the test?

   • AUse Test.loadData(Account.SObjectType, 'staticResourceName') and ensure the CSV file has a header row matching field API names.
   • BUse @isTest(SeeAllData=true) and query the static resource directly in the test.
   • CUse System.enqueueJob(new MyBatchClass()) and pass the static resource as a parameter.
   • DCreate the Account records in a loop with random field values and insert them.
   Reveal Solution Discussion Select an answer first
4. 13foundation · medium

   A developer is writing a test for a class that calculates a discount based on a custom setting and an Account's industry. The test must verify the calculation for a specific industry. The developer wants to ensure the test is self-contained and does not depend on org data. Which approach best achieves this?

   • AUse a test data factory to create the Account and custom setting, and then use @isTest(SeeAllData=true) to ensure the factory can access org data.
   • BCreate the Account and custom setting within the test method, and use the default data isolation to prevent access to org data.
   • CUse @isTest(SeeAllData=true) to access an existing Account and custom setting in the org, and then modify them to match the test scenario.
   • DUse a static resource to load the Account and custom setting data, and then query them in the test.
   Reveal Solution Discussion Select an answer first
5. 14application · medium

   A developer is writing a test class for a trigger that updates a custom object's 'Status__c' field based on related Account records. The developer wants to ensure the test is self-contained and does not depend on any existing data in the org. Which approach should the developer use to set up the test data?

   • AUse Test.loadData() with a static resource containing Account records, but do not create the custom object records.
   • BCreate an Account and the custom object records directly in the test method using SObject constructors and field assignments.
   • CUse @isTest(SeeAllData=true) on the test class to access existing Account records in the org.
   • DQuery for existing Account records using a SOQL query in the test method without any annotation.
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   A developer is testing a trigger that performs a callout when a record is inserted. The test must ensure that the callout is made within the test context and that the test does not exceed governor limits. What is the correct way to structure the test?

   • ACall Test.stopTest() before inserting the record to reset limits.
   • BUse @isTest(SeeAllData=true) to allow the callout to execute without mocking.
   • CInsert the record inside Test.startTest() and call Test.stopTest() after the insert.
   • DInsert the record before Test.startTest() and call Test.stopTest() at the end of the test.
   Reveal Solution Discussion Select an answer first