Developer Fundamentals practice questions

50

Why wrong: 50 is incorrect; the limit is higher for synchronous transactions.

200

Why wrong: 200 is the limit for SOSL queries, not SOQL queries.

500

Why wrong: 500 is too high for a single synchronous transaction.

SELECT Id, Name, CONCAT(Contacts) FROM Account

Why wrong: CONCAT is not a valid SOQL function for relationship queries.

SELECT Id, Name, (SELECT Id, LastName FROM Contact) FROM Account

Why wrong: The subquery must use the plural child relationship name, which is 'Contacts'.

SELECT Id, Name, Contacts__r FROM Account

Why wrong: Child relationships must be queried as a subquery list.

enforce sharing

Why wrong: This is not a valid Apex keyword.

without sharing

Why wrong: Disables sharing rule enforcement.

inherited sharing

Why wrong: Inherited sharing adopts the sharing context of the class that called it.

System.Security

Why wrong: System.Security has methods for stripInaccessible, but describe results come from Schema classes.

UserInfo

Why wrong: UserInfo provides details about the current user like profile ID and language, not FLS.

ApexPages.StandardController

Why wrong: StandardController is used for Visualforce page controllers and extensions.

Execute the query using Database.queryWithBinds() with a restricted access modifier.

Why wrong: Database.queryWithBinds does exist, but string concatenation with bind syntax is the correct concept; the modifier option is a distractor.

Use String.escapeSingleQuotes() on all user inputs before concatenating into the query string.

Why wrong: While it helps with single quotes, bind variables are the definitive best practice and more secure.

Enclose all dynamic parameters in single quotes within the dynamic SOQL query string.

Why wrong: This approach is vulnerable to SOQL injection if the user input contains quote characters.

Coordinate

Why wrong: Coordinate is not a valid Apex primitive data type.

Address

Why wrong: Address is a compound compound field data structure, but Location is specifically for latitude/longitude points.

GeoPoint

Why wrong: GeoPoint is a SOQL distance function, not an Apex data type.

Access standard relationship fields directly without querying if the records are in Trigger.new.

Why wrong: Trigger.new only contains fields for the object itself, not parent fields unless queried.

Loop through each Contact and issue a separate SOQL query for its Account.

Why wrong: This violates governor limits by issuing SOQL queries inside a loop.

Use the Database.getQueryLocator method with Trigger.new.

Why wrong: getQueryLocator is used primarily for batch apex, not standard trigger context.

Queueable

Why wrong: Queueable is an interface used for asynchronous processing, not a collection type.

List

Why wrong: Lists allow duplicate values and require linear scans for existence checks.

Map

Why wrong: Maps store key-value pairs, which is overkill for a simple collection of unique values.

HTML template files

Why wrong: HTML template files represent the View layer.

CSS style sheets

Why wrong: CSS style sheets define the styling in the View layer.

JavaScript controller files

Why wrong: JavaScript files represent part of the Controller layer in client-side code.

Database.insert(records, AccessType.ENFORCE_ACCESSIBLE)

Why wrong: ENFORCE_ACCESSIBLE throws an exception rather than stripping inaccessible fields.

Approval.lock()

Why wrong: Approval locking is used for record approval processes, not FLS enforcement.

Schema.sObjectType.fields.isAccessible()

Why wrong: This is a boolean check method, not a method that strips data.

Database.query() with dynamic bindings

Why wrong: Database.query executes SOQL, which cannot query multiple disparate objects at once.

SOQL query with multiple WHERE clauses

Why wrong: SOQL queries can only query one object type per statement.

Global Search API via REST

Why wrong: Apex code should use SOSL rather than making external REST API calls for internal search.

Trigger.newMap

Why wrong: Trigger.newMap is a map of IDs to the new sObject versions, not a list.

Trigger.old

Why wrong: Trigger.old contains the old versions of sObject records for update and delete triggers.

Trigger.caller

Why wrong: Trigger.caller is not a valid Apex trigger context variable.

List<Map<Id, Case>>

Why wrong: A list of maps does not provide direct key-based lookup for grouping.

Set<Map<Id, Case>>

Why wrong: Maps cannot be elements of a Set because they are not hashable primitives.

Map<Id, Case>

Why wrong: Map<Id, Case> only allows one Case per AccountId, which fails if multiple cases share an account.

It throws a compilation error because sharing modes conflict.

Why wrong: Inherited sharing is specifically designed to interoperate safely.

It executes in system mode without enforcing sharing rules.

Why wrong: That is the behavior of without sharing.

It prompts the user to select a sharing mode at runtime.

Why wrong: Sharing mode is determined statically by the execution stack, not user prompts.

String.valueOf(jsonString)

Why wrong: String.valueOf simply returns the string representation.

JSON.serialize()

Why wrong: JSON.serialize converts Apex objects into a JSON string.

JSON.parse()

Why wrong: JSON.parse is not a valid method in the JSON class.

merge()

Why wrong: merge() is used for DML operations on sObjects, not for combining collections.

combine()

Why wrong: combine() is not a valid collection method in Apex.

putAll()

Why wrong: putAll() is used specifically for Map collections, not Sets.

static readonly Integer MAX_COUNT = 10;

Why wrong: readonly is not an Apex modifier.

immutable Integer MAX_COUNT = 10;

Why wrong: immutable is not an Apex keyword.

const Integer MAX_COUNT = 10;

Why wrong: const is not a reserved keyword in Apex.

getNumElements()

Why wrong: getNumElements is not a valid Apex method.

length()

Why wrong: length() is used for Strings, not collections.

count()

Why wrong: count() is a SOQL aggregate function, not a collection method.

Use Database.upsert with strict mode enabled inside the trigger loop.

Why wrong: Performing DML statements inside trigger loops violates governor limits.

Query the database inside a for loop for every record in Trigger.new.

Why wrong: This leads to SOQL limit exceptions.

Use an asynchronous @future method to validate duplicates after insert.

Why wrong: Future methods run after insert and cannot prevent the transaction from committing the duplicate records.

WITH RECYCLE_BIN

Why wrong: This is not valid SOQL syntax.

SYSTEM MODE

Why wrong: System mode controls sharing enforcement, not visibility of deleted records.

INCLUDE DELETED

Why wrong: INCLUDE DELETED is not a valid SOQL clause.