Test your basic knowledge |

SWA - Software Architecture

Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. No man's land. Guard bytes before the after allocated heap memory.






2. When a concrete class inherits from a pure interface.






3. Default branch within your repository.






4. Function doesn't exist.






5. What is part of the current scope.






6. Define a one-to-many dependency between objects so that when one object changes state - all its dependents are notified and updated automatically






7. Inheritance between object.






8. Trying to access a location in memory that your computer cannot access.






9. A pointer or reference. One object needs to know about the other object to work.






10. The process of deciding which function definition to link during run-time.






11. Simply a value.






12. Are what function classes should include.






13. Freed heap memory.






14. Invalid or unexpected input that the program is not designed to process.






15. Bad! Don't ever use these types of variables!






16. A set of creation and initialization steps useful for a set of different related tests.






17. Symbols that can be invoked or used by other code in a different unit. All non inline class member functions and variables - non-static non-member functions and variables defined within a .cpp file






18. A group of code. unnamed can only be accessed within that translation unit - name can be accessed anywhere






19. CONSTANT






20. Ability to accept different types of parameters to bind to different implementations at run-time.






21. Application






22. When a .cpp file is compiled - the header files are first included (recursively) by the pre-processor. This block of code is called a ______________.






23. One of the linking methods (pragma comment)






24. NULL memory.






25. When GIT cannot merge your data.






26. Linking to dynamic libraries is usually handled by linking to an ____________.






27. Static in C++. Can span all instances of a class.






28. Concept based on limiting the scope of modules to provide better structures.






29. 2 Eyes + 2 Minds = AWESOME!






30. Treating a derived class's data members like it's base class's.






31. Allows you to switch your working copy to another branch.






32. Stops when memory changes.






33. Downloads your changes and then merges.






34. Current view/ previous line.






35. Written by the customers as things that the system needs to do for them.






36. Makes a copy of your repository.






37. No more than 40 hours to stop burnouts.






38. The default nickname for the remote repository.






39. A collection of memory addresses for all virtual functions in an objects class hierarchy.






40. Use this to find a memory address or signiture in a dll






41. Set of all pending changes.






42. Bookmark of a revised set with a title. For easy checkouts.






43. When you type in an object - you can see its attributes.






44. Variable doesn't exist.






45. When we remove redundant or obsolete designs and replace them with a new.






46. Classes build off of each other.






47. Provide a unified interface to a set of interfaces in a subsystem. Defines a higher-level interface that makes the subsystem easier to use.






48. When exporting a dll - the names of the functions are changed. This is knwon as ____________.






49. Taking code and moving it to a function that usually returns an object. They are always virtual functions.






50. Copies all changes from one branch into another branch.