SF-PD2 Practice Test 16 — 15 Questions

Question 1

A developer is refactoring a large legacy trigger. They want to ensure performance does not degrade while maintaining test coverage. Which TWO practices should be followed to ensure high-quality, performant testing?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Create a data factory class to handle object creation and common test data scenarios.. Data factory classes and bulk data testing are critical for PD2-level development. Using data factories centralizes object creation, reducing maintenance overhead, while bulk testing ensures that logic performs efficiently when handling the maximum allowed batch size of 200 records. These practices prevent governor limit exceptions and ensure that the code scales effectively in a production environment with high transaction volumes.

Answer

Insert test records within the @isTest methods to ensure data isolation for every test run.

Answer

Use System.runAs() to test user permissions and visibility settings for every individual record.

Answer

Use the SeeAllData=true annotation on all test classes to ensure full visibility.

Question 2

Refer to the exhibit. A developer attempts a deployment using Salesforce CLI. The deployment fails with the circular dependency error shown. What is the root cause of this failure?

Accepted Answer

The classes share a cyclic reference, preventing the compiler from determining the initialization order.. Circular dependencies occur when two Apex classes reference each other's static methods or class variables directly. During compilation, the Apex compiler cannot resolve the symbols because each class requires the other to be compiled first. This scenario highlights the importance of modular design and the use of interfaces or abstract classes to decouple interdependent logic, which allows the deployment to proceed smoothly.

Answer

The classes are missing the 'global' access modifier.

Answer

The deployment is using a source-format package that lacks a proper 'package.xml' file.

Answer

The test classes for these Apex classes were not included in the deployment package.

Question 3

A developer needs to write a unit test for an asynchronous future method that updates account records. How should the developer structure the test to ensure the asynchronous code executes and validates correctly?

Accepted Answer

Enclose the future method invocation between Test.startTest() and Test.stopTest() to force synchronous execution.. Wrapping the asynchronous invocation block inside Test.startTest() and Test.stopTest() forces all asynchronous calls queued within the block to execute synchronously before Test.stopTest() completes. This pattern is fundamental in Salesforce testing because it allows developers to reliably assert database states modified by future methods, batch apex, or queueable jobs, preventing false test failures caused by execution timing races.

Answer

Call the future method directly, then immediately query the database to verify updates without any extra context blocks.

Answer

Use Thread.sleep() to pause the main test thread for five seconds, giving the asynchronous queue enough time to finish processing.

Answer

Annotate the test method with @IsTest(isAsync=true) to instruct the Apex runtime to run the test in parallel execution mode.

Question 4

A developer is building a search feature that must query across multiple objects. What is the most performant approach to searching for a term that might exist in any field?

Accepted Answer

Use a SOSL query to perform a multi-object search.. SOSL is optimized specifically for full-text searching across multiple objects. Unlike SOQL, which is designed for structured data retrieval and field filtering, SOSL indexes text fields to return results quickly. Using SOSL ensures that the search functionality remains performant as record volumes increase, preventing the performance degradation that would occur if multiple SOQL queries were executed sequentially to achieve the same result.

Answer

Run multiple SOQL queries and combine the results in Apex.

Answer

Implement a custom Apex search using a loop over all records.

Answer

Query the Setup Audit Trail object for search results.

Question 5

A developer wants to log information to the Debug Log for a specific class only, without cluttering the logs for the entire organization. What is the most efficient way to achieve this?

Accepted Answer

Use the Debug Logs Setup page to create a Trace Flag for the user/class.. Setting a 'Trace Flag' for a specific user or class is the standard Salesforce tool for targeted logging. This allows developers to isolate log output to their specific testing or debugging activities, preventing the organization's overall log capacity from being consumed by irrelevant system-wide logs. It is a fundamental skill for keeping production and sandbox environments manageable during active development and troubleshooting phases.

Answer

Set the organization-wide debug log level to 'FINEST'.

Answer

Hardcode log level changes in the Apex class constructor.

Answer

Use 'System.setLogLevel()' in the Apex code.

Question 6

Refer to the exhibit. A developer encounters this error during a unit test. What is the most likely cause, and how should it be resolved?

Accepted Answer

The trigger logic is missing a bulkified query pattern.. The 101 SOQL limit is triggered when a loop performs a query for every record in a collection. Developers should refactor code to move queries outside of loops by collecting IDs into a set and performing a single, bulkified SOQL query. This pattern is fundamental to Salesforce development, ensuring that applications remain performant and scalable regardless of the volume of data processed during transactions.

Answer

The test class needs more setup data, so add more records.

Answer

Increase the SOQL limit by modifying the Org settings.

Answer

Change the test class to run as a user with fewer permissions.

Question 7

A developer wants to ensure that their Apex code is tested against a specific set of data that is consistent across all sandbox environments. What is the best way to achieve this?

Accepted Answer

Use the @testSetup annotation to create data once per class.. Using @testSetup methods allows developers to create a baseline set of data that executes once for the entire test class. This ensures that every test method starts with the same data state, reducing setup redundancy and improving test reliability. This consistency is essential for debugging and ensuring that tests remain stable as the project grows and evolves over time.

Answer

Hardcode the data creation in each individual @isTest method.

Answer

Query for data that already exists in the environment.

Answer

Create a separate trigger to populate test data during deployment.

Question 8

A developer needs to verify that an asynchronous Apex process (Future method) executes correctly in a test environment. Which approach is best suited to ensure the test waits for the asynchronous execution to finish before asserting the results?

Accepted Answer

Wrap the asynchronous call between Test.startTest() and Test.stopTest().. The Test.startTest() and Test.stopTest() methods define a block where the platform processes asynchronous operations, such as @future methods or Queueable Apex. When Test.stopTest() is called, the platform forces the completion of all asynchronous jobs within the test context, allowing the developer to assert the outcomes synchronously. This is vital for ensuring test reliability and preventing race conditions during verification.

Answer

Use the Thread.sleep() method to pause the test execution until the job completes.

Answer

Query the AsyncApexJob table to check the status of the job before asserting.

Answer

Use the System.enqueueJob() method within the test to monitor the job.

Question 9

What is the primary benefit of using a Platform Cache for application data?

Accepted Answer

It reduces latency by storing frequently accessed data in memory.. Platform Cache provides a high-speed, in-memory storage layer that allows developers to cache frequently accessed data. This significantly reduces the need for expensive SOQL queries or API calls, resulting in faster response times and lower CPU usage. By storing data in the cache, the application becomes more efficient and scalable, especially when handling high-frequency access to static or semi-static information.

Answer

It provides permanent storage for large files like images.

Answer

It eliminates the need for writing any SOQL queries.

Answer

It automatically synchronizes data with external systems.

Question 10

An Apex trigger is failing due to a 'System.LimitException: Too many DML statements: 151'. What is the optimal refactoring approach?

Accepted Answer

Refactor the code to collect records in a List and perform one DML.. The error clearly indicates the failure to bulkify DML. The solution is to collect all records needing updates into a single list and perform one DML statement after the loop. This reduces 150+ individual operations to one, keeping the code within governor limits and significantly improving performance by reducing the number of round-trips to the database during the transaction processing cycle.

Answer

Increase the DML statement limit in the Apex class.

Answer

Move the logic to a @future method to allow more DML.

Answer

Use the Database.update() method with allOrNone set to false.

Question 11

A developer needs to improve the performance of a report that queries millions of records across several custom objects. The architect suggests using Skinny Tables. Which TWO statements correctly describe the benefits and limitations of Skinny Tables? (Choose two.)

Accepted Answer

Skinny tables do not include soft-deleted records, which reduces the volume of data scanned.. Skinny tables are a specialized performance feature in Salesforce that improve query performance by mapping frequently used fields into a separate table. This table contains only the necessary columns, reducing the number of joins required and the overall amount of data scanned. They are particularly useful for large tables but require support assistance for creation and maintenance.

Answer

Skinny tables can include fields from different objects, effectively acting as a pre-joined view.

Answer

Skinny tables are automatically created by Salesforce for any object exceeding 1 million records.

Answer

Skinny tables can be created by developers directly using the Metadata API or Tooling API.

Question 12

A developer needs to deploy a complex Apex class and its corresponding test class to production. The org's unit test coverage is currently 74%. Which statement accurately describes the deployment requirements?

Accepted Answer

The deployment will fail because the aggregate code coverage must be at least 75%.. Salesforce mandates a minimum of 75% code coverage for all Apex classes and triggers in an organization to deploy to production. Since the current coverage is 74%, the deployment will fail unless the new tests push the total organization coverage above the required threshold. This rule ensures that developers maintain high-quality code and provides a safety net against regressions, emphasizing the critical importance of writing effective tests during development.

Answer

The deployment will succeed because unit tests only need to be written for the new code.

Answer

The developer can bypass the coverage requirement by using the 'Ignore Warnings' flag in deployment.

Answer

The deployment will succeed if the new Apex class itself has 75% coverage.

Question 13

Refer to the exhibit. The developer has implemented the security check inside the 'process' method. Why is this implementation insufficient for a secure, professional-grade enterprise application?

Accepted Answer

The check only validates object-level access and ignores Field-Level Security (FLS).. Performing security checks inside a method is better than nothing, but it fails to address the 'CRUD/FLS' enforcement at the query level and often lacks granularity. The best practice is to utilize a security-focused library or framework to enforce FLS (Field-Level Security) consistently across all fields being accessed, rather than relying on manual, ad-hoc checks which are prone to developer oversight during code maintenance.

Answer

The check should be performed using 'without sharing' to ensure all data is accessible.

Answer

The class should be declared 'inherited sharing' to avoid performance overhead.

Answer

The method should be annotated with @AuraEnabled to ensure it is secure for Lightning.

Question 14

Refer to the exhibit. A developer is attempting to push source code to a scratch org and encounters the error shown. The developer confirms that 'utils.js' and 'utils.js-meta.xml' exist in the 'force-app/main/default/lwc/utils/' directory. What is the most likely cause of this error?

Accepted Answer

The main JavaScript file in the 'utils' folder must be named 'utils.js'.. LWC requires a specific file structure and naming convention for components and modules. When importing a local module, the framework looks for a component folder and a corresponding main JavaScript file. If the main file name does not match the folder name, the compiler cannot resolve the import, leading to deployment failures.

Answer

The developer forgot to add the '@salesforce/resource' prefix to the import.

Answer

The 'utils' component is missing the 'isExposed' tag in its metadata file.

Answer

The developer needs to run 'sfdx force:source:pull' first to sync metadata.

Question 15

Refer to the exhibit. The developer observes the error above. What is the most efficient architectural change to prevent this limit from being hit?

Accepted Answer

Refactor the logic to collect IDs and execute a single SOQL query before the loop.. The 'Too many SOQL queries: 101' error indicates that queries are being executed inside a loop. By moving the SOQL queries outside of the loop and utilizing Map-based lookups, the developer can satisfy the requirements for data access while adhering to governor limits. This transition from iterative query execution to bulkified access is the hallmark of scalable Salesforce development.

Answer

Wrap the SOQL queries in a try-catch block to handle the exception gracefully.

Answer

Increase the Apex heap size in the class definition.

Answer

Use an @future method to process each record individually.