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