A dashboard must not receive data when the missing-value rate exceeds its threshold.
Minor violations should warn, while severe violations should block publication.
Which quality approach is most appropriate?
Define warning and blocking thresholds per rule and map quality states to publication, quarantine, and notification actions.
Detailed explanation
A minor optional-field issue can cause an unnecessary outage.
A minor optional-field issue can cause an unnecessary outage.
Degraded data can silently propagate to consumers.
Degraded data can silently propagate to consumers.
Operators can respond consistently according to impact and violation rate.
Operators can respond consistently according to impact and violation rate.
The quality signal and data completeness are hidden.
The quality signal and data completeness are hidden.
Check official documentation
Compare the following points with the official documentation.
AWS Glue Data Quality results、threshold、data pipeline quality gateの公式説明を確認する。
What to confirm
全無視・全停止と、重大度に応じた品質ゲートの違いを説明できる。
Key points
- Quality policy
- Warning/Block
- Threshold
- Publication decision
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Risk-based control
Give financial, contractual, and sensitive fields stricter treatment than optional attributes.
Accountability
Expose quality state, check time, and violation counts with the published dataset.