Site icon T4Tutorials.com

Stress Testing – Real-time Systems MCQs

1. What is the main purpose of stress testing in real-time systems?

(A) To measure average task execution times


(B) To evaluate system behavior under extreme or abnormal conditions beyond normal loads


(C) To store logs without analysis


(D) To replace the operating system



2. Stress testing helps identify:

(A) Disk batch-only delays


(B) CPU idle exclusively


(C) System weaknesses, bottlenecks, and potential failure points


(D) Memory-only inefficiencies



3. One key metric during stress testing is:

(A) CPU idle exclusively


(B) Deadline miss rate


(C) Disk batch-only usage


(D) Memory-only throughput



4. Stress testing often involves:

(A) CPU idle exclusively


(B) Overloading tasks, injecting faults, or simulating hardware failures


(C) Disk batch-only testing


(D) Memory-only overload



5. The main difference between load testing and stress testing is:

(A) Load testing tests expected or peak loads, while stress testing tests beyond normal limits


(B) CPU idle exclusively


(C) Disk batch-only testing


(D) Memory-only evaluation



6. Stress testing helps ensure:

(A) Memory-only stability


(B) CPU idle exclusively


(C) Disk batch-only safety


(D) System reliability and robustness under worst-case conditions



7. In real-time systems, stress testing can reveal:

(A) Memory-only conflicts


(B) CPU idle exclusively


(C) Disk batch-only failures


(D) Race conditions, deadlocks, and priority inversions



8. Stress testing is critical for:

(A) Disk batch-only systems


(B) CPU idle exclusively


(C) Safety-critical and mission-critical real-time systems


(D) Memory-only testing



9. Synthetic stress testing generates:

(A) Memory-only bursts


(B) CPU idle exclusively


(C) Disk batch-only workloads


(D) Artificially high task loads or event bursts to evaluate system performance



10. Trace-driven stress testing uses:

(A) Recorded high-load traces from real systems to reproduce extreme conditions


(B) CPU idle exclusively


(C) Disk batch-only traces


(D) Memory-only simulation



11. Monitoring system performance during stress testing focuses on:

(A) CPU idle exclusively


(B) Response times, deadline adherence, and resource utilization


(C) Disk batch-only metrics


(D) Memory-only performance



12. Stress testing can be used to evaluate:

(A) Network latency, throughput, and message handling under extreme load


(B) CPU idle exclusively


(C) Disk batch-only network performance


(D) Memory-only communication



13. One limitation of stress testing is:

(A) Disk batch-only limitations


(B) CPU idle exclusively


(C) Extreme conditions may not represent typical operation, so results should be interpreted carefully


(D) Memory-only accuracy



14. Stress testing can help improve system design by:

(A) CPU idle exclusively


(B) Identifying weak points and guiding optimization for robustness


(C) Disk batch-only improvements


(D) Memory-only fixes



15. Stress testing is essential for:

(A) Disk batch-only applications


(B) CPU idle exclusively


(C) Mission-critical applications like aerospace, automotive, and medical systems


(D) Memory-only tasks



16. Resource contention observed during stress testing indicates:

(A) Memory-only competition


(B) CPU idle exclusively


(C) Disk batch-only contention


(D) Multiple tasks competing for limited CPU, memory, or I/O resources



17. Task starvation detected during stress testing shows:

(A) Low-priority tasks unable to execute due to high-priority task overload


(B) CPU idle exclusively


(C) Disk batch-only starvation


(D) Memory-only starvation



18. Stress testing results can guide:

(A) Disk batch-only tuning


(B) CPU idle exclusively


(C) Scheduling adjustments, resource allocation, and system optimization


(D) Memory-only adjustments



19. Continuous stress monitoring helps in:

(A) Disk batch-only detection


(B) CPU idle exclusively


(C) Detecting early signs of system instability or failure


(D) Memory-only monitoring



20. The main goal of stress testing in real-time systems is:

(A) Memory-only evaluation


(B) CPU idle exclusively


(C) Disk batch-only validation


(D) Ensuring the system remains reliable, robust, and predictable under extreme conditions



Exit mobile version