Automating Amazon Redshift Materialized View Refresh
A company uses Amazon Redshift for its data warehouse. The company must automate refresh schedules for Amazon Redshift materialized views. Which solution will meet this requirement with the LEAST effort?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests knowledge of automated maintenance for Redshift objects, specifically highlighting that native auto-refresh or simple scheduling is less complex than external orchestration tools.
Learn how to automate Amazon Redshift materialized view refresh schedules with the least effort using built-in features or Query Editor v2.
Many candidates choose AWS Lambda (B) or Apache Airflow (A), over-engineering the solution by adding custom code and infrastructure management when native capabilities exist.
Community Discussion (11 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option C is correct because Amazon Redshift provides two primary mechanisms to handle this requirement with minimal effort: Native Auto-Refresh and Query Scheduler in Query Editor v2. The most efficient method is configuringAUTO REFRESH during the creation of the materialized view, which requires zero operational overhead after setup. Alternatively, if a specific schedule is needed rather than event-driven refreshes, Query Editor v2 allows users to schedule SQL queries directly without managing external services. Both approaches leverage built-in Redshift functionality, satisfying the 'LEAST effort' constraint.Why the Other Options Are Wrong
Options A (Apache Airflow) and D (AWS Glue) introduce significant complexity by requiring the setup, configuration, and maintenance of external orchestration workflows. Option B (AWS Lambda UDF) is technically incorrect and overly complex; Lambda functions are not designed to trigger internal database metadata operations like refreshing views, and implementing such a pattern would require extensive custom coding and permission management, violating the least-effort principle.Community Comment Notes
Community consensus strongly supports Option C, citing the availability of native auto-refresh features as well as the query scheduler in Query Editor v2. As user magnorm noted, "https://docs.aws.amazon.com/redshift/latest/mgmt/query-editor-v2-schedule-query.html" confirms the scheduling capability. Users like Christina666 pointed out that auto-refresh can be set during creation, while others like confusedyeti69 correctly identified that Lambda and orchestration tools add unnecessary overhead compared to native solutions.Official Reference
Exam Strategy
When asked for the 'least effort' or 'simplest' solution, always prioritize managed, native service features over building custom integrations with Lambda, Glue, or third-party tools unless those features do not exist.
Frequently Asked Questions
Is Native Auto-Refresh better than Query Editor v2?
Native Auto-Refresh is generally preferred as it is event-driven and requires no ongoing management, but Query Editor v2 is also a valid low-effort option for scheduled refreshes.
Can I use Lambda to refresh Redshift views?
While possible via API calls, it is not the least effort solution and introduces unnecessary complexity compared to native Redshift capabilities.
Related Analysis
Practice All DEA-C01 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DEA-C01 Practice Test →