A _______________ change is one that does not negatively impact existing service

Question

A _______________ change is one that does not negatively impact existing service consumers (Chapter 10)

A) contemporary

B)comparable

C)compatible

D)contemptible

RESTful services should define custom payload media types with the format : (Chapter 9)

A) application/x-www-form-urlencoded

B) application/vnd.[organization].[type+supertype]

C)vendor/custom.[application-name].[format-type]

D) [vendor-name].multipart/form-data You need to confirm a manager is authorized to review time sheets. To do so, you should use __________________ service (Chapter 6)

Explanation / Answer

1.

Ans A

explantion : contemporary models of change, based on the principles of effectiveness and efficiency. According to Albrow (1989), effectiveness and efficiency is achieved through the division and specialisation of labour, a hierarchal management structure with definite roles and rules, and the discouragement of the use of official titles for personal gain. Albrow (1989) maintained that efficiency and effectiveness is achieved using the Weberian (bureaucratic) model of administrative theory in contrast to NPM. For example, Max Weber formulated a theory of ‘bureaucracy’ whereby he envisioned the creation of distinct professional services ‘recruited and appointed by merit, politically neutral, which would remain in office throughout changes in government’ (Hughes, 2003, p. 20). Lane (1993

Q2

ans:B

explanation :

The majority of HTTP APIs out there do not reap the benefits of using media types correctly either. The majority seem to use application/json and call it done. The client gets absolutely no information about how to read the data, other than they'll need a JSON decoder… This is like having an HTML file and using a `.txt` file extension. It's correct in the sense that the file is plain text, but absolutely useless for interpreting the file to render a web page.

Media types allow an API to inform the client how to interpret the data in the payload. This is arguably much harder than adding hypermedia to an API. The correct media types enforce the structure of the payload and also what the payload data means.

This is why most APIs just use application/json. If you're lucky, there's some documentation somewhere that explains things. Half the time, we seem to expect client developers to read the JSON and interpret it based on experience.

The best example of where this works well is the media type "text/html". Given a payload in this media type, a web browser can render the information in the way that the web developer (api server) automatically. This is because every server that sends a document with a text/html payload sends the same tags for the same meaning.

We can do this in the API world too, but it requires thinking about and is harder, so it doesn't happen…

There are three uses of media-types that I see in the world:

Related Questions

Navigate

• Browse (All)
• Browse A
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.