Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Data Architect Topic 4 Question 40 Discussion

Actual exam question for Salesforce's Data Architect exam
Question #: 40
Topic #: 4
[All Data Architect Questions]

Universal Containers has a custom object with millions of rows of data.

When executing SOQL queries, which three options prevent a query from being selective? (Choose three.)

Show Suggested Answer Hide Answer
Suggested Answer: B

Creating validation rules to check if the required attributes are entered is the best option to mandate this when customers are created in Salesforce. Validation rules allow you to specify criteria that must be met before a record can be saved. You can use validation rules to ensure that customers have a first name, last name, and email when they are created in Salesforce. This way, you can prevent incomplete or invalid data from being sent to your MDM solution.


Contribute your Thoughts:

Pansy
1 months ago
Wait, millions of rows? That's just a warm-up for me. I can query that dataset with my eyes closed and one hand tied behind my back. Now, where's the option for 'use your Jedi mind tricks to make the database return only the rows you need'?
upvoted 0 times
...
Hillary
1 months ago
This is a great question. It really makes you think about the different ways you can inadvertently write a non-selective query. Time to brush up on my SOQL best practices!
upvoted 0 times
Dana
14 days ago
C) Performing large loads and deletions.
upvoted 0 times
...
Edmond
20 days ago
A) Using leading % wildcards.
upvoted 0 times
...
...
Wilburn
1 months ago
Haha, the 'large loads and deletions' option is a classic red herring. Imagine trying to run a SOQL query while the data is constantly changing - what a nightmare!
upvoted 0 times
Chandra
6 days ago
E) Using a custom index on a deterministic formula field.
upvoted 0 times
...
Catarina
14 days ago
B) Using trailing % wildcards.
upvoted 0 times
...
Carmen
15 days ago
A) Using leading % wildcards.
upvoted 0 times
...
...
Gayla
2 months ago
I was tempted to choose E, but you're right - a custom index should actually help with performance. I guess that's a trick question to see if we really know our stuff.
upvoted 0 times
Dorsey
8 days ago
E) Using a custom index on a deterministic formula field.
upvoted 0 times
...
Alesia
10 days ago
C) Performing large loads and deletions.
upvoted 0 times
...
Stephaine
1 months ago
A) Using leading % wildcards.
upvoted 0 times
...
...
Matthew
2 months ago
A, B, and D are the correct answers. Wildcards and inequality operators can really slow down a query, especially on a large dataset. I'm glad they're testing our understanding of selective SOQL queries.
upvoted 0 times
Andra
7 days ago
I'm glad they're testing our understanding of selective SOQL queries.
upvoted 0 times
...
Lenita
11 days ago
Especially on a large dataset.
upvoted 0 times
...
Kirk
19 days ago
Wildcards and inequality operators can really slow down a query.
upvoted 0 times
...
Precious
1 months ago
I think A, B, and D are the correct answers.
upvoted 0 times
...
...
Lashaunda
3 months ago
I believe using a custom index on a deterministic formula field can actually help make the query more selective.
upvoted 0 times
...
Ahmed
3 months ago
I agree with Lanie. Using trailing % wildcards and performing large loads and deletions also make the query non-selective.
upvoted 0 times
...
Lanie
3 months ago
I think using leading % wildcards prevents a query from being selective.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77