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. Uploads all changes staged in the index list into the repository database.






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






3. Stops when memory changes.






4. When a conflict is fixed.






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






6. 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






7. No more than 40 hours to stop burnouts.






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






9. Ignores files when pushing.






10. CONSTANT






11. Meetings used to create a release plan - which will lay out the overall project.






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






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






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






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






16. No man's land. Guard bytes before the after allocated heap memory.






17. Connection between a local brand and a remote branch.






18. Code whatever it is you need to code.






19. When GIT cannot merge your data.






20. Figure out what is feasible. Decide whether to use API's or to write from scratch.






21. The default nickname for the remote repository.






22. Italicized in UML.






23. Separating out a section of code into a reusable function or class.






24. Downloads your changes and then merges.






25. Creates a spin-off of a repository for concurrent development.






26. Whats displayed to the screen






27. Set of all pending changes.






28. Keeps a team using a similar naming convention for things.






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






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






31. Variable doesn't exist.






32. Breaks encapsulation boundaries.






33. NULL memory.






34. Ability to withstand change and what the effects are.






35. (Door-----Spell) BI_DIRECTIONAL because both classes can reference each other. (Door--->Spell) DIRECTIONAL because only the door knows and can reference Spell.






36. Always do the simplest design that could possibly work.






37. Input






38. Application






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






40. Having power over inheritance with the flexibility of composition.






41. Quick program.






42. Weak relationship between two classes. Almost always results in a #include.






43. Function doesn't exist.






44. Views all previous changes.






45. 2 Eyes + 2 Minds = AWESOME!






46. Makes a copy of your repository.






47. One of the linking methods (pragma comment)






48. When a class is defined within another class.






49. Current line that is executing.






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







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:



Major Subjects



Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Most popular tests