Select Two (Multi-Select) Questions

Database.save()

Why wrong: Database.save does not exist; savepoints use setSavepoint.

Database.commit()

Why wrong: Database.commit is not a valid Apex method.

Database.persist()

Why wrong: Database.persist is not a valid Apex method.

Standard Page Layout Editor

Why wrong: Page Layout Editor configures field placement, not code execution.

Lightning App Builder

Why wrong: Lightning App Builder configures app pages graphically.

Trigger.oldMap

Why wrong: Trigger.oldMap is not available on insert operations.

Trigger.old

Why wrong: Trigger.old is not available on insert operations.

Trigger.operationType

Why wrong: While System.TriggerOperation exists, operationType as a direct context variable list is not standard terminology compared to new and newMap.

Integer variables default to 1 if unassigned.

Why wrong: Unassigned integers default to null, not 1.

Apex supports dynamic duck typing without variable declarations.

Why wrong: Apex is strictly statically typed.

Boolean variables default to true if unassigned.

Why wrong: Unassigned booleans default to null, not true.

TreeSet

Why wrong: TreeSet does not exist in Apex.

Set

Why wrong: Sets do not guarantee any specific iteration order.

Queue

Why wrong: Queue is not an Apex collection type.

System.describeFields()

Why wrong: describeFields is not a valid System method.

Object.inspect()

Why wrong: inspect is not an Apex method.

Database.getMetadata()

Why wrong: Database.getMetadata is not a valid Apex method.

Omitting LIMIT clauses on large queries to ensure all records are fetched at once.

Why wrong: Omitting limits on unbounded tables can cause heap size and row limit violations.

Placing SOQL queries inside helper methods called within loops.

Why wrong: Putting queries inside loops is an anti-pattern that violates query limits.

Place DML statements inside 'for' loops to ensure immediate database commits.

Why wrong: DML inside loops will trigger DML limits after 150 iterations.

Use the 'webservice' keyword on helper methods called by triggers.

Why wrong: The 'webservice' keyword exposes methods as SOAP web services and is not used for trigger optimization.

Execute a separate SOQL query for every single record in Trigger.new.

Why wrong: Querying per record violates SOQL query limits and is an anti-pattern.

Disable FLS checks in user profile settings before executing queries.

Why wrong: Modifying profiles is an admin configuration task, not an Apex development pattern for enforcing security.

Execute queries inside an asynchronous @future method.

Why wrong: Asynchronous methods run in system context, bypassing user-level sharing rules.

Use the 'without sharing' keyword on all transaction controllers.

Why wrong: 'without sharing' explicitly disables sharing rule enforcement.

Apex Triggers cannot be deactivated without deploying code changes.

Why wrong: Incorrect. Triggers can be managed or bypassed depending on deployment, but this is not a core technical reason.

Record-Triggered Flows cannot run asynchronously.

Why wrong: Incorrect. Flows can run asynchronously using scheduled paths or async paths.

Flows cannot execute before-save updates.

Why wrong: Incorrect. Flows fully support before-save updates.

Hardcode record IDs directly from the sandbox into assertions.

Why wrong: Hardcoding record IDs causes tests to fail when deployed to other environments where IDs differ.

Query production records directly in every assertion to verify live system status.

Why wrong: Unit tests should not rely on live production data querying.

Use @isTest(SeeAllData=true) on all test classes to ensure maximum compatibility with production data.

Why wrong: SeeAllData=true should be avoided unless strictly necessary to prevent dependency on brittle production state.

Declaring every class with 'without sharing'.

Why wrong: without sharing bypasses security and increases vulnerability.

Relying solely on Lightning Web Component HTML rendering tags.

Why wrong: Client-side hiding does not secure server-side Apex queries or DML operations.

Execute a separate SOQL query for every child record individually.

Why wrong: This violates bulkification and governor limits.

Always use SELECT FIELDS(ALL) to ensure all data is retrieved.

Why wrong: SELECT FIELDS(ALL) is restricted and generally inefficient for bulk Apex code.

SOQL supports traversing up to 10 levels of parent relationships.

Why wrong: Parent relationship traversal is limited to 5 levels.

Parent-to-child queries use dot notation on the parent object.

Why wrong: Dot notation is for child-to-parent traversal.

Child-to-parent queries require subqueries.

Why wrong: Child-to-parent queries use dot notation on the child object, not subqueries.

Trigger.old is available in insert triggers

Why wrong: Trigger.old is not available in insert.

Trigger.newMap is available in before insert

Why wrong: The ID is not yet assigned in before insert.

Trigger.new is available in delete triggers

Why wrong: Trigger.new is not available in delete.

Queue

Why wrong: Queue is not a generic collection type in Apex (Queueable is an asynchronous interface).

Table

Why wrong: Table is not a built-in collection type in Apex.

Catching a DmlException inside a try-catch block.

Why wrong: Catching an exception prevents rollback of preceding successful code unless manually triggered.

Executing Database.insert(records, false) with partial failure.

Why wrong: Using false allows successful records to commit without rolling back.

Hardcode record IDs in trigger logic to route specific test accounts.

Why wrong: Hardcoding IDs is an anti-pattern that breaks when deploying between sandbox and production environments.

Use synchronous callouts directly inside before insert triggers.

Why wrong: Synchronous callouts are prohibited inside triggers.

Place SOQL queries inside loops to ensure every record gets fresh data.

Why wrong: Putting SOQL queries inside loops quickly violates the 100 SOQL queries per transaction limit.

System mode ignores record-level sharing rules and user permissions entirely.

Why wrong: System mode ignores FLS and CRUD, but if 'with sharing' is present, sharing rules are still enforced.

Apex code automatically enforces sharing rules unless declared 'without sharing'.

Why wrong: Sharing rules are only enforced if 'with sharing' or 'inherited sharing' is specified on the class.

Profile permissions always override Apex system mode execution.

Why wrong: Profile permissions do not restrict code execution when running in system mode.

Profiles and Permission Sets

Why wrong: Profiles and Permission Sets manage user access and permissions.

Salesforce Sharing Rules

Why wrong: Sharing rules enforce security, not MVC architecture layers.

Governor Limits

Why wrong: Governor limits are resource constraints, not architectural layers.