You have a shared resource accessed by multiple tasks and interrupts. Which approach best protects the resource while keeping system responsiveness high?

hard📝 Application Q15 of 15

FreeRTOS - Interrupt Management

AUse long critical sections with taskENTER_CRITICAL() and taskEXIT_CRITICAL() around all resource access

BUse short critical sections only around the minimal code that accesses the resource

CDisable all interrupts globally for the entire program runtime

DAvoid using critical sections and rely on task delays

Step-by-Step Solution

Solution:

Step 1: Understand impact of critical section length
Long critical sections block interrupts for too long, reducing system responsiveness.
Step 2: Best practice for protecting shared resources
Short critical sections minimize interrupt blocking while protecting shared data safely.
Final Answer:
Use short critical sections only around the minimal code that accesses the resource -> Option B
Quick Check:
Short critical sections = better responsiveness [OK]

Quick Trick: Keep critical sections short for best performance [OK]

Common Mistakes:

Using long critical sections unnecessarily
Disabling interrupts globally
Ignoring synchronization needs

Master "Interrupt Management" in FreeRTOS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More FreeRTOS Quizzes

You have a shared resource accessed by multiple tasks and interrupts. Which approach best protects the resource while keeping system responsiveness high?

Step 1: Understand impact of critical section length

Step 2: Best practice for protecting shared resources

Final Answer:

Quick Check:

Want More Practice?