Free guides, interview Q&As, and job responsibility breakdowns — curated by industry veterans to help you crack MNC interviews
Figure 1: The NTFS Permission Ladder — Full Control down to Write
Figure 2: Local access uses NTFS only; network access combines Share + NTFS, and the most restrictive wins
File Server
Definition: A server that stores, manages, and shares files across a network so multiple users can access centralized data.
Day-to-Day Example: Like a company's central filing room where every department's documents are kept, instead of everyone keeping loose papers at their own desk.
Centralized File Storage
Definition: Storing organizational data in one managed server location rather than spread across individual computers.
Day-to-Day Example: Like a shared company warehouse where all inventory is tracked in one place, instead of each employee storing stock in their own garage.
Shared Folder
Definition: A folder made available over the network so authorized users can open, save, and modify its contents remotely.
Day-to-Day Example: Like a community bulletin board where anyone with the right access can post, read, or update notices.
Basic Sharing
Definition: A simple sharing method with quick setup and minimal permission options, suited to small environments.
Day-to-Day Example: Like handing someone a spare house key with no restrictions — quick and easy, but not very fine-tuned.
Advanced Sharing
Definition: A sharing method offering custom share names, detailed permission settings, and connection limits, suited to enterprise use.
Day-to-Day Example: Like a hotel key-card system where each card can be programmed for specific rooms, floors, and time windows.
Share Path
Definition: The network address (\\ServerName\FolderName) used to reach a shared folder from another computer.
Day-to-Day Example: Like a building's street address — it tells visitors exactly where to go to find the shared resource.
Hidden Share ($)
Definition: A shared folder whose name ends in $, which hides it from normal network browsing while still allowing direct access by path.
Day-to-Day Example: Like an unmarked staff-only door in a building — invisible on the directory, but still usable if you already know it's there.
NTFS Permissions
Definition: Security permissions on NTFS-formatted drives that control who can access files/folders and what actions they can perform, both locally and over the network.
Day-to-Day Example: Like the lock and access rules built into a specific filing cabinet itself, no matter which room the cabinet is moved to.
Full Control (NTFS)
Definition: The highest NTFS permission level, allowing reading, modifying, deleting, changing permissions, and taking ownership.
Day-to-Day Example: Like being the building owner — you can do absolutely anything, including changing who else has keys.
Modify (NTFS)
Definition: An NTFS permission allowing reading, writing, editing, and deleting content, but not changing permissions or ownership.
Day-to-Day Example: Like a tenant with full use of an apartment who still can't change the locks or hand out new keys.
Inheritance (NTFS)
Definition: The default behavior where permissions set on a parent folder automatically apply to its subfolders and files.
Day-to-Day Example: Like a company dress code that automatically applies to every department, unless one department is explicitly given an exception.
Share Permissions
Definition: Permissions applied to a shared folder that control access only when it's reached over the network.
Day-to-Day Example: Like a checkpoint guard at the entrance to a building — relevant only if you're coming from outside, not if you're already inside.
Change (Share Permission)
Definition: A share-level permission allowing users to read, create, modify, and delete files, but not change permissions or ownership.
Day-to-Day Example: Like a staff pass that lets someone rearrange and update stock on shelves, but not redesign the store's security system.
Effective Permission
Definition: The final access level a user actually receives after combining NTFS permissions, Share permissions, and group memberships.
Day-to-Day Example: Like the actual amount of light that gets through several stacked window blinds — determined by whichever blind blocks the most.
Principle of Least Privilege
Definition: A security principle stating that users should receive only the minimum permissions necessary to do their job.
Day-to-Day Example: Like giving a delivery driver access only to the loading dock, not a master key to the entire office building.
Role-Based Access Control (RBAC)
Definition: A method of assigning permissions according to a person's job role rather than configuring access individually for each user.
Day-to-Day Example: Like a uniform that automatically comes with certain access badges attached — wear the HR uniform, get HR-level access.
Security Group (File Server Context)
Definition: A group used to collectively assign and manage permissions for its members, rather than configuring each user separately.
Day-to-Day Example: Like a team jersey — everyone wearing it gets let into the same locker room, without needing an individual check each time.
Mapped Network Drive
Definition: A shared folder connected to a drive letter on a user's computer, so it behaves like a local drive.
Day-to-Day Example: Like giving a shared storage unit its own labeled parking spot right outside your house, so it feels as convenient as your own garage.
Disk Quota
Definition: A limit on how much storage space a specific user or group is allowed to consume on a server.
Day-to-Day Example: Like a data cap on a mobile plan — once you hit the limit, you can't keep piling on more without special arrangement.
Effective Permission Checking (Troubleshooting)
Definition: The process of determining a user's actual, final access level by reviewing NTFS permissions, Share permissions, and group memberships together.
Day-to-Day Example: Like an auditor tracing every approval stamp on a form to figure out why a request was ultimately approved or denied.
Figure 3: Recommended permission model — Users to Security Group to Permissions to Shared Folder
Figure 4: Step-by-step troubleshooting flow for "Access Denied" errors
1. File Server vs. Local Storage
Feature File Server (Centralized) Local Storage Access Available to authorized users network-wide Limited to the one computer Backup Centralized, easier to manage No centralized backup Security Controlled via permissions and groups Limited security management Data consistency Single shared copy Risk of duplicate/inconsistent copies
2. Basic Sharing vs. Advanced Sharing
Feature Basic Sharing Advanced Sharing Setup complexity Simple, quick More detailed configuration Permission control Simple permission settings Granular, custom permission control Best for Small offices, simple setups Enterprise environments
3. NTFS Permissions vs. Share Permissions
Feature NTFS Permissions Share Permissions Applies to Local and network access Network access only Granularity More detailed, advanced Simpler, fewer levels Levels available Full Control, Modify, Read & Execute, List Folder Contents, Read, Write Full Control, Change, Read Security strength Stronger, more precise Basic, broader control
4. Full Control vs. Modify (NTFS)
Feature Full Control Modify Read/Write/Delete Yes Yes Change permissions Yes No Take ownership Yes No Typical holder Administrators Regular editing users
5. Full Control vs. Change vs. Read (Share Permissions)
Aspect Full Control Change Read Read files Yes Yes Yes Create/modify/delete Yes Yes No Change permissions Yes No No Typical use Administrators Editing team members View-only users
6. User-Based Permissions vs. Group-Based Permissions
Feature User-Based Group-Based Scalability Poor in large environments Scales easily Administrative effort High — per-user changes Low — manage via membership Best practice? Generally avoided Recommended
7. Local Access vs. Network Access (Effective Permission)
Aspect Local Access Network Access Permissions that apply NTFS only Share + NTFS combined Effective result NTFS permission directly The more restrictive of the two Example NTFS: Modify -> Effective: Modify Share: Full Control, NTFS: Read -> Effective: Read
8. Principle of Least Privilege vs. RBAC
Concept Principle of Least Privilege Role-Based Access Control (RBAC) Focus Minimum necessary access per person Access tied to job role Implementation Careful, individual permission tuning Predefined role-based permission sets Relationship A guiding security principle A practical method that helps apply the principle
9. File Access Auditing vs. Disk Quota Management
Feature File Access Auditing Disk Quota Management Purpose Tracks who accessed/changed/deleted files Limits how much storage a user/group can use Helps with Security monitoring, investigations Preventing storage overuse Output Security logs / Event Viewer entries Enforced storage limits
10. Troubleshooting Tools Compared
Tool Purpose net use Views, connects, and disconnects mapped network shares whoami Shows the current logged-in user and their group memberships Event Viewer Logs file access failures, authentication issues, and security events
Q1. What is a File Server, and why do enterprises use one?
Answer: A File Server stores, manages, and shares files across a network from one central location, letting departments collaborate securely instead of storing data separately on individual computers.
Q2. What are the main benefits of centralized file storage over local storage?
Answer: Centralized storage improves file access, security, backup management, and collaboration, while reducing data duplication and the risk of loss from individual system failures.
Q3. What is the difference between Basic Sharing and Advanced Sharing?
Answer: Basic Sharing is a quick, simple method suited to small setups, while Advanced Sharing offers custom share names, detailed permission control, and connection management, making it better suited to enterprise environments.
Q4. What is a Share Path, and what format does it use?
Answer: A Share Path is the network address used to reach a shared folder, in the format \\ServerName\FolderName, allowing users across the network to access it.
Q5. What is a hidden share, and why would an organization use one?
Answer: A hidden share ends its name with a $ symbol and doesn't appear when browsing the network, though it's still reachable if the exact path is known — useful for administrative or sensitive shares that shouldn't be casually visible.
Q6. What are the main NTFS permission levels, from most to least powerful?
Answer: From most to least powerful: Full Control, Modify, Read & Execute, List Folder Contents, Read, and Write.
Q7. What is NTFS permission inheritance, and why is it useful?
Answer: Inheritance means permissions set on a parent folder automatically apply to its subfolders and files, which simplifies management and keeps security settings consistent, though it can be disabled where special permissions are needed.
Q8. Why do most organizations assign permissions to groups rather than individual users?
Answer: Group-based permissions scale far better — administrators configure access once on the group, and adding or removing a user from the group instantly changes their access, reducing administrative workload.
Q9. What is the difference between NTFS Permissions and Share Permissions?
Answer: NTFS Permissions apply both locally and over the network with detailed, granular control, while Share Permissions apply only over network access and offer just three simpler levels: Full Control, Change, and Read.
Q10. How is Effective Permission calculated when both Share and NTFS permissions are applied?
Answer: When accessing a resource over the network, the more restrictive of the Share permission and NTFS permission becomes the effective permission — for example, Share: Full Control with NTFS: Read results in an effective permission of Read.
Q11. What is the Principle of Least Privilege?
Answer: It's a security principle stating that users should be given only the minimum permissions necessary to perform their job, reducing security risk and limiting the impact of mistakes or malware.
Q12. What is Role-Based Access Control (RBAC), and why is it widely used?
Answer: RBAC assigns permissions based on job role (e.g., HR Staff, Finance Team) instead of configuring each user individually, making administration easier, more consistent, and more scalable.
Q13. What is disk quota management, and why is it important?
Answer: Disk quota management limits how much storage space a user or group can consume, which prevents excessive usage, protects server performance, and keeps storage usage fair and organized.
Q14. What causes most "Access Denied" errors on shared folders?
Answer: Common causes include incorrect NTFS permissions, incorrect Share permissions, missing or wrong security group membership, and inheritance-related permission problems.
Q15. What tools are commonly used to troubleshoot file access issues?
Answer: Administrators commonly use net use (to check/manage mapped shares), whoami (to verify user identity and group membership), and Event Viewer (to review access failures and security events).
Q1. A Finance folder needs to give Finance staff editing rights but everyone else only viewing rights. How should this be configured?
Answer: Assign Modify (NTFS) permission to the Finance security group for editing rights, and Read permission to other relevant users or groups so they can view but not change the files.
Q2. A department wants a folder that's reachable by direct path but shouldn't show up when employees browse the network.
Answer: Configure a Hidden Share by adding a $ to the end of the share name (e.g., \\FileServer\HR$), so it stays invisible to casual browsing but is still accessible to anyone who knows the exact path.
Q3. A user has Share permission of Full Control but NTFS permission of Read on the same folder, accessed over the network. What access do they actually get?
Answer: Their effective permission is Read, since when Share and NTFS permissions combine over network access, the more restrictive of the two always wins.
Q4. An employee complains they get "Access Denied" opening a shared folder they should have access to. How should this be troubleshot?
Answer: Check the NTFS permissions on the folder, check the Share permissions on the network share, verify the user's security group membership with whoami, and calculate the effective permission to find where access is being blocked.
Q5. A company wants every new HR hire to automatically get the same folder access as the rest of the HR team, with minimal admin effort.
Answer: Assign the required NTFS and Share permissions once to an HR security group, then simply add each new HR hire to that group so they automatically inherit the same access.
Q6. Managers should see more storage headroom than regular employees, and the server is starting to run low on space.
Answer: Implement Disk Quota Management, assigning a larger quota (e.g., 20 GB) to managers and a smaller quota (e.g., 5 GB) to regular employees to control overall storage usage.
Q7. A security review requires the company to know who accessed, modified, or deleted files in a sensitive folder over the past month.
Answer: Enable File Access Auditing on that folder so file access, modifications, deletions, and failed attempts are logged for review and investigation.
Q8. A user reports that a shared drive they normally use, mapped as drive F:, is suddenly unreachable. What should be checked first?
Answer: Check for network path issues — verify the server name, confirm DNS resolution is working, check general network connectivity, and use net use to confirm whether the mapped drive connection is still active.
