**Why RMI Needs Proxies**: Clients invoke remote objects as if local; stubs/skeletons provide location transparency and serialization. **Stub (Client-side)**: Proxy for remote object; marshals arguments, sends over network, unmarshals return. Acts as local representative....
This easy-level General/Other question appears frequently in data engineering interviews at companies like JP Morgan. While less common, it tests deeper understanding that distinguishes strong candidates.
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 RMI Needs Proxies: Clients invoke remote objects as if local; stubs/skeletons provide location transparency and serialization.
Stub (Client-side): Proxy for remote object; marshals arguments, sends over network, unmarshals return. Acts as local representative.
Skeleton (Server-side): Receives calls, unmarshals args, invokes real object, marshals result. Modern Java RMI uses dynamic stub replacing skeleton.
Data Flow: Client -> stub (serialize) -> network -> skeleton (deserialize) -> server object.
Scalability: Each remote call incurs network latency; use for coarse-grained ops. At JP Morgan: consider serialization cost for large payloads.
Want feedback on your answer?
Paste your answer to this question and our AI Coach scores it, finds gaps, and shows you the FAANG-level version.
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 General/Other 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.