Elastic File System (EFS) for EC2 Basics Quiz Quiz

Assess your understanding of Elastic File System (EFS) concepts, features, and usage for EC2 environments. This quiz is designed to help learners evaluate their knowledge of cloud file storage, configuration, and best practices for scalable workloads.

  1. EFS Mounting Points

    Which protocol is primarily used by Elastic File System (EFS) for mounting on EC2 instances?

    1. HTTP
    2. SMB
    3. NFS
    4. FTP

    Explanation: EFS uses the Network File System (NFS) protocol for mounting and accessing files from EC2 instances, allowing multiple clients to access the same file system. SMB and FTP are commonly used for different types of network file access but are not supported by EFS. HTTP is not a file mounting protocol, and it does not enable file system mounting for EC2 instances.

  2. EFS Storage Growth

    How does EFS handle increases in file storage usage?

    1. Automatically scales storage
    2. Requires manual resizing
    3. Needs scheduled upgrades
    4. Uses fixed storage pools

    Explanation: EFS automatically scales file storage up or down as needed without user intervention, ensuring scalability for changing workloads. Manual resizing and scheduled upgrades are not needed because the system scales seamlessly. Fixed storage pools limit flexibility and do not reflect how EFS works.

  3. Data Accessibility

    What type of data access does EFS provide to EC2 instances within a region?

    1. Shared, concurrent access
    2. Read-only, global access
    3. Time-limited temporary access
    4. Exclusive, single-instance access

    Explanation: EFS allows multiple EC2 instances to access and modify files simultaneously, making it ideal for shared data environments. Exclusive access prevents sharing across instances and is not how EFS works. EFS supports both read and write actions, not just read-only access, and its access is persistent rather than time-limited.

  4. EFS Use Case

    Which scenario is best suited for using EFS with EC2 instances?

    1. Backing up data to offline tape storage
    2. Downloading software updates
    3. Storing a single database for exclusive instance use
    4. Hosting shared application files across multiple instances

    Explanation: EFS is optimized for use cases where shared access to files is necessary, such as serving the same application files to several instances. It is not intended for exclusive storage typically used for databases, nor is it designed for offline backup methods like tape storage. Software updates do not require shared persistent file systems.

  5. EFS Security

    Which method can control access to files stored on EFS?

    1. Security groups and NFS permissions
    2. Diffie-Hellman encryption
    3. FTP user passwords
    4. Firewall MAC address filtering

    Explanation: Access to files in EFS can be managed by configuring security groups for network access and using NFS permissions for file-level control. FTP passwords and MAC address filtering are not standard mechanisms for securing this type of file system. Diffie-Hellman is a cryptographic protocol, not an access control mechanism.

  6. EFS Performance Modes

    Which performance mode should be selected for workloads with high levels of parallel access?

    1. Single Thread
    2. Synchronous Mode
    3. Standard I/O
    4. Max I/O

    Explanation: The Max I/O performance mode is designed for environments needing the highest levels of parallel access and throughput. Standard I/O suits most general workloads but may not perform optimally for high concurrency. Single Thread and Synchronous Mode are not available performance modes in EFS.

  7. EFS Lifecycle Management

    What is the purpose of EFS lifecycle management?

    1. Encrypts files at rest
    2. Automatically moves files to lower-cost storage classes
    3. Limits the number of users accessing files
    4. Deletes files after 30 days

    Explanation: Lifecycle management in EFS automates the movement of infrequently accessed files to more cost-effective storage, reducing expenses without manual intervention. It does not delete files simply after a duration, perform encryption, or restrict user numbers.

  8. EFS Availability Zones

    Why is it recommended to deploy EFS mount targets in multiple availability zones?

    1. To ensure high availability and fault tolerance
    2. To increase storage capacity limits
    3. To restrict storage access to a single zone
    4. To prevent billing for multiple zones

    Explanation: Deploying mount targets across multiple availability zones provides resilience and continuous access in case of failure in one zone. Restricting access or preventing billing does not improve fault tolerance. Storage capacity is independent of mount target distribution.

  9. EFS Data Encryption

    Which type of encryption is supported by EFS to protect sensitive data?

    1. Only hashing at rest
    2. Hardware-based self-encryption
    3. Encryption at rest and in transit
    4. Only encryption in transit

    Explanation: EFS supports encrypting data both at rest and during transfer, enhancing the security of sensitive information. Encryption only in transit or only at rest provides partial protection, while hashing at rest is not the same as full encryption. Hardware-based self-encryption is not a specific feature in this context.

  10. EFS Billing Model

    How is EFS usage billed to users?

    1. According to CPU and memory usage on EC2
    2. Based on the amount of storage used
    3. By the number of EC2 instances connected
    4. At a flat monthly rate regardless of usage

    Explanation: EFS charges are determined by how much file storage a user consumes, making it scalable and cost-efficient. The number of connected EC2 instances and their compute usage are not part of EFS's billing model. There is no fixed monthly rate that ignores usage, as costs depend on actual storage.