Q: 10
Which OSPF database packet determines which router is in charge of the database synchronization
and the transferring of LSA headers between the two systems?
Options
Discussion
D tbh, since link-state update is what actually sends LSAs so kinda close, but probably a trap in this context.
Its B. Database description packets set the master/slave roles for OSPF sync. Link-state request is just for missing LSAs, not control.
Always get tripped up by these Juniper OSPF wording quirks. Its B
Not A, it’s B here. Database description packets decide which router's in charge (master/slave) and manage the LSA header exchange during synchronization. Link-state request (A) gets used if something’s missing after that, but B matches what they’re asking. Pretty sure based on OSPF process for adjacency, but open if someone sees it different.
These Juniper questions word stuff so awkwardly. B imo
B or A? I'm leaning toward B since database description packets pick master/slave for OSPF db sync and handle LSA headers. But if it's about actually requesting the full LSAs, that's where A (link-state request) comes in. Still think B fits the question wording better, but open to other takes.
Option B not A. Link-state request is tempting but it's database description packets that actually determine master/slave for sync control.
A tbh, since link-state request packets seem like they're doing the actual work of database sync by asking for LSAs that are missing. Database description feels more like just sharing summaries, not deciding who controls the process. I could be missing a detail but that's how I remember it from OSPF section. Anyone see it differently?
B
Probably B here. Database Description packets (DBD) handle the master/slave role and exchange just LSA headers, not the full LSA content. If the question asked about transferring full LSAs instead of headers, D would make sense, but with the focus on sync control and headers, B lines up. I think that’s why they worded it this way. Anyone see a scenario where this flips?
Be respectful. No spam.