Given the command shown below: Brocade 150-420 Exam ServerIronADX 1000(debug-filter-MP)#packet 128 What is the result?

Yusuf A.Oct 17, 2025

The correct answer is D, packet length is set to 128 bytes. On a ServerIronADX the "packet" command inside the debug-filter-MP context controls how many bytes of each captured packet are included in the debug output, not a memory buffer size, so options A and C are off the mark entirely. A senior tech I work with described it like a "snapshot window," where you tell the device how far into the packet to look before it stops capturing, and 128 here is that byte depth. The "MB" options in A and C are a trap for people mixing this up with buffer memory commands that show up elsewhere in the CLI.

Anjali D.Jun 27, 2026

The answer is D, packet length set to 128 bytes. In the ServerIronADX debug filter context, the "packet" command specifies the maximum packet length to capture or filter on, and the value is always interpreted in bytes, not megabytes, so 128 means 128 bytes. Anyone who picked A or C, watch out for the MB trap, the ADX debug filter does not use megabyte units for packet parameters. Does this match what others in the group are seeing in their study materials?

Hiroshi T.Oct 9, 2025

Honestly I first went with B thinking bytes was the logical unit for a buffer size parameter, but the ServerIron ADX documentation makes clear that the packet command in the debug-filter context sets the maximum packet length to capture, not a buffer allocation, and 128 there refers to 128 bytes of packet length, which lands you at D for the right reason, not just the right unit.

Mei-Ling H.Nov 10, 2025

The two things you have to separate here are "buffer size" and "packet length," because A and B use "buffer size" while C and D use "packet length," and those are not the same thing in debug-filter context. The packet command in debug-filter-MP mode controls the length of the captured packet, not the size of a buffer, so that already cuts A and B. Then look at the unit, because 128 with no label in a packet-capture context on this platform is bytes, not megabytes, which points you to D over C. My clarifying question is this: does the packet length value here act as a maximum capture length per packet, meaning packets shorter than 128 bytes get captured in full and only longer ones get truncated at 128, or does the device drop anything outside that length entirely? I have seen conflicting explanations on this and I want to make sure I understand the behavior before the exam, not just the command syntax.

Bao N.Jun 27, 2026

D is right, but do you know why 128 here means bytes and not MB?

Dervla O.Nov 5, 2025

D is right, packet sets the capture length in bytes, not a buffer size.

Nina C.Jun 18, 2026

I almost picked B because 128 bytes sounds right and I conflated "buffer size" with "packet length" for a second, but the packet command in debug-filter-MP sets the capture length, not a buffer allocation, so D is correct.

Mateus R.Nov 1, 2025

Think of a debug filter like a security guard at a building entrance who is told to only stop and inspect people shorter than a certain height. The "packet" keyword in that command is telling the guard what measurement to care about, and the number after it is the cutoff. On the ServerIronADX, the "packet" subcommand under a debug filter sets the maximum packet LENGTH in bytes that the filter will capture, so typing "packet 128" means only packets up to 128 bytes long get flagged for inspection, making D the right call. The answer is not about buffer memory size at all, so A and C are leading you down the wrong road entirely. Here is my question for you: do you know what happens to packets that are LONGER than the value you set here, meaning does the device still process them normally or does it drop them outright? That distinction matters a lot if you are trying to troubleshoot a specific traffic type and you set your filter threshold too low.

Goran A.Jun 27, 2026

Thought B, but "length" not "buffer" sealed it for me.