Working with Data →mediumMultiple SelectObjective-mapped

SNOW-CAD Working with Data Practice Question

Which TWO GlideRecord methods can be used to create OR conditions in a query? (Choose two.)

⚠ Common exam trap

Many candidates confuse `addOrCondition()` with a non-existent `ORQuery()` method, or assume that `addQuery()` can be chained with `addOrCondition()` as a single fluent call, which is syntactically incorrect in ServiceNow.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

GlideRecord.addEncodedQuery()

B is correct because `GlideRecord.addEncodedQuery()` allows you to pass an encoded query string that can include OR conditions using the `^OR` operator. This method is a direct way to construct complex queries with OR logic without chaining multiple method calls. D is correct because `GlideRecord.addOrCondition()` explicitly adds an OR condition to the current query, typically used after an initial `addQuery()` call.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
GlideRecord.ORQuery()
Why it's wrong here
ORQuery() is not a valid method in GlideRecord.
✓
GlideRecord.addEncodedQuery()
Why this is correct
addEncodedQuery() can include OR operators in the encoded query string, thus creating OR conditions.
✗
Using addQuery().addOrCondition() pattern
Why it's wrong here
This is a pattern, not a single method; addQuery() itself adds an AND condition.
✓
GlideRecord.addOrCondition()
Why this is correct
addOrCondition() explicitly adds an OR condition to the query.
✗
GlideRecord.addQuery()
Why it's wrong here
addQuery() adds an AND condition, not OR.

Go deeper

SNOW-CAD Working with Data Practice Question

Why each option matters

Option-by-option breakdown

Related to this question