CERTIFIED-DATA-ANALYST-ASSOCIATE Question #39: Real Exam Question with Answer & Explanation

Question

A data analyst has been asked to configure an alert for a query that returns the income in the accounts_receivable table for a date range. The date range is configurable using a Date query parameter. The Alert does not work. Which of the following describes why the Alert does not work?

Options

• AAlerts don't work with queries that access tables.
• BQueries that return results based on dates cannot be used with Alerts.
• CThe wrong query parameter is being used. Alerts only work with Date and Time query
• DQueries that use query parameters cannot be used with Alerts.
• EThe wrong query parameter is being used. Alerts only work with drogdown list query parameters,

Explanation

Option D is correct because most analytics platforms (such as Redash) do not support Alerts on parameterized queries - when the alert scheduler runs a query automatically, it has no mechanism to supply dynamic parameter values, so the query cannot execute as intended.

Why the distractors fail:

• A is wrong - Alerts work perfectly fine with queries that access database tables; the table is not the problem.
• B is wrong - date-based logic in queries is supported by Alerts, as long as those dates are hardcoded or derived dynamically (e.g., NOW()), not passed as a query parameter.
• C is wrong - the parameter type (Date vs. Date and Time) is irrelevant; no query parameter type is compatible with Alerts.
• E is wrong - Alerts do not work with any query parameter, not just non-dropdown ones; the restriction is on parameters themselves, not their input type.

Memory tip: Think "Alerts need static queries" - if a query requires user input at runtime (a parameter), an automated alert scheduler has no user to ask, so it simply won't run.

No community discussion yet for this question.