The key idea here is knowing the standard five-paragraph structure of an OPORD and what each section addresses. The five sections are Situation, Mission, Execution, Sustainment, and Command and Control. Situation sets the stage: it describes the operational environment, enemy and friendly forces, terrain, weather, and civil considerations that affect the plan. Mission states the task and purpose in a concise way, answering who will do what and why it matters. Execution provides the plan for how the mission will be accomplished—the concept of operations, the main effort, tasks to units, sequencing, and coordination details. Sustainment covers logistics and support—how supplies, transportation, maintenance, medical, and other support will be provided. Command and Control outlines how the operation will be commanded and controlled—the command relationships, communications plan, information requirements, and control measures needed to synchronize effort. Other formats that include a separate “Intent” paragraph or treat “Communications” or “Logistics” as standalone sections deviate from this standard five-paragraph structure.

The main idea being tested is OPSEC—the process of identifying critical information that, if exposed to adversaries, could jeopardize operations, and then applying measures to protect that information. In practice, this means spotting what details matter most to mission success (like sensitive routes, timings, or capabilities), analyzing who might seek them out and how they could be exposed, and then putting safeguards in place to prevent leakage. This approach is what keeps plans and intentions from becoming known to the enemy, reducing true risk. COMSEC focuses specifically on protecting communications and cryptographic material, not the broader set of operational details. INFOSEC covers information security in a general sense across all data and systems, which is related but broader than the operational emphasis of OPSEC. MDMP is the planning process used to develop and compare courses of action, not a security discipline.

Warfighting Function describes how military activities are organized as groups of tasks and the supporting systems that enable them, all linked by a common purpose to achieve missions and training objectives. This concept emphasizes how different tasks—like movement and maneuver, fires, intelligence, sustainment, protection, and mission command—are integrated so that people, equipment, and processes work together to create a coordinated effect on the battlefield or in training environments. It’s about how the force is structured to execute operations, not about a single unit performing a specialty, a doctrine document, or a metric. By organizing tasks and enabling systems under each function, commanders can plan, synchronize, and assess operations more effectively, ensuring all parts of the force contribute toward the same goals.

Information operations are governed by the Law of Armed Conflict. The best choice captures that IO must comply with LOAC and consciously limit harm to civilians while pursuing military objectives, applying the principles of necessity and proportionality and adhering to distinction and precautions in attack. This means IO activities must be conducted in a way that avoids civilian harm, only uses force or impact when necessary, and ensures any legitimate military objective is not outweighed by civilian or collateral damage. It also requires distinguishing between military targets and civilians and taking feasible steps to minimize harm. The other options miss essential LOAC obligations: aiming to maximize hits conflicts with LOAC protections; stating IO disregards civilian harm ignores civilian-protection rules; and claiming IO is exempt from LOAC denies that all armed actions must follow LOAC.