Cisco Exam 300-435 Topic 1 Question 46 Discussion

Actual exam question for Cisco's 300-435 exam

Question #: 46
Topic #: 1

[All 300-435 Questions]

What are two characteristics of synchronous calls to APIs? (Choose two.)

AThey can be used only with certain programming languages.

BThey make your application less portable, so asynchronous calls are preferred.

CThey can add perceived latency to your application if data is not received.

DThey block until a response is returned from the servers.

EThey do not block while waiting for the API to be processed.

Show Suggested Answer

Suggested Answer: A

by Eladia at Apr 25, 2023, 07:49 AM

Limited Time Offer

25%

Off

Get Premium 300-435 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Lai

1 months ago

Synchronous calls, eh? Sounds like a real 'sync' or swim situation! But seriously, C and D are the way to go. Blocking is the name of the game, baby!

upvoted 0 times

...

Lashawn

1 months ago

Synchronous calls are like waiting in line at the DMV - it may be slow, but at least you know where you stand. C and D are the clear winners here.

upvoted 0 times

...

Rosio

1 months ago

Haha, E is just plain wrong. Synchronous calls are all about blocking until you get a response. I'm going with C and D, no doubt about it.

upvoted 0 times

Carey

12 days ago

Synchronous calls are all about waiting for a response, so C and D make sense.

upvoted 0 times

...

Rolland

13 days ago

Yeah, C and D are the correct characteristics. They can add latency and block until a response.

upvoted 0 times

...

Mattie

17 days ago

User 3: Synchronous calls can add perceived latency if data is not received, and they block until a response is returned.

upvoted 0 times

...

Gabriele

22 days ago

I agree, E is definitely wrong. Synchronous calls do block until a response.

upvoted 0 times

...

Dwight

23 days ago

User 2: Yeah, I think C and D are the correct characteristics for synchronous calls.

upvoted 0 times

...

Jaclyn

1 months ago

User 1: I agree, E is definitely wrong. Synchronous calls block until a response is returned.

upvoted 0 times

...

Odette

2 months ago

Hmm, I'm not sure about B. Synchronous calls might not be the most portable, but that doesn't mean we should avoid them entirely. I'd say C and D are the way to go.

upvoted 0 times

Emily

16 days ago

Yes, C and D are key factors to consider when using synchronous calls to APIs.

upvoted 0 times

...

Emily

17 days ago

B is not entirely accurate, synchronous calls can still be useful in certain situations.

upvoted 0 times

...

Emily

22 days ago

I agree, C and D are important characteristics of synchronous calls.

upvoted 0 times

...

Jacquline

2 months ago

Synchronous calls can be a pain, but at least they're straightforward. I'd go with C and D - that's the classic synchronous behavior, right?

upvoted 0 times

Mike

1 months ago

I think C and D are the right choices too. Synchronous calls can definitely add latency to an application.

upvoted 0 times

...

William

2 months ago

I agree, synchronous calls can be easier to understand. And yes, C and D are correct.

upvoted 0 times

...

Ricarda

2 months ago

But asynchronous calls are preferred because they do not block while waiting for the API to be processed.

upvoted 0 times

...

Bernardine

2 months ago

I agree, synchronous calls block until a response is returned from the servers.

upvoted 0 times

...

Johanna

2 months ago

I think synchronous calls can add perceived latency to the application.

upvoted 0 times

...