Free Cisco 200-201 Actual Exam Questions - Question 10 Discussion

Not B, using web apps doesn't prevent buffer overflows at all. Variable randomization (A) helps but mainly makes exploitation harder, so C really fits best since it stops bad input from causing overflow.

Makes sense to rule out B and D since web apps and OS choice alone don’t stop overflows. C seems solid because cleaning inputs directly stops buffer overflow attempts at the source. That’s my pick: C.

Maybe A here. Variable randomization, like ASLR (Address Space Layout Randomization), makes it harder for attackers to predict memory locations, which helps prevent successful buffer overflow exploits by messing with their ability to jump to the right places. Input sanitization (C) is good but more about stopping bad input itself; if some input still slips through, randomization adds a layer of defense. Options B and D don’t really prevent buffer overflows directly. So, A is a solid choice if you think about preventing the attack from working rather than just filtering inputs.

C stops bad data before it causes overflow, so definitely prevention.

C, input sanitization directly stops bad data causing overflow.

I’m thinking C makes the most sense since buffer overflow is caused by too much or unexpected input data. Sanitizing input is directly aimed at preventing that by validating and limiting what gets through. A and D are more like additional layers of defense or mitigation rather than prevention. B doesn’t really relate at all. Does anyone have thoughts on whether sanitization alone is usually enough, or if it needs to be combined with other methods?

Probably A here. Variable randomization like ASLR doesn’t stop buffer overflows themselves but makes it way harder for attackers to predict memory locations and exploit them.

A/D? Variable randomization like ASLR (address space layout randomization) helps make buffer overflow exploits harder by randomizing memory locations. Using Linux can add some built-in protections too. Input sanitization is important but might not fully stop overflows if the code still mishandles buffer sizes. So I see A and D as preventative steps from a system perspective, while C handles the input side but may not be enough alone.

C imo, because buffer overflow happens when too much data is put into a buffer. Sanitizing input helps make sure data fits safely, unlike options A, B, or D that don’t directly stop overflows.

Option C, but does it mean all inputs or specific types?