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

Questions 16–20

1. 16application · medium

   A developer is writing a test for a class that updates a custom object's record type based on a picklist value. The developer wants to avoid hard-coding record type IDs in the test. What is the best practice?

   • ACreate a record type in the test using Apex code.
   • BUse @isTest(SeeAllData=true) to access the record type directly.
   • CQuery for the record type using the DeveloperName and SObjectType in the test.
   • DUse a hard-coded record type ID from the production org.
   Reveal Solution Discussion Select an answer first
2. 17expert · hard

   A team is developing a large Salesforce org with many test classes. They notice that test data creation code is duplicated across multiple test classes, leading to maintenance issues. They decide to implement a test data factory. Which design consideration is most important for the factory to be effective?

   • AThe factory should be a non-test class so it can be used in production code as well.
   • BThe factory should use @isTest(SeeAllData=true) to access existing data and reduce the need for creation.
   • CThe factory should use static resources to load data, avoiding Apex code entirely.
   • DThe factory should provide methods that return sObjects with default field values, allowing tests to override specific fields as needed.
   Reveal Solution Discussion Select an answer first
4. 18foundation · medium

   A developer is writing an Apex test for a trigger that updates Account records. They want to use standard Salesforce records as test data. What is the most accurate statement about using standard records in this scenario?

   • AStandard records such as accounts and contacts are always available in tests without any setup, and they can be modified directly to test trigger logic.
   • BStandard records can be used as test data, but they must be created within the test method or test class to ensure data isolation and reliable results.
   • CStandard records are read-only in tests, so developers must use custom objects or static resources to provide test data for triggers.
   • DStandard records are automatically available in tests, but only if the test class is annotated with @isTest(SeeAllData=true).
   Reveal Solution Discussion Select an answer first
5. 19expert · hard

   A developer is testing a trigger that makes a callout to an external system to validate a zip code. The trigger is invoked when a Lead is inserted. The developer wants to ensure the callout is mocked and that the test does not fail due to governor limits. Which test structure is correct?

   • ASet the mock after Test.startTest() and insert the Lead after Test.stopTest().
   • BInsert the Lead before Test.startTest(), set the mock, and call Test.stopTest() at the end.
   • CUse @isTest(SeeAllData=true) and do not set a mock, allowing the real callout to execute.
   • DSet the mock with Test.setMock, insert the Lead inside Test.startTest(), and call Test.stopTest() after the insert.
   Reveal Solution Discussion Select an answer first
6. 20application · medium

   A developer is writing a test for a class that sends an email to a Contact's email address. The test needs to verify that the email is sent. Which source of test data should the developer use?

   • AUse @isTest(SeeAllData=true) to access an existing Contact with a valid email address.
   • BUse a static resource with a CSV file containing Contact records.
   • CUse Test.loadData() to load a Contact from a static resource.
   • DCreate a Contact record with a valid email address in the test method.
   Reveal Solution Discussion Select an answer first