A design review covers customer-data protection and service continuity during a failure.
Select the two appropriate requirement-to-pillar mappings.
Which TWO mappings are appropriate?
Encryption and access controls map to Security; recovery and continuity map to Reliability.
Detailed explanation
Recovery and continuity are primarily Reliability concerns, not Sustainability-only concerns.
Recovery and continuity are primarily Reliability concerns, not Sustainability-only concerns.
Encryption primarily protects data and is not a Cost Optimization-only concern.
Encryption primarily protects data and is not a Cost Optimization-only concern.
Encryption is a protection control evaluated under the Security pillar.
Encryption is a protection control evaluated under the Security pillar.
Recovery, availability, and failure tolerance are Reliability concerns.
Recovery, availability, and failure tolerance are Reliability concerns.
Check official documentation
Compare the following points with the official documentation.
AWS Well-Architected Frameworkの6つの柱の定義を確認する。
What to confirm
データ保護をSecurity、復旧・継続をReliabilityへ対応付けられる。
Key points
- Security
- Reliability
- Design review
Notes
- Environment: AWS公式Well-Architected Frameworkの確認
- Verify current pillar definitions in the official AWS Well-Architected Framework documentation.
Foundation review
Different evaluation axes
Security, Reliability, Performance Efficiency, Cost Optimization, Operational Excellence, and Sustainability address different primary questions, even when one change affects several pillars.
Use the requirement
Map the stated outcome—protection, recovery, efficient resources, lower spending, effective operations, or lower environmental impact—to the corresponding pillar.