Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

LPI 201-450 Exam - Topic 7 Question 107 Discussion

Which of the following is a side effect of extensive usage of swap space?
A) The root filesystem may become full because swap space is always located on the system root partition. and B) The overall system performance may degrade because of heavy hard disk use and memory reorganization.
C) Since processes always exist completely in either RAM or swap, regular RAM may become unused if the kernel does not move processes back from the swap space to memory.
D) The memory may become fragmented and slow down the access to memory pages. However, this can be kept to a minimum by the regular use of memfrag -d.
E) Applications need to restart because their virtual memory addresses change to reflect memory relocation to the swap address area.

LPI 201-450 Exam - Topic 7 Question 107 Discussion

Actual exam question for LPI's 201-450 exam
Question #: 107
Topic #: 7
[All 201-450 Questions]

Which of the following is a side effect of extensive usage of swap space?

Show Suggested Answer Hide Answer
Suggested Answer: A, B

by Tish at Feb 07, 2025, 10:54 PM

Limited Time Offer

25%

Off

Get Premium 201-450 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Deandrea
9 months ago
D makes sense, fragmentation can be a real pain.
upvoted 0 times
...
Rosendo
9 months ago
A is a common issue, I've seen it happen before.
upvoted 0 times
...
Dyan
9 months ago
Wait, E sounds a bit off. Applications restarting because of swap? Really?
upvoted 0 times
...
Anglea
10 months ago
I disagree, I think C is more relevant in practice.
upvoted 0 times
...
Rima
10 months ago
B is definitely true, heavy disk use slows things down.
upvoted 0 times
...
Jolene
10 months ago
I vaguely recall something about processes being stuck in swap and not using RAM effectively, so option C could be relevant too.
upvoted 0 times
...
Brent
10 months ago
I practiced a question similar to this, and I think fragmentation is a concern, which might relate to option D.
upvoted 0 times
...
Erinn
10 months ago
I'm not entirely sure, but I feel like the root filesystem issue mentioned in option A could be a problem if swap is on the root partition.
upvoted 0 times
...
Lachelle
11 months ago
I think I remember that using too much swap can really slow down the system, so maybe option B is correct?
upvoted 0 times
...
Regenia
11 months ago
I think the answer is B. Extensive swap usage means the system is constantly moving data between RAM and disk, which is a performance bottleneck. The other options don't seem as directly related to the core side effect of swap overuse.
upvoted 0 times
...
Nada
11 months ago
I don't want to overthink this, but I'm a bit concerned about option E. If applications need to restart due to virtual memory changes, that could be a major issue. I'll double-check that one.
upvoted 0 times
...
Nobuko
11 months ago
The key here is understanding how swap space works. Option B seems the most likely - heavy disk activity and memory management issues can definitely impact performance when relying too much on swap.
upvoted 0 times
...
Luke
11 months ago
Hmm, I'm not entirely sure about this one. I know swap space is used when RAM is full, but I'm not clear on the specific side effects. I'll have to think this through carefully.
upvoted 0 times
...
Zoila
11 months ago
I'm pretty sure the answer is B. Extensive usage of swap space can degrade overall system performance due to heavy disk use and memory reorganization.
upvoted 0 times
...
Kris
1 year ago
Swap space? More like 'Swap Nightmare'! I'd rather have a system with infinite RAM than deal with the performance hit of constant swapping.
upvoted 0 times
Kenneth
1 year ago
C) The memory may become fragmented and slow down the access to memory pages. However, this can be kept to a minimum by the regular use of memfrag -d.
upvoted 0 times
...
Merrilee
1 year ago
B) Since processes always exist completely in either RAM or swap, regular RAM may become unused if the kernel does not move processes back from the swap space to memory.
upvoted 0 times
...
Glory
1 year ago
A) The overall system performance may degrade because of heavy hard disk use and memory reorganization.
upvoted 0 times
...
...
Angelica
1 year ago
E) is just plain wrong. Applications don't need to restart just because their virtual memory addresses change. The kernel handles that transparently.
upvoted 0 times
Marvel
1 year ago
D) The memory may become fragmented and slow down the access to memory pages. However, this can be kept to a minimum by the regular use of memfrag -d.
upvoted 0 times
...
Markus
1 year ago
B) The overall system performance may degrade because of heavy hard disk use and memory reorganization.
upvoted 0 times
...
...
Gail
1 year ago
D) is just ridiculous. Who actually uses 'memfrag -d' to 'minimize' memory fragmentation? Clearly, the developers who wrote that option have never used a real system before.
upvoted 0 times
Nu
1 year ago
E) Applications need to restart because their virtual memory addresses change to reflect memory relocation to the swap address area.
upvoted 0 times
...
Nelida
1 year ago
C) Since processes always exist completely in either RAM or swap, regular RAM may become unused if the kernel does not move processes back from the swap space to memory.
upvoted 0 times
...
Elmira
1 year ago
B) The overall system performance may degrade because of heavy hard disk use and memory reorganization.
upvoted 0 times
...
Tori
1 year ago
C) Since processes always exist completely in either RAM or swap, regular RAM may become unused if the kernel does not move processes back from the swap space to memory.
upvoted 0 times
...
Mollie
1 year ago
B) The overall system performance may degrade because of heavy hard disk use and memory reorganization.
upvoted 0 times
...
Sanda
1 year ago
A) The root filesystem may become full because swap space is always located on the system root partition.
upvoted 0 times
...
Casie
1 year ago
A) The root filesystem may become full because swap space is always located on the system root partition.
upvoted 0 times
...
...
Melissa
1 year ago
I agree with Detra. Constant swapping between RAM and disk is bound to hurt performance. Although C) sounds plausible, I don't think that's the primary side effect.
upvoted 0 times
...
Detra
1 year ago
B) is the correct answer. Extensive swap usage can lead to heavy disk I/O, which degrades overall system performance.
upvoted 0 times
Theresia
1 year ago
Yes, extensive swap usage can definitely slow down the system.
upvoted 0 times
...
Pamella
1 year ago
I think B) is the correct answer.
upvoted 0 times
...
...
Madalyn
1 year ago
I'm not sure, but I think it could also lead to the root filesystem becoming full, so maybe A is also a possible side effect.
upvoted 0 times
...
Eve
1 year ago
I agree with you, Eve. Extensive swap space usage can definitely slow down the system.
upvoted 0 times
...
Mariann
1 year ago
I think the answer is B.
upvoted 0 times
...

Save Cancel