Bird
0
0

Why might relying only on @Input() and @Output() for all component communication be limiting in large Angular apps?

hard📝 Conceptual Q10 of 15
Angular - Component Interaction
Why might relying only on @Input() and @Output() for all component communication be limiting in large Angular apps?
ABecause deeply nested or sibling components need shared services for scalable communication
BBecause @Input() and @Output() cause performance issues
CBecause Angular does not support @Input() and @Output() in large apps
DBecause services cannot be used with @Input() and @Output()
Step-by-Step Solution
Solution:
  1. Step 1: Understand communication complexity

    In large apps, components can be deeply nested or siblings without direct relation.
  2. Step 2: Recognize service role

    Shared services provide a scalable way to share data beyond parent-child bindings.
  3. Final Answer:

    Because deeply nested or sibling components need shared services for scalable communication -> Option A
  4. Quick Check:

    @Input/@Output limited for complex apps, services help [OK]
Quick Trick: Use services for complex or sibling communication [OK]
Common Mistakes:
  • Thinking @Input/@Output cause performance issues
  • Believing Angular disallows @Input/@Output in big apps
  • Assuming services can't be combined with @Input/@Output

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Angular Quizzes