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