Exam Certified Data Architect topic 1 question 12 discussion

The where clause alone is not performant when there are many records without description. having description field in the query output would not matter. A more deterministic search criteria and extraction in batches according to those criteria should help.

A will help with query plan investigation with indicies. C - description would not be enough to improve performance

The requirement is query ALL records that DON'T have a value in WhatID. Therefore it cannot be A and must C, that will improve reporting performance.

The question mentions that it should return all records that do NOT have a value in the WhatId field and the conditions that the architect wrote in the query will search for all records that the WhatId field is different from null. Therefore it is option A.

Shouldn’t it be D , Time-out error: A time-out error typically indicates that the query is taking too long to execute. This can happen when querying large datasets or performing complex calculations.Where conditions improve performance but doesn’t throw errors, right ?

Answer has to be C. Remember the purpose of the question. Wants ALL records that DON'T have a value in WhatID. D is wrong, because that limits the results to only 100 records, and there might be more. B is wrong, we need SOQL. A is wrong IN THIS case, because we already have a deterministic WHERE clause. We want records where WHATID is not null. C makes sense because if we want to increase performance, get rid of stuff we don't care about. The purpose of the query is to pull not null What IDs, so we don't care about the long text description.

Answer is A. See https://help.salesforce.com/s/articleView?id=000385213&type=1 to explain how to mitigate query limitation one must add "selective criteria" into the SOQL query. For example, "The performance of the SOQL query improves when two or more filters used in the WHERE clause meet the mentioned conditions."

Here are some examples of deterministic defined values that could be used to filter the query: A specific task ID The current date The ID of the current user By filtering the query to retrieve a smaller number of records, the data architect can significantly improve its performance and avoid timeout errors.

I think it is C. As we are looking for records that have WhatID as blank, I don't see how we can have a more "deterministic defined value" as a criteria. D option limits to 100 and therefore doesn't return everything either.

A. Change the WHERE clause to filter by a deterministic defined value: This is a good practice. The query should be selective, meaning one of the query filters is on an indexed field and the query filter reduces the resulting number of rows below a system-defined threshold

I think it is C, removing a long text field would make a query more performant and Description is not required for the request. Changing the filter to a deterministic value would mean it's not fetching all records where WhatId != null.

Only A is suitable! As D suggested from thneeb is not selective, because whatId is required field, therefore, there is no sense to check WhatID != null

I think that A is wrong. I would use D and limit the result and reexecute the query until the NULL values are solved.