What are characteristics of Edge-based activation? (Select two.)

Question

Options

• AEnables real-time personalization.
• BUses batch workflows for data updates.
• CProcesses data locally to reduce latency.
• DRequires manual activation triggers.

• A
  71% (15)
• B
  10% (2)
• D
  19% (4)

Explanation

Edge-based activation works by processing data at distributed nodes close to the end user rather than routing requests back to a central server. This architecture inherently reduces latency (C) because computation happens locally, and it enables real-time personalization (A) because decisions are made instantly at the point of interaction - no waiting on a central data pipeline.

Why B is wrong: Batch workflows are the hallmark of scheduled/batch activation, where data is collected and processed in bulk at set intervals - the opposite of edge's always-on, event-driven model.

Why D is wrong: Edge activation is automated and event-triggered (e.g., a page load or API call). Manual triggers describe a different activation pattern, often used in simple or legacy workflows.

Memory tip: Think of "EDGE" as Event-driven, Distributed, Ground-level (local), Emmediate - all pointing to real-time and low-latency processing. If an answer mentions "batch" or "manual," it's describing the opposite of what edge activation does.

No community discussion yet for this question.