What is a core architectural difference between the traditional Windows Command Prompt (cmd.exe) and Windows PowerShell?
Difficulty: Medium
About this MCQ
This Medium Windows 10/11 Mcqs question asks: What is a core architectural difference between the traditional Windows Command Prompt (cmd.exe) and Windows PowerShell? The correct choice is D. PowerShell passes .NET objects between commands, whereas Command Prompt passes unstructured text strings.. Read the options below, commit to one, then use the explanation to see why that choice holds and why the others do not.
Windows 10/11 Mcqs items like this one are written for Pakistan exams such as CSS, FPSC, PPSC, and NTS. The difficulty label is a hint about how much of the topic the stem assumes, not a score. Tags and exam names, when they are present, tell you where else the same idea is tested. Previous and next links stay in Windows 10/11 Mcqs so you can continue the subject. Related questions point at nearby stems if you want another angle on the same idea.
Treat the explanation as part of the question, not a footnote. If you missed it, reread the stem against the correct option before you open the next Windows 10/11 Mcqs item. A timed quiz is the same pool with a clock and a score. A past paper is a full sitting rather than this single question.
- A. PowerShell only functions on Linux kernels, while Command Prompt runs exclusively on Windows.
Why not A: “PowerShell only functions on Linux kernels, while Command Prompt runs exclusively on Windows.” does not fit this question. The answer is PowerShell passes .NET objects between commands, whereas Command Prompt passes unstructured text strings..
- B. Command Prompt utilizes .NET objects, whereas PowerShell relies entirely on raw text string manipulation.
Why not B: “Command Prompt utilizes .NET objects, whereas PowerShell relies entirely on raw text string manipulation.” does not fit this question. The answer is PowerShell passes .NET objects between commands, whereas Command Prompt passes unstructured text strings..
- C. PowerShell cannot execute batch files or legacy system binaries.
Why not C: “PowerShell cannot execute batch files or legacy system binaries.” does not fit this question. The answer is PowerShell passes .NET objects between commands, whereas Command Prompt passes unstructured text strings..
- D. PowerShell passes .NET objects between commands, whereas Command Prompt passes unstructured text strings. ✓
Correct answer
D. PowerShell passes .NET objects between commands, whereas Command Prompt passes unstructured text strings.
Explanation
PowerShell passes NET objects between commands whereas Command Prompt passes unstructured text strings is the value that answers What is a core architectural difference between the traditional Windows Command Prompt cmd exe and Windows PowerShell option D Option A PowerShell only functions on Linux kernels while Command Prompt runs exclusively on Windows does not fit this question Option B Command Prompt utilizes NET objects whereas PowerShell relies entirely on raw text string manipulation does not fit this question Option C PowerShell cannot execute batch files or legacy system binaries does not fit this question For this Windows Mcqs question the accepted answer is PowerShell passes NET objects between commands whereas.
Source: Original practice question, MCQsHub
Tags: powershell, command prompt, windows scripting
Submitted by: MCQsHub Editorial
Related MCQs
- Which specific executable command-line tool is used in Windows Command Prompt to launch Windows Defender comma...
- Which specific tab in the modern Windows 10/11 Task Manager allows administrators to inspect programs configur...
- When a BitLocker-encrypted drive goes into recovery mode on Windows 10/11 because of a hardware or firmware ch...
- An engineer types ncpa.cpl into the Run command window. What network configuration window will open?
- If an IT administrator inputs appwiz.cpl in the Run line, which traditional graphical control panel interface...
- What is the standard naming syntax convention used for PowerShell cmdlets?