Newly Released Salesforce PDI Exam PDF

Page: 9 / 12

Question 36

Which statement should be used to allow some of the records in a list of records to be inserted if others fail to be inserted?

Options:

insert records

Database.insert (records, false)

Insert (records, false)

Database.insert(records, true)

Question 37

Since Aura application events follow the traditional publish- subscribe model, which method is used to fire an event?

Options:

registerEvent

fireEvent ()

emit{)

fire()

Question 38

What should a developer do to check the code coverage of a class after running all tests?

Options:

View the Class Test Percentage tab on the Apex Class list view in Salesforce Setup.

View the code coverage percentage for the class using the Overall Code Coverage panel in the Developer Console Tests tab,

View the Code Coverage column in the list view on the Apex Classes page.

Select and run the class on the Apex Test Execution page in the Developer Console.

Question 39

Assuming that name is a String obtained by an tag on a Visualforce page, which two SOQL queries performed are safe from SOQL injection? Choose 2 answers

Options:

Option A

Option B

Option C

Option D

Answer:

A, C

Explanation:

Option A:

String query = 'SELECT Id FROM Account WHERE Name LIKE \'%' + String.escapeSingleQuotes(name) + '%\'';

List results = Database.query(query);

Explanation: This option uses String.escapeSingleQuotes(name) to sanitize the name variable. This method escapes any single quotes in the input, preventing malicious input from breaking out of the string context in the SOQL query.

[Reference: Salesforce Apex Developer Guide - Escaping Single Quotes, Why Safe: By escaping single quotes, it mitigates the risk of SOQL injection attacks that rely on manipulating string literals., , Option C:, , String query = '%' + name + '%';, List results = [SELECT Id FROM Account WHERE Name LIKE :name];, Explanation: This option uses a bind variable (:name) in the SOQL query. When variables are bound in this way, Salesforce automatically handles escaping and ensures that the input cannot alter the structure of the query., Reference: Salesforce Apex Developer Guide - Using Apex Variables in SOQL and SOSL Queries, Why Safe: Bind variables are the recommended way to include user input in SOQL queries safely, as they prevent injection by treating the input as a parameter rather than part of the query string., , Option B:, , String query = 'SELECT Id FROM Account WHERE Name LIKE \'%' + name.noQuotes() + '%\'';, List results = Database.query(query);, Explanation: The method noQuotes() does not exist in the Apex String class. Therefore, this code does not properly sanitize the name variable., Reference: Salesforce Apex Developer Guide - String Class Methods, Why Unsafe: Without proper sanitization, the name variable could contain malicious SOQL code, leading to injection vulnerabilities., , Option D:, , String query = 'SELECT Id FROM Account WHERE Name LIKE \'%' + name + '%\'';, List results = Database.query(query);, Explanation: This option directly concatenates the name variable into the query string without any form of sanitization or escaping., Reference: Salesforce Apex Developer Guide - SOQL Injection Overview, Why Unsafe: Direct concatenation of user input without sanitization leaves the application vulnerable to SOQL injection attacks., , Conclusion:, Safe Options: A and C are safe from SOQL injection because they properly handle user input through escaping and bind variables, respectively., Unsafe Options: B and D are unsafe as they do not adequately prevent SOQL injection., ]

Page: 9 / 12