Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

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

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
B) Work with Salesforce Support to enable Skinny Tables. and D) Make the queries more selective using indexed fields.
A) Use SOQL queries without WHERE conditions.
C) Reduce the number of triggers on Order _c object.

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

Actual exam question for Salesforce's Plat-Arch-201 exam
Question #: 6
Topic #: 3
[All Plat-Arch-201 Questions]

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

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


Contribute your Thoughts:

0/2000 characters
Lilli
3 days ago
I think B and D are the best options. Skinny tables can really speed things up.
upvoted 0 times
...
Charlette
8 days ago
SOQL without WHERE? That's a no-go for performance!
upvoted 0 times
...
Rusty
13 days ago
Reducing triggers is a good idea, but not always feasible.
upvoted 0 times
...
Stephaine
18 days ago
Not sure about the skinny tables, are they really that effective?
upvoted 0 times
...
Winfred
23 days ago
Definitely need to use indexed fields for better queries.
upvoted 0 times
...
Socorro
29 days ago
Skinny Tables can really boost performance!
upvoted 0 times
...
Kristofer
1 month ago
A is a no-go; you need those WHERE conditions for efficiency!
upvoted 0 times
...
Pearline
1 month ago
Reducing triggers is also a good idea, but not the main focus here.
upvoted 0 times
...
Dean
1 month ago
Wait, are skinny tables really that effective?
upvoted 0 times
...
Lauran
2 months ago
I disagree with A, that's just asking for trouble.
upvoted 0 times
...
Aaron
2 months ago
Definitely B and D! Skinny tables are a game changer.
upvoted 0 times
...
Lenna
2 months ago
Reducing triggers might help, but I’m not convinced it directly impacts SOQL performance. I need to review that part again.
upvoted 0 times
...
Rocco
2 months ago
I feel like using SOQL without WHERE conditions is definitely not a good idea. It would return too much data, right?
upvoted 0 times
...
Garry
2 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.
upvoted 0 times
...
Rikki
4 months ago
I remember discussing the importance of using indexed fields to make queries more selective. That seems like a solid choice here.
upvoted 0 times
...

Save Cancel