**Why XCom matters**: Cross-task communication for DAG orchestration; misuse = performance and size issues. **Mechanism**: Push via return value or `xcom_push`; pull via `xcom_pull`. Stored in Airflow metadata DB by default. **Scalability trade-offs**: Default backend has ~1MB...
This easy-level Spark/Big Data question appears frequently in data engineering interviews at companies like Citi. While less common, it tests deeper understanding that distinguishes strong candidates. Mastering the underlying concepts (airflow) will help you answer variations of this question confidently.
Start by clearly defining the core concept being asked about. Interviewers want to see that you understand the fundamentals before diving into implementation details. Structure your answer with a definition, then explain the practical application with a concise example.
Why XCom matters: Cross-task communication for DAG orchestration; misuse = performance and size issues. Mechanism: Push via return value or xcom_push; pull via xcom_pull. Stored in Airflow metadata DB by default. Scalability trade-offs: Default backend has ~1MB limit; large payloads = DB bloat. Cost implications: XCom in DB = latency for large data. Best practice: Keep XCom small (<1MB); use custom backend or external storage (S3) for paths; pass references, not data.
This answer is partially locked
Unlock the full expert answer with code examples and trade-offs
Practice real interviews with AI feedback, track progress, and get interview-ready faster.
Pro starts at $24/mo - cancel anytime
Get the most asked SQL questions with expert answers. Instant download.
No spam. Unsubscribe anytime.
Paste your answer and get instant AI feedback with a FAANG-level improved version.
Analyze My Answer β FreeAccording to DataEngPrep.tech, this is one of the most frequently asked Spark/Big Data interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.