Software engineers know that a poorly written application can consume

Question

Software engineers know that a poorly written application can consume more memory than it should and that running out of memory can cause an application to crash. However, if a crashing application causes the whole operating system to crash, the fault lies with the operating system.

Which one of the following, if true, is least helpful in establishing that this conclusion is properly drawn?

(A) Operating systems with generous amounts of memory are less susceptible to crashing, even when applications are poorly written.

(B) Operating systems can isolate the memory used by individual applications, even when an application uses a large amount of memory.

(C) An operating system can monitor an application’s consumption of memory and take action when that gets too high.

(D) Techniques for programming operating systems to catch and handle memory errors are well-defined and well-known among programmers.

(E) Because many applications can run simultaneously under a single operating system, the operating system should have a well-defined method of managing memory consumption.

Ritwick91 · Answer

Hi Bunuel,
Can you please explain why option D is wrong? I mean, except option D, all the options mentions something about operating system which can be taken into account to draw the conclusion but option D talks about the programming techniques known by programmers...which, IMO, may or may-not be relevant to draw the conclusion about OS's. 
Please clarify my understanding.

Thank you.

kumarankit01 · Answer

Hi I have also think Option D

Could you help here to understand why the option D is wrong .

Posted from my mobile device

KHow · Answer

Can someone help explain how option A is least helpful in establishing that the conclusion is properly drawn? I thought it was actually helpful. Thanks!

Posted from my mobile device

KarishmaB · Answer

- a poorly written application can consume more memory than it should 
- running out of memory can cause an application to crash.

However, if a crashing application causes the whole operating system to crash, the fault lies with the operating system.

So running out of memory can crash an application but it should not crash the operating system. So the operating system should have in-built measures because of which it should not crash. If it does crash with an application, it means the system is faulty, A normal operating system should not crash with a crashing app.

4 options below will help in establishing this.

(A) Operating systems with generous amounts of memory are less susceptible to crashing, even when applications are poorly written.

How much memory the operating system has should be irrelevant. When an application runs out of memory, the system should not crash. Actually how much memory there was doesn't matter. If systems will more memory crash fewer times, it's probably because they don't run out of memory that often. We need to establish that when the programs do run out of memory, the system should not crash.

(B) Operating systems can isolate the memory used by individual applications, even when an application uses a large amount of memory.

If the OS isolates the memory used by each application, when the app runs out of memory, the system should still have memory leftover. Hence, it should not crash. So a normal system should not crash with a crashing app. If it does, it means it is faulty.

(C) An operating system can monitor an application’s consumption of memory and take action when that gets too high.

Monitoring memory consumption and taking action are capabilities that normal operating systems have. Then they should not crash when an app crashes. If they do, they are faulty. Helps.

(D) Techniques for programming operating systems to catch and handle memory errors are well-defined and well-known among programmers.

Programmers know techniques to handle memory errors. So the techniques would be built in the operating system. Hence it should not crash because of a memory error. If it does, it is faulty. Helps.

(E) Because many applications can run simultaneously under a single operating system, the operating system should have a well-defined method of managing memory consumption.

The op system should have a well defined method of memory usage for many applications. Hence, it should not crash because of memory error. Helps.

Bunuel · Answer

OFFICIAL EXPLANATION:

A. Operating systems with generous amounts of memory are less susceptible to crashing, even when applications are poorly written.

Okay, you want to find the four answers indicating that operating systems are responsible for the smooth functioning of applications and are able to somehow manage their memory problems. The best way to do this is by process of elimination. If you can find four answers that show the operating system handling applications’ memory issues, then the answer that’s left over should be correct. Choice (B) helps the conclusion because it shows that operating systems are responsible for handling the memory used by individual applications. Choice (C) helps because it shows that operating systems can spot overuse of memory and stop it. Choice (D) helps because it tells you that programmers should know how to program an operating system that can prevent memory errors, which means all operating systems should be able to do this. Choice (E) helps the conclusion because it describes what an efficient operating system should be able to do. Choice (A) is the only answer that doesn’t put responsibility for memory management on the operating system; adding memory to the computer evidently can let the operating system off the hook. Choice (A) is the right answer.

Arro44 · Answer

Hi Bunuel , brief question; Could you add the source, as there seems to be an OA provided by the question creator?

BingingOnNetflix · Answer

+1 on this. Good question. Would like to know the source

wizmaverick · Answer

Hi Bunuel,

Going purely by the information stated, option A considers memory to be a part of the operating system, not the computer (even though we know that an operating system is a piece of software, and can't have memory per se). I would appreciate if you or any other community member could help me identify the flaw in my reasoning.

Posted from my mobile device

VerbalBot · Answer

Automated notice from GMAT Club VerbalBot: 

A member just gave Kudos to this thread, showing it’s still useful. I’ve bumped it to the top so more people can benefit. Feel free to add your own questions or solutions.

 This post was generated automatically.

Software engineers know that a poorly written application can consume

Prep Toolkit

Top 5 GMAT Debrief Videos

615 to 715 in 15 Days (Ria's Strategies)

More than Quant/Verbal Abilities: Speed vs. Accuracy

745 with Only Self-Prep and GMAT Club

From 555 to 765: 210-point Improvement

Perfect 805 Score Debrief by Julia

My Rewards

GMAT Critical Reasoning (CR) Questions

Software engineers know that a poorly written application can consume

Prep Toolkit

615 to 715 in 15 Days (Ria's Strategies)

More than Quant/Verbal Abilities: Speed vs. Accuracy

745 with Only Self-Prep and GMAT Club

From 555 to 765: 210-point Improvement

Perfect 805 Score Debrief by Julia

My Rewards