Service-Fit Recognition — AWS Solutions Architect (SAA-C03)
The right service fits without importing unused capability
A candidate sees "store files for a web application" and reaches for EFS because it sounds enterprise-grade. The scenario specifies static assets served over HTTP — S3 with a bucket policy and CloudFront is the correct fit. EFS is a shared file system for compute workloads requiring POSIX access, not a web content store. The exam repeatedly tests whether candidates can identify the minimal-fit service: the one whose primary capability matches the stated need without importing architecture the scenario does not require.
What This Pattern Tests
The exam tests whether you match a specific requirement to the most appropriate service even when a more powerful service could technically handle it. DynamoDB excels at single-digit millisecond key-value access at any scale but cannot do joins. Aurora excels at complex relational queries with up to 128TB storage but has provisioning overhead. ElastiCache Redis provides microsecond reads but data is volatile. The exam gives a specific access pattern and tests whether you pick the service that fits rather than the service that can do the most.
Decision Axis
Requirement precision vs. service capability. The best fit is the simplest service that fully meets the access pattern.
Associated Traps
More Top Traps on This Exam
Decision Rules
When a Linux workload requires shared NFS-compatible file storage, select Amazon EFS; disqualify Amazon FSx for Windows File Server on protocol incompatibility (SMB/Windows-only) before applying any cost comparison.
Given explicit Linux/NFS semantics and no Windows or hybrid dependency, does the team select Amazon EFS (purpose-fit, cost-effective Bursting mode) over Amazon FSx for Windows File Server (scope overreach: SMB-only protocol incompatible with Linux NFS) or Amazon S3 (no filesystem mount semantics)?
Does the workload require shared filesystem semantics — NFS mounts, POSIX permissions, or concurrent multi-instance file access — or only sequential object-level reads and writes? If no filesystem protocol is stated, S3 dominates on cost and fit; EFS is near-right but imposes shared-filesystem infrastructure the workload does not need.
Domain Coverage
Difficulty Breakdown