Q: 8
What are two characteristics of synchronous calls to APIs? (Choose two.)
Options
Discussion
C/D? This flips if they cared about async behavior but blocking and added latency both scream synchronous to me.
Its B and C
D imo, but C is also correct. Synchronous calls block execution until a response (that's D), and that blocking can add noticeable latency to your app (C). Option B sounds more like a side effect rather than a main trait. Open if anyone sees it differently.
Not sure C/D always fits here. If the API is designed to return instantly with partial data and process in background, does that still count as "blocking" in the strict sense? Some platforms blur this (like with webhooks).
C and D tbh, that's what you'd expect for blocking calls and possible latency.
Honestly Cisco loves to word these tricky, but it’s D and C this time.
Probably C and D, sync calls block and can slow things down if data isn’t fast. Not confident about B since that’s more about preference than a core feature.
C/D? I think C and D fit since sync calls block and bump up latency but not totally sure.
D , but you gotta include C. Sync API calls block until response (D), and that can add perceived latency while waiting (C). B is more of a side effect, not a core trait. Happy to hear other logic here.
I don’t think C/D is right, B/C could fit-sync calls can affect portability (B) and add latency (C). D feels more like a technical detail, but portability impact shows up in real projects. Let me know if I’m off.
Be respectful. No spam.