Using the accept attribute in the tag allows specifying the allowed file types (MIME types) that users can upload. This provides client-side validation to ensure that only files of specified types are accepted. The File API, on the other hand, allows accessing file metadata, including size. Using typeof is not suitable for file type validation. The FileReader API is used to read file content, not metadata.

The correct option is ".dockerfile." Docker uses Dockerfiles, which are plain text configuration files with a specific syntax, to define the steps needed to create a container image. These files specify the base image, environment variables, dependencies, and commands to run when the container starts. Dockerfiles are essential for building reproducible and version-controlled containerized applications, making it easier to manage and scale container deployments.

Merge sort is preferable over quicksort when dealing with large input sizes due to its guaranteed O(n log n) time complexity, which is advantageous over quicksort's worst-case O(n^2) time complexity.

A singly linked list is best suited for implementing a stack because it only requires a pointer to the top element, allowing for efficient insertion and removal operations at the top of the stack.

WebSocket communication is crucial for real-time chat apps. Socket.IO provides a robust framework for WebSocket communication, including features like automatic reconnection, event handling, and room management, making it suitable for instant messaging applications in Node.js.

Option 2 suggests implementing an LRU (Least Recently Used) policy by moving recently accessed data to the front of the linked list. This approach optimizes cache performance by ensuring that frequently accessed data remains at the forefront, reducing access times and enabling efficient eviction of least used data when the cache is full. This strategy aligns with common cache management principles for improving access speed and overall system performance.

The correct option is "commit." A commit in Git represents a snapshot of the project's files at a specific moment in time. When you make changes to files and then commit those changes, Git records the changes and creates a new commit object. Commits are essential for tracking project history and collaborating with others in a version-controlled manner.

Git squashing is a technique used to combine multiple commits into a single commit. It's useful for creating cleaner commit histories and for preparing changes before merging them into a main branch or repository.

A process has its own address space in memory, which includes code, data, and resources allocated to that process. This separation ensures that processes can operate independently without interfering with each other's memory space. Threads, on the other hand, share the same address space within a process and can directly access shared data and resources. Understanding this distinction is fundamental in designing efficient and secure concurrent applications.

The Product Owner in Scrum is responsible for managing the product backlog, which includes prioritizing tasks and ensuring that the team understands the requirements and goals of each item in the backlog. The Scrum Master, on the other hand, focuses on facilitating the Scrum process and removing impediments.