B is not correct
Synchronous API calls are blocking calls that do not return until either the change has been completed or there has been an error. For asynchronous calls, the response to the API call is returned immediately with a polling URL while the request continues to be processed. In heavier load conditions, it can be more efficient to submit multiple async calls and periodically check the status than to wait for each call to complete before submitting the next one.
This is correct, see below for source:
https://developer.cisco.com/docs/packaged-contact-center/#!synchronous-vs-asynchronous-writes/synchronous-vs-asynchronous-writes
Synchronous does NOT return immediately, it returns when either the change has been completed or there was an error.
Asynchronous call does return immediately
I'm going with D.
Synchronous calls have to wait for the response.
Asynchronous calls are just "subscriptions" which receive a callback later on, once the data is retrieved. Hence other calls can be made in the meantime.
Option B states "immediately" which can be interpreted multiple ways, it's not stated that it means "the requested data are returned immediately". Asynchronous APIs do respond immediately, not with the requested data but with a "taskID" or similar info.
This is another terribly written question. When considering answer B, is it talking about the actual data we're looking for or just a response in general? If it's talking about the actual data we want, then synchronous would be faster. If it's talking about any response at all, then async would be faster as it gets the callback now so you can fetch the data later. So if we're going strictly on the face value of the wording of the question without inferring anything else, answer D would make more sense.
In general, a synchronous API call is a request made by a client that waits for a response before moving on to the next task. The client is blocked or "stuck" until it receives a response from the server. This means that the client is unable to perform any other actions or processes until it receives the response.
On the other hand, an asynchronous API call is a request made by a client that does not wait for a response before moving on to the next task. The client is able to continue performing other actions or processes while it waits for a response from the server. This means that the client is able to handle multiple requests simultaneously, rather than having to wait for one request to be completed before moving on to the next.
The other options are not accurate. A synchronous or asynchronous API call may or may not require authentication, and there is no inherent difference in the offline capabilities or the number of calls that can be made in a specified time period between the two types of API calls.
Synchronous API calls are blocking calls that do not return until either the change has been completed or there has been an error
Asynchronous the response to the API call is returned immediately with a polling URL while the request continues to be processed
https://developer.cisco.com/docs/packaged-contact-center/#!synchronous-vs-asynchronous-writes/synchronous-vs-asynchronous-writes
B is correct
Netacad 4.2.2
Benefits of a synchronous API design
Synchronous APIs enable the application to receive data immediately. If the API is designed correctly, the application will have better performance because everything happens quickly. However, if it is not designed correctly, the API request will be a bottleneck because the application has to wait for the response.
When are APIs asynchronous?
APIs are usually designed to be asynchronous when the request is an action that takes some time for the server to process, or if the data is not readily available. For example, if the server has to make a request to a remote service to fetch the data, it cannot guarantee that it will receive the data immediately to send back to the client. Just because an API is asynchronous does not necessarily mean that the client will not get the data immediately. It only means that an immediate response with data is not guaranteed.
In the case of synchronous APIs, the expectation is that there will be an immediate return of data. The application requests data and waits for it until a value is returned.
In the case of asynchronous APIs, the availability of a resource, service or data store may not be immediate. These APIs may provide a callback to the requester when the requested resource is ready.
B) DEFINITELY
This section is not available anymore. Please use the main Exam Page.200-901 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
arthurb
Highly Voted 2 years, 9 months agoaplicacion101
2 years, 1 month agoThePokemonNuzlockingMaster
2 years, 5 months agoanagy11
Highly Voted 2 years, 7 months agoconcepcionz
1 year, 11 months agoFryja
Most Recent 3 weeks agoTejas007
3 weeks, 4 days agokymoni
6 months, 2 weeks agoknowyourself7
1 year, 3 months agoknowyourself7
1 year, 3 months agothrowaway_account
1 year, 4 months agonunyabeez
1 year, 8 months agomellohello
1 year, 10 months agoconcepcionz
1 year, 11 months agoSR_Cisco
2 years agoaplicacion101
2 years, 1 month agomacxsz
2 years, 4 months agoThePokemonNuzlockingMaster
2 years, 5 months agodaloslav
2 years, 6 months ago[Removed]
2 years, 6 months ago