Describe Pravega and Its Storage Architecture DATA-ENGINEERING-OPTIMIZE Practice Questions (Page 5)

Questions 21–23

1. 21application · medium

   A retail company uses Pravega to stream clickstream data and processes it with Apache Flink for real-time personalization. They notice that when the stream is scaled to more segments, the Flink job's parallelism is not fully utilized. What is the most likely cause?

   • AThe Flink job is using a single Pravega reader group.
   • BThe Pravega stream is configured with a low retention policy.
   • CThe Flink job's parallelism is set lower than the number of segments, so some segments are not read by any subtask.
   • DThe Flink job is using event-time processing instead of processing-time.
   Reveal Solution Discussion Select an answer first
2. 22application · medium

   A healthcare analytics platform uses Pravega to ingest patient monitoring data. They must guarantee that once a write is acknowledged, the data is not lost even if the low-latency tier fails. How does Pravega achieve this durability?

   • AWrites are acknowledged only after the data is durably stored in the low-latency tier and replicated to the durable tier.
   • BData is written only to the durable tier, and the low-latency tier is used solely for reads.
   • CWrites are acknowledged immediately upon receipt, and data is later flushed to the durable tier asynchronously.
   • DDurability is achieved by keeping multiple copies of data in the low-latency tier only.
   Reveal Solution Discussion Select an answer first
3. 23foundation · easy

   What write semantics does Pravega provide?

   • ARandom-access writes to any offset in a segment.
   • BOverwrite semantics for existing events.
   • CTransactional writes that can be rolled back.
   • DAppend-only writes to segments.
   Reveal Solution Discussion Select an answer first