DAA-C01 Question 245
Single answerCreate and manage custom filtersA data analyst in Snowsight is building a worksheet to review order quality issues. The underlying query returns ORDER_ID, ORDER_DATE, REGION, STATUS, and DEFECT_COUNT. The analyst repeatedly needs to show only rows where STATUS is either 'RETURNED' or 'CANCELLED' and DEFECT_COUNT is greater than 0. They want to avoid rebuilding the same filter logic every time they revisit the worksheet and also want the filter to remain easy to reapply after sorting or changing visible columns. What is the best approach?
- A
Create a custom filter in the worksheet using the STATUS and DEFECT_COUNT conditions, save it, and reapply it when needed.
- B
Sort the worksheet by STATUS and DEFECT_COUNT, then save the worksheet so the relevant rows remain isolated.
- C
Hide rows that do not match the conditions and save the worksheet layout, because hidden rows function like reusable filters.
- D
Export the filtered result to a CSV file and re-upload it as a new table so the filtered subset can be queried later.
Show answer and explanation
Correct answer: A
Explanation
The best answer is to create and save a custom filter in Snowsight. Custom filters are designed to help analysts repeatedly apply the same row-level conditions to worksheet results without rebuilding them each time. This is especially useful for recurring investigative workflows, such as isolating problematic order statuses combined with threshold-based numeric conditions. Sorting, hiding, or exporting data may change presentation or create alternative artifacts, but they do not provide the maintainable, reusable filtering behavior requested in the scenario. As a best practice, analysts should use saved/custom filters for repeated interactive analysis and reserve creation of new tables or exported files for cases where a separate persisted dataset is actually required.
- A. Correct.
Correct. In Snowsight, custom filters are intended for exactly this use case: defining reusable filtering logic on worksheet results. A custom filter based on STATUS IN ('RETURNED','CANCELLED') and DEFECT_COUNT > 0 can be saved and reapplied later without manually reconstructing the conditions. This is more reliable than relying on visual changes such as sorting or column display changes.
- B. Incorrect.
Incorrect. Sorting changes only the order of rows; it does not restrict the dataset to matching records. Even if the desired rows appear together after sorting, all nonmatching rows are still present. This is a common misconception when users confuse data organization with data filtering.
- C. Incorrect.
Incorrect. Hiding rows is not the same as creating a reusable filter condition. In worksheet interfaces, hiding or changing display settings affects presentation, not the underlying filter logic in a durable, reusable way. If the analyst needs to consistently isolate rows based on conditions, a custom filter is the appropriate feature.
- D. Incorrect.
Incorrect. Exporting and re-uploading creates unnecessary data duplication, adds operational overhead, and breaks the intended workflow for interactive analysis. The problem is about managing reusable result-set filters in the worksheet, not materializing a separate physical dataset.