**S3**: Object storage. Key-value; eventual consistency (strong for new overwrites). No filesystem. Use for data lake, backup, static assets. Cheaper at scale ($0.023/GB). **EFS**: File system (NFS). Shared across EC2/ECS/Lambda. Use when apps need POSIX, shared storage, or random write. **Trade-off**: EFS is more expensive; S3 is cheaper and scales infinitely. EFS when you need mount point, multi-writer, or legacy app compatibility. **Use S3**: Data lakes, ETL outputs, backups....
The complete answer continues with detailed implementation patterns, architectural trade-offs, and production-grade considerations. It covers performance optimization strategies, common pitfalls to avoid, and real-world examples from companies like Wipro. The answer also includes follow-up discussion points that interviewers commonly explore.
Continue Reading the Full Answer
Unlock the complete expert answer with code examples, trade-offs, and pro tips - plus 1,863+ more.
Or upgrade to Platform Pro - $39
Engineers who used these answers got offers at
AmazonDatabricksSnowflakeGoogleMeta
According to DataEngPrep.tech, this is one of the most frequently asked Cloud/Tools interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.