A) Only the source code of the software B) Helps new team members onboard quickly C) Written text and illustrations describing architecture, design, functionality, and usage
A) Only the HTTP methods B) Purpose, expected behavior, URL route, and HTTP methods C) Only the description of what the endpoint does
A) GET, POST, PUT, DELETE B) START, STOP, PAUSE, RESUME C) OPEN, CLOSE, SAVE, LOAD
A) Avoiding any comments in the code B) Using inline comments to explain complex logic C) Adding redundant comments that restate obvious code
A) Standardized descriptions for functions, classes, or modules B) To debug the code C) . To store data in the program
A) Javadoc style B) HTML format C) PEP 257
A) Confluence B) Javadoc C) Doxygen
A) To compile code into executable files B) To generate structured documentation from reStructuredText and docstrings C) To design user interfaces
A) Creative Commons B) Apache License 2.0 C) MIT License
A) Creative Commons B) MIT License C) Apache License 2.0
A) Software only B) Media and documents, not software C) Hardware designs
A) It makes the software harder to use B) It is not necessary for open-source projects C) It protects intellectual property and clarifies usage rights
A) The ability to perform required functions under stated conditions without failure B) The ability to be easily modified C) The ability to handle unexpected inputs without crashing
A) Error Detection & Correction B) Recovery Mechanisms C) Redundancy
A) Check sums, parity bits, and validation rules B) Redundancy C) Automated testing
A) Performance testing B) User acceptance testing C) Automated testing
A) Checkpointing and rollback in databases B) Duplicating servers C) Using parity bits
A) To ensure code and systems are clear, maintainable, and legally safe B) To avoid following any conventions C) To increase the number of tools used
A) Postman B) Swagger / OpenAPI C) RAML
A) API testing and documentation B) Creating documentation websites C) Designing API schemas
A) RAML and API Blueprint B) Redoc and MkDocs C) Swagger and OpenAPI
A) Sphinx B) Postman C) Redoc
A) status B) message C) parameters
A) daily.temp.min B) daily.feels_like C) daily.temp.max
A) Optimal use of resources (time, memory, CPU) while delivering results quickly B) Ability to duplicate critical components C) Ability to handle unexpected inputs without crashing
A) Duplicating critical components B) Checkpointing and rollback in databases, retry logic C) Using parity bits to detect errors
A) Adding more servers B) Using linear search instead of binary search B. Using binary search instead of linear search for larg C) Using binary search instead of linear search for large datasets
A) Ability to perform functions without failure over time B) Ability to duplicate critical components for fault tolerance C) Optimal use of resources (time, memory, CPU, network) while delivering results quickly
A) Database Optimization B) Caching & Memoization C) Algorithmic Optimization
A) To identify performance bottlenecks using tools B) To use multithreading C) To avoid memory leaks
A) Resource Management B) Caching & Memoization C) Caching & Memoization
A) Handling exceptions B) Avoiding memory leaks and releasing unused objects C) Testing edge cases
A) Database Optimization B) Algorithmic Optimization C) Parallelism & Concurrency
A) Indexing, query optimization, and normalization/denormalization trade-offs B) Caching all data C) Exception handling
A) Testing only the user interface B) Testing individual units of code (functions, classes, methods) in isolation C) Testing after full integration
A) Improves code maintainability and reduces regression issues B) Makes code harder to modify C) Increases development time significantly
A) Frequently integrating code into a shared repository and running automated tests B) Working on code in isolation without sharing C) Testing only once before release
A) To ensure new code does not break existing functionality B) To reduce the number of tests C) To delay integration until the end
A) Ability to use resources optimallyWhich practice involves never trusting user input and checking ranges, types, and formats? B) Ability to handle unexpected situations gracefully without crashing or incorrect results C) Ability to recover from failures automatically
A) Input Validation B) Fail-Safe Defaults C) Exception Handling
A) Testing only valid inputs B) Using try/except blocks C) Testing minimum, maximum, and out-of-range values
A) if/else B) try/except C) loops
A) Defaulting to secure/safe behavior if inputs are invalid B) Allowing any input without checks C) Showing technical errors to users
A) Anticipating and guarding against potential failures B) Writing complex code to prevent errors C) Avoiding any error handling
A) To retry failed operations B) To define preconditions, postconditions, and invariants C) To log runtime information
A) Stopping the system on failure B) Ignoring failed operations C) Automatically retrying operations like API calls if they fail
A) To collect runtime information for debugging and failure analysis B) To speed up the code C) To prevent errors from happening
A) Implementing watchdogs or self-healing services B) Ignoring failures C) Manually fixing errors
A) JUnit B) Jest C) pytest
A) Code that does not have any error handling B) Code that only works with perfect inputs C) A login form that handles incorrect passwords gracefully without crashing |