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. Initialized stack memory.






2. Default branch within your repository.






3. A measure of logical dependency.






4. Code whatever it is you need to code.






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






6. Ignores files when pushing.






7. Stand up meetings show who will be valuable and needed.






8. Fix any problems and then repeat the process.






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






10. Stops when memory changes.






11. You have to tell it to link






12. A function that can load a library






13. The linking is already done internally






14. Downloads your changes and then merges.






15. When a conflict is fixed.






16. Portioning your changes to commit by inserting them into the index.






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






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






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






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






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






22. When doing a - precise task.






23. Link multiple projects together






24. Views all previous changes.






25. The default nickname for the remote repository.






26. What is part of the current scope.






27. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






28. Adds files to the repository.






29. Ask questions and obtain the details and requirements given.






30. Creates a copy of your current branch into a remote branch.






31. Do not optimize until the very end.






32. Makes a project compile in order of who is dependent on what






33. Try to find the flaws in your code.






34. Black Box - The way the program works is internally unknown.






35. Current line that is executing.






36. Developers should be integrated and releasing code into the code repository every few hours.






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






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






39. Uploads all changes staged in the index list into the repository database.






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






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






42. Downloads without merging.






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






44. One of the linking methods (pragma comment)






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






46. Freed heap memory.






47. Removes files from the repository.






48. Quick program.






49. Current view/ previous line.






50. Valid input that the program is designed to process.






Can you answer 50 questions in 15 minutes?



Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests