Discuss Salesforce Plat-Arch-201 Exam Topic 3 Question 6

Universal Container (UC) has around 200,000 Customers (stored in Account object). They get 1 or 2 Orders every month from each Customer. Orders are stored in a custom object called "Order c"; this has about 50 fields. UC is expecting a growth of 10% year -over -year. What are two considerations an architect should consider to improve the performance of SOQL queries that retrieve data from the Order _c object? Choose 2 answers

AUse SOQL queries without WHERE conditions.

BWork with Salesforce Support to enable Skinny Tables.

CReduce the number of triggers on Order _c object.

DMake the queries more selective using indexed fields.

Suggested Answer: B, D

To improve the performance of SOQL queries that retrieve data from the Order_c object, the data architect should work with Salesforce Support to enable Skinny Tables and make the queries more selective using indexed fields. Skinny Tables are custom tables that contain frequently used fields and are kept in sync with the base tables3. They can improve performance by reducing the number of table joins and using indexes. Making the queries more selective using indexed fields can also improve performance by reducing the query execution time and avoiding query timeouts4. The other options are not effective or recommended for improving SOQL performance.

Get Premium Plat-Arch-201 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

24 comments · newest first

Irma 2 days ago

C could help, but triggers are important. Balance is key.

Davida 8 days ago

D makes sense too. Using indexed fields can speed things up.

Curtis 13 days ago

Agreed! A is definitely not the way to go. No WHERE conditions? That's risky.

Kirk 18 days ago

I think B is a solid choice. Skinny Tables can really boost performance.

Gerald 23 days ago

Definitely D! More selective queries mean better performance.

Anthony 28 days ago

I feel like B is a must. Skinny tables help with large data sets.

Ruthann 1 month ago

C is important too. Too many triggers can slow down performance.

Beatriz 1 month ago

A is a bad choice. Queries without WHERE conditions can be slow.

Joye 1 month ago

Agreed! D is crucial. Using indexed fields makes queries faster.

Lilli 2 months ago

I think B and D are the best options. Skinny tables can really speed things up.

Charlette 2 months ago

SOQL without WHERE? That's a no-go for performance!

Rusty 2 months ago

Reducing triggers is a good idea, but not always feasible.

Stephaine 2 months ago

Not sure about the skinny tables, are they really that effective?

Winfred 2 months ago

Definitely need to use indexed fields for better queries.

Socorro 2 months ago

Skinny Tables can really boost performance!

Kristofer 3 months ago

A is a no-go; you need those WHERE conditions for efficiency!

Pearline 3 months ago

Reducing triggers is also a good idea, but not the main focus here.

Dean 3 months ago

Wait, are skinny tables really that effective?

Lauran 3 months ago

I disagree with A, that's just asking for trouble.

Aaron 3 months ago

Definitely B and D! Skinny tables are a game changer.

Lenna 4 months ago

Reducing triggers might help, but I’m not convinced it directly impacts SOQL performance. I need to review that part again.

Rocco 4 months ago

I feel like using SOQL without WHERE conditions is definitely not a good idea. It would return too much data, right?

Garry 4 months ago

I'm not entirely sure, but I think enabling Skinny Tables could help with performance too. We talked about that in our last study group.

Rikki 5 months ago

I remember discussing the importance of using indexed fields to make queries more selective. That seems like a solid choice here.

Salesforce Plat-Arch-201 Exam - Topic 3 Question 6 Discussion