API Design Principles Practice Test

These questions are part of the practice quiz. Start practicing

• Should good APIs prioritize user experience over strict functionality?
• Is API usability impacted by the clarity of its design semantics?
• Are convenience methods generally accepted in API design?
• Which of the following elements are included in "well documented" APIs?
• What does REST stand for in RESTful APIs?
• Is the wrong order of design considered to be "implement functionality -> design API"?
• Is it necessary to provide detailed documentation for implementation specifics.
• What is the primary difference between an open and a closed API?
• What is a web hook in the context of APIs?
• What is an API key?
• What data formats are commonly used in APIs for data interchange?
• What is a common challenge when updating an API?
• Which of the following is a common guideline in both API design principles and clean code principles?
• What guideline is addressed when a method has many same-typed parameters in a row?
• Which principle stresses the importance of avoiding abbreviations in API design?
• Why is it important to understand both subclassing and overriding?
• Should APIs be designed for easy extensibility due to the natural growth of libraries over time?
• What is a major difference between subclassing and overriding?
• If you allow subclassing in your API, what must you document?
• Does a good API require the user to call methods in a specific sequence?
• What does CRUD stand for in API operations?
• What step follows exemplary design in the API development process?
• What could indicate that a feature of an API needs redesign?
• What is the role of documentation in API design?
• Which aspect does not directly influence the performance of an API?
• Which practice is essential for effective API design?
• What is a key advantage of using APIs in software development?
• Can an API be modified at any time once it has established users?
• Which of the following is NOT a common type of API?
• What can be a result of improper overriding?
• In which scenario would subclassing be most appropriate?
• What is an essential step after defining API use cases?
• Which of the following is a consequence of proper subclassing?
• In API design, what outcome is expected when subclassing is executed correctly?
• In API design, what is a common method to enhance security?
• What should documentation for an API ideally include?
• What is meant by a RESTful API’s self-descriptiveness?
• In RESTful APIs, what is a resource?
• Which guideline is flagged when an API returns null instead of an empty collection?
• What is the purpose of error handling in API design?
• Should implementation adapt to the user rather than the user adapting to the implementation?
• What is a key benefit of overriding methods in subclassing?
• What role does caching play in API performance?
• What is meant by API discoverability?
• In semantic versioning, what fills the blank in major.___.patch?
• For a "fail fast" approach at runtime, where should pre-conditions be checked?
• What does 'idempotent' mean in the context of API methods?
• What guideline is violated if a public API uses exceptions for control flow?
• How is a resource defined in RESTful design?
• What is an example of a violation in API design related to error reporting?
• What does overriding in API design primarily allow developers to do?
• If an API fails silently without reporting errors, which guideline does this violate?
• Does a modular design with APIs help in managing large software systems?
• What technique supports setting properties in any order for GUI property-based APIs?
• What is the purpose of API logging?
• What does JSON stand for?
• Which of the following principles is NOT associated with API usability?
• What role does the Schema play in API design?
• Should users be made aware of implicit side effects when using an API?
• Which guideline is violated if different names are used for the same concept in an API?
• How do APIs typically enhance user experience in applications?
• In API design, what is the consequence of using overly clever methods?
• What is the main purpose of using version numbers in API endpoints?
• What distinguishes a PUT request from a PATCH request in API operations?
• Why is JSON often preferred over XML in API design?
• What is a potential issue with overloaded methods in an API?
• What is an API Gateway?
• What is not a recommended practice when designing the naming of API methods?
• Which principle focuses on having a clear interface in API design?
• What does versioning an API involve?
• Should API functions be published early to provide immediate user benefits?
• Which aspect of API design is prioritized by the principle of consistency?
• What distinguishes synchronous from asynchronous API calls?
• Which of the following describes a scaling strategy for APIs?
• What is the guideline violated when an API has a clever method that causes unexpected side effects?
• Should side effects be avoided in API design?
• What does the principle of "complete" API mean?
• What practices support API version evolution?
• What does authorization refer to in the context of APIs?
• Why is feedback vital in API design?
• Should convenience methods be included in an API?
• What violation occurs when an API has ambiguous overloads applicable to the same actuals?
• When should you prefer using overriding over subclassing?
• What does API stand for?
• What is one benefit of clear and consistent API versioning?
• According to the "Get up and running in 3 lines," what is included alongside instantiation and basic configuration?
• How important is it for an API to be easy to learn and use for newcomers?
• Can readable code be considered effective if it is verbose?
• What does scalability in API design refer to?
• Does good software design typically involve the use of modular components with APIs?
• Is readable code designed to be at the right abstraction level and should it hide important information?
• What does the Principle of Least Astonishment entail?
• What is an API payload?
• Is it true that anyone who programs is considered an API designer?
• What is an SDK (Software Development Kit) in relation to APIs?
• Which of the following is a recommended practice for API response formats?
• Why is API design considered important?
• How does a consistent API benefit users?
• What does error handling in API design involve?
• What is the single responsibility principle in API design?
• Should an API throw an exception immediately when an incoming parameter is incorrect?
• Can readable code sometimes obscure critical details?
• Is it feasible for a good API to provide all functions needed by users based solely on requirements collection?
• What is the last recommended step in the API design process?
• What is an endpoint in API terminology?
• What does OAuth stand for?
• In API design, why is consistency across endpoints important?
• What is the first step in the API design process?
• What is the purpose of API versioning?
• What is the role of authentication in API security?
• What should be done when in doubt about including certain features in an API?
• Which characteristic helps make an API "hard to misuse"?
• What is the conservative inheritance policy for concrete classes?
• What is a significant outcome of effective API design?
• When documenting an API, which aspect is essential for public methods?
• What is a characteristic of a good API?
• Which technique would you use to provide a new implementation for an existing method in a subclass?
• What is a potential risk of excessive subclassing in API design?
• What does "beware of bool values" primarily caution against?
• When needing to publish special values used internally, what is a best practice?
• What should API documentation primarily focus on?
• What does REST stand for in API design?
• When designing an API, does the implementation come before writing the code examples?
• Must the internal implementation of a library be publicly documented?
• What does the 204 status code indicate?
• What is the primary purpose of an API?
• If public methods are virtual in an API, which rule is not being followed?
• What role does authentication play in API security?
• Is it advisable to allow users to encounter defaults in the API without clear documentation?
• What aspect of an API often allows users to anticipate functionality based on previous experiences?
• What is CORS and why is it important?
• Which option improves memorability when designing an API?
• What role do SDKs play in API integration?
• What does the term 'response schema' refer to?
• What is the suggested course of action when in doubt about functionality in an API?
• Which guideline emphasizes the importance of handling edge cases?
• In practice, can an API ever be complete for all users?
• Which architectural style is commonly associated with modern API design?
• What does endpoint security in APIs ensure?
• What recommended technique can shorten a method with a long parameter list?
• How can user experience influence API design?
• What is one of the guiding principles in API design for maintenance?
• What should the semantics of an API ideally be?
• What does a major increment in semantic versioning indicate?
• What protocol is primarily used for REST APIs?
• Which type of API documentation focuses on user outcomes rather than implementation details?
• What's the recommended approach when modifying an established API?
• What best describes a mock API?
• Is it often the case that API users are less concerned with how the API works and more focused on what it accomplishes?
• Should "hello world" samples typically be lengthy?
• To avoid boilerplate for starting users of an API, what should you provide?
• What does HATEOAS stand for?
• What should exception messages include beyond just the problem description?
• What is a status code in an HTTP response?
• Is an API considered bad if it requires more than three lines of code to alter default behavior?
• What is one reason for writing use cases before any other code?
• Which of the following scenarios best illustrates the use of overriding?
• What guideline is violated when an API uses the prefix "set" for non-setter methods?
• Which of the following is a common method for securing APIs?
• Why is it crucial to monitor API performance regularly?
• What is rate limiting in API design?
• Which design principle focuses on keeping APIs simple and easy to use?
• What issue is highlighted when method signatures use many bool arguments?
• What is the significance of using a well-structured API?
• Is a minimal API more likely to be easy to memorize for users?
• Which semantic versioning increment is used for backwards-compatible bug fixes?
• Which of the following best defines an API's endpoint?
• Which aspect is crucial when designing a user-friendly API?
• In API design, what does the term "customization" generally refer to?
• Which of the following is NOT one of the main HTTP methods used in RESTful APIs?
• What is the recommended API style for users who must configure many GUI settings?
• Which characteristic is NOT considered essential for a good API?
• What is a service-oriented architecture (SOA)?
• What does 'contract first' mean in API development?
• What is one guideline to favor in API design regarding exceptions?
• What is API testing?
• Why is it important to design APIs with scalability in mind?
• Is documentation unnecessary if an API is implemented according to clean code principles?
• What best describes the relationship between an API's usability and how functions are named?
• Are API designs typically iterative, accommodating user feedback and changes over time?