How to Prevent SMB Direct Connections in Windows Server?
You have a server that runs Windows Server. You need to prevent the creation of SMB Direct connections. Which cmdlet should you run?
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
This question tests your understanding of Windows Server feature management architecture, trapping candidates who confuse optional feature toggles with standard role removal or NIC binding configurations.
Disabling SMB Direct in Windows Server requires managing its status as an optional OS feature rather than a network binding or server role. The community unanimously confirms that the Disable-WindowsOptionalFeature cmdlet is the precise tool for this operation.
Candidates frequently choose Disable-NetAdapterBinding because it intuitively sounds like it would stop network protocols, but it only manages legacy or standard adapter bindings and cannot control the SMB Direct optional feature.
Community Discussion (5 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
SMB Direct is deployed as a Windows Optional Feature, meaning its lifecycle is managed through the Windows Optional Features API rather than traditional role installation. RunningDisable-WindowsOptionalFeature -Online -FeatureName SMBDirect cleanly deactivates the underlying RDMA-based networking stack without removing other components. This approach aligns with Microsoft's modern Windows Server configuration model.Why the Other Options Are Wrong
Remove-WindowsFeature permanently uninstalls roles or features, which is destructive and unnecessary for simply disabling SMB Direct. Set-NetAdapterAdvancedProperty modifies hardware or driver-level NIC settings but does not interact with the OS-level SMB protocol stack. Disable-NetAdapterBinding targets specific network adapter bindings like QoS or IPv6, but SMB Direct bypasses this mechanism by operating as a standalone optional feature.Community Comment Notes
The discussion overwhelmingly supports option A, with multiple users providing the exact PowerShell syntax required for implementation. Comments [4] and [5] directly reference the official Microsoft Learn documentation, confirming the-FeatureName SMBDirect parameter. The 100% vote distribution demonstrates strong community alignment on this specific cmdlet usage. Official Reference
Exam Strategy
Always verify whether a Windows Server component is classified as a Role, a Feature, or an Optional Feature before selecting a management cmdlet. Use Get-WindowsOptionalFeature to quickly identify the exact naming convention required for targeted enable or disable operations.