Salesforce Certified Platform Data Architect (Plat-Arch-201) Exam - Topic 4 Question 40 Discussion

Actual exam question for Salesforce's Salesforce Certified Platform Data Architect (Plat-Arch-201) exam

Question #: 40
Topic #: 4

[All Salesforce Certified Platform Data Architect (Plat-Arch-201) 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.)

AUsing leading % wildcards.

BUsing trailing % wildcards.

CPerforming large loads and deletions.

DUsing NOT and != operators.

EUsing a custom index on a deterministic formula field.

Show Suggested 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.

by Rima at Jun 28, 2024, 03:36 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified Platform Data Architect (Plat-Arch-201) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Jesus

5 months ago

Totally agree, leading % wildcards are a killer for performance!

upvoted 0 times

...

Benedict

5 months ago

Wait, using a custom index on a formula field? That sounds odd!

upvoted 0 times

...

Georgeanna

5 months ago

C is a big one too, those large loads mess things up.

upvoted 0 times

...

Vonda

5 months ago

I think B can also impact selectivity, right?

upvoted 0 times

...

Loreen

6 months ago

A and D definitely make queries non-selective.

upvoted 0 times

...

Twanna

6 months ago

I feel like performing large loads and deletions might not directly affect selectivity, but it could still be relevant in some way.

upvoted 0 times

...

Claudio

6 months ago

Trailing % wildcards could also be a problem, but I can't recall if they are as bad as leading ones.

upvoted 0 times

...

Clay

6 months ago

I remember practicing a question about NOT and != operators affecting selectivity. I think that might be one of the answers.

upvoted 0 times

...

Malcolm

6 months ago

I think using leading % wildcards definitely makes a query non-selective, but I'm not sure about the others.

upvoted 0 times

...

Armanda

6 months ago

A custom index on a formula field? I haven't heard of that before, I'll need to research that option.

upvoted 0 times

...

Tamesha

6 months ago

Performing large loads and deletions - that makes sense, those would impact query performance. I'll keep that in mind.

upvoted 0 times

...

Titus

6 months ago

Hmm, I'm a bit unsure about the difference between leading and trailing wildcards. I'll need to review that.

upvoted 0 times

...

Justine

6 months ago

This question seems straightforward. I'll focus on the key points about selective SOQL queries.

upvoted 0 times

...

Malinda

7 months ago

Using NOT and != operators can make a query non-selective? Good to know, I wouldn't have thought of that.

upvoted 0 times

...

Gail

7 months ago

Hmm, I'm a little unsure about this one. The question mentions "post-acute care for behavioral health disorders" but the answer choices don't seem to directly match that. I'll have to think this through carefully and try to identify the setting that best aligns with the information given.

upvoted 0 times

...

Therese

7 months ago

Ah, I remember learning about these in class. I'm pretty confident option C has the correct list of Cisco's converged infrastructure solutions.

upvoted 0 times

...

Stephen

7 months ago

Okay, I've got this. The answer is definitely option C - setting the workload profile within the server profile template and updating all the profiles. That way, I can configure it once and apply it across the entire fleet of servers.

upvoted 0 times

...

Pansy

11 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

11 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

Halina

10 months ago

E) Using a custom index on a deterministic formula field.

upvoted 0 times

...

Dana

10 months ago

C) Performing large loads and deletions.

upvoted 0 times

...

Edmond

11 months ago

A) Using leading % wildcards.

upvoted 0 times

...

Wilburn

11 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

10 months ago

E) Using a custom index on a deterministic formula field.

upvoted 0 times

...

Catarina

10 months ago

B) Using trailing % wildcards.

upvoted 0 times

...

Carmen

11 months ago

A) Using leading % wildcards.

upvoted 0 times

...

Gayla

12 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

10 months ago

E) Using a custom index on a deterministic formula field.

upvoted 0 times

...

Alesia

10 months ago

C) Performing large loads and deletions.

upvoted 0 times

...

Stephaine

11 months ago

A) Using leading % wildcards.

upvoted 0 times

...

Matthew

1 year 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