← Salesforce theorytheory 0/4 · 0%

level 1

Curious · 0 XP

streak

perfect

badges

100 XP to Apprentice

Apex · medium

2. Bulkification & Apex Triggers

Writing triggers that handle batches of up to 200 records.

1 min read2 questionsup to 50 XPtopic 2/4

Read in another language

AI translates the explanation and quiz text while preserving code and answer scoring.

Apex triggers execute before or after insert, update, delete, or undelete operations. Code must always be 'bulkified' to iterate over collections in `Trigger.new` rather than processing single records, and SOQL/DML must NEVER be executed inside loops.

apex
trigger AccountTrigger on Account (before insert, before update) {
    for (Account acc : Trigger.new) {
        if (acc.BillingCountry == null) {
            acc.BillingCountry = 'USA';
        }
    }
}

How to study this topic

1. Read the explanation once end to end, skipping the code.
2. Re-read the code snippets and say out loud what each line does.
3. Answer the quiz without scrolling back — that is the real check.
4. Read every explanation, even for the answers you got right.

Scoring

· Up to 30 XP from quiz accuracy.
· +15 XP for a perfect first attempt.
· +5 XP while a 3-day streak is running.
· 75% or higher marks the topic complete.

Check your understanding

1. Why must Apex triggers be written to handle bulk collections (Trigger.new) instead of single records?
DML operations and bulk API calls execute triggers in batches of up to 200 records at onceApex does not support single recordsTo avoid compiler errorsTo bypass tests
2. What critical rule must be followed when writing SOQL queries or DML statements in Apex?
Never place SOQL or DML statements inside 'for' or 'while' loopsAlways query inside loopsUse raw SQL stringsDisable triggers in production

Badges

First light

Pass your first topic

Sharp shooter

3 perfect first-try quizzes

On a roll

Study 3 days in a row

Week warrior

Study 7 days in a row

Grinder

Earn 500 XP

Deep diver

Earn 1500 XP