Setting and Characteristics of Synchronous Calls to APIs

AC.

Sure, I can provide a detailed explanation of the answers to your question.

First, regarding the configuration of an on-change publication for YANG-push versus OpenConfig, the dampening period setting is used to control how often updates are sent to the subscriber. It determines the amount of time that must elapse before subsequent updates can be sent, in order to prevent excessive updates from flooding the network.

Moving on to the characteristics of synchronous calls to APIs, the correct answers are A and C.

A. They block until a response is returned from the servers Synchronous calls to APIs block the application until a response is received from the server. This means that the application will not be able to execute any further code until the server has sent a response back. While this may be convenient in some cases, it can also lead to performance issues if the server takes a long time to respond, as the application will be unresponsive during that time.

C. They add perceived latency to an application if data is not received When an application makes a synchronous call to an API and waits for a response, it can create the perception of latency or slowness, particularly if the response is delayed. This can be frustrating for users who expect the application to respond quickly.

B. They make an application less portable, so asynchronous calls are preferred Asynchronous calls are often preferred over synchronous calls because they allow the application to continue executing while waiting for a response from the server. This can improve the overall performance and responsiveness of the application. Additionally, asynchronous calls can be more portable, as they do not require the application to wait for a response before continuing with other tasks.

D. Calls are limited to specific programming languages Synchronous calls to APIs are not limited to specific programming languages, as they are a common feature in many programming languages and frameworks. However, different programming languages may have different ways of making synchronous calls to APIs.

E. They do not block while waiting for the API to be processed. This statement is incorrect. Synchronous calls to APIs do block the application while waiting for a response from the server. Asynchronous calls, on the other hand, do not block the application and allow it to continue executing while waiting for a response.