The driven source is that flume periodically and actively acquires data.

Question

Options

• ATrue
• BFalse

• A
  15% (3)
• B
  85% (17)

Explanation

Option B is correct because a driven source in Apache Flume is a passive source - it waits for an external agent to push data to it (e.g., Avro or Thrift sources that listen for incoming connections). The behavior described - periodically and actively acquiring data - actually defines a polling source (also called an event-driven or pull-based source), such as the Spooling Directory or Exec sources that Flume actively checks on a schedule.

Option A is wrong because it conflates two distinct Flume source categories: driven (push-based, passive) and polling (pull-based, active). The statement incorrectly attributes the polling source's behavior to the driven source.

Memory tip: Think of "driven" as being driven by someone else - external systems push data in. If Flume is the one doing the driving (going out to fetch data), that's a polling source, not a driven source.

No community discussion yet for this question.