{"id":1270,"date":"2018-02-21T13:58:40","date_gmt":"2018-02-21T13:58:40","guid":{"rendered":"https:\/\/www.h2kinfosys.com\/blog\/?p=1270"},"modified":"2025-10-22T07:08:09","modified_gmt":"2025-10-22T11:08:09","slug":"istqb-mock-test-4","status":"publish","type":"post","link":"https:\/\/www.h2kinfosys.com\/blog\/istqb-mock-test-4\/","title":{"rendered":"ISTQB Mock Test 4"},"content":{"rendered":"\n<h3 class=\"wp-block-heading\"><strong>1. In integration testing, a stub is used to:<\/strong><\/h3>\n\n\n\n<p>A. Replace a called module temporarily<br>B. Replace a calling module<br>C. Execute system-level testing<br>D. Simulate user input<\/p>\n\n\n\n<p>\u2705 <strong>Answer:<\/strong> A. Replace a called module temporarily<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>2. In integration testing, a driver is used to:<\/strong><\/h3>\n\n\n\n<p>A. Simulate low-level modules<br>B. Simulate high-level modules<br>C. Replace missing test cases<br>D. Debug performance issues<\/p>\n\n\n\n<p>\u2705 <strong>Answer:<\/strong> B. Simulate high-level modules<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>3. Boundary value analysis is used to:<\/strong><\/h3>\n\n\n\n<p>A. Test functional workflows<br>B. Test internal logic<br>C. Focus on input limits and edges<br>D. Validate non-functional attributes<\/p>\n\n\n\n<p>\u2705 <strong>Answer:<\/strong> C. Focus on input limits and edge<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>4. Decision table testing is most useful for:<\/strong><\/h3>\n\n\n\n<p>A. User interface testing<br>B. Exploratory testing<br>C. Business rule validation<br>D. Regression testing<\/p>\n\n\n\n<p>\u2705 <strong>Answer:<\/strong> C. Business rule validation<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>5. State transition testing is based on:<\/strong><\/h3>\n\n\n\n<p>A. Logical decisions<br>B. System states and events<br>C. User stories<br>D. Code syntax<\/p>\n\n\n\n<p>\u2705 <strong>Answer:<\/strong> B. System states and events<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>6. Pairwise testing reduces:<\/strong><\/h3>\n\n\n\n<p>A. Number of users<br>B. Number of possible test combinations<br>C. Test team workload<br>D. Documentation effort<\/p>\n\n\n\n<p>\u2705 <strong>Answer:<\/strong> B. Number of possible test combinations<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>7. Root cause analysis is used to:<\/strong><\/h3>\n\n\n\n<p>A. Assign severity levels<br>B. Find who caused the defect<br>C. Identify underlying cause of defects<br>D. Close the project<\/p>\n\n\n\n<p>\u2705 <strong>Answer:<\/strong> C. Identify underlying cause of defects<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>8. Test automation is best suited for:<\/strong><\/h3>\n\n\n\n<p>A. Usability tests<br>B. Security assessments<br>C. Regression and repetitive tests<br>D. Ad-hoc testing<\/p>\n\n\n\n<p>\u2705 <strong>Answer:<\/strong> C. Regression and repetitive tests<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>9. A test execution tool is used to:<\/strong><\/h3>\n\n\n\n<p>A. Track defects<br>B. Measure code coverage and automate execution<br>C. Manage configuration items<br>D. Collect customer feedback<\/p>\n\n\n\n<p>\u2705 <strong>Answer:<\/strong> B. Measure code coverage and automate execution<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>10. A test oracle is:<\/strong><\/h3>\n\n\n\n<p>A. The tester\u2019s intuition<br>B. A document specifying expected results<br>C. A test automation tool<br>D. A database schema<\/p>\n\n\n\n<p>\u2705 <strong>Answer:<\/strong> B. A document specifying expected results<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>11. Entry and exit criteria act as:<\/strong><\/h3>\n\n\n\n<p>A. Test execution guidelines<br>B. Quality control checkpoints<br>C. Automation standards<br>D. Debugging policies<\/p>\n\n\n\n<p>\u2705 <strong>Answer:<\/strong> B. Quality control checkpoints<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>12. The biggest challenge in automation testing is:<\/strong><\/h3>\n\n\n\n<p>A. Script execution<br>B. Script maintenance after product updates<br>C. Test data management<br>D. Scheduling tests<\/p>\n\n\n\n<p>\u2705 <strong>Answer:<\/strong> B. Script maintenance after product updates<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>13. Load testing primarily measures:<\/strong><\/h3>\n\n\n\n<p>A. Security vulnerabilities<br>B. Application usability<br>C. System performance under expected load<br>D. User satisfaction<\/p>\n\n\n\n<p>\u2705 <strong>Answer:<\/strong> C. System performance under expected load<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>14. Ad-hoc testing relies on:<\/strong><\/h3>\n\n\n\n<p>A. Structured planning<br>B. Tester\u2019s experience and intuition<br>C. Automated scripts<br>D. Test design tools<\/p>\n\n\n\n<p>\u2705 <strong>Answer:<\/strong> B. Tester\u2019s experience and intuition<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>15. Test logs are maintained to:<\/strong><\/h3>\n\n\n\n<p>A. Track test execution results and environment details<br>B. Record coding standards<br>C. Store test data only<br>D. Maintain configuration items<\/p>\n\n\n\n<p>\u2705 <strong>Answer:<\/strong> A. Track test execution results and environment details<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>16. The first step in defect management is:<\/strong><\/h3>\n\n\n\n<p>A. Assigning the defect<br>B. Logging or reporting the defect<br>C. Fixing the defect<br>D. Closing the defect<\/p>\n\n\n\n<p>\u2705 <strong>Answer:<\/strong> B. Logging or reporting the defect<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>17. The pesticide paradox suggests:<\/strong><\/h3>\n\n\n\n<p>A. Developers reuse the same code<br>B. Testers must repeat same test cases<br>C. Repeated tests lose effectiveness unless updated<br>D. Bugs appear randomly<\/p>\n\n\n\n<p>\u2705 <strong>Answer:<\/strong> C. Repeated tests lose effectiveness unless updated<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>18. Defect clustering means:<\/strong><\/h3>\n\n\n\n<p>A. Defects are equally distributed<br>B. Most defects are found in few modules<br>C. Each test reveals equal defects<br>D. Defects occur randomly<\/p>\n\n\n\n<p>\u2705 <strong>Answer:<\/strong> B. Most defects are found in few modules<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>19. Absence-of-errors fallacy implies:<\/strong><\/h3>\n\n\n\n<p>A. If software has no bugs, it\u2019s perfect<br>B. Even bug-free software can fail user expectations<br>C. Errors can\u2019t be removed<br>D. Testing never ends<\/p>\n\n\n\n<p>\u2705 <strong>Answer:<\/strong> B. Even bug-free software can fail user expectations<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>20. Test independence is important because:<\/strong><\/h3>\n\n\n\n<p>A. It ensures automation coverage<br>B. It avoids conflict between teams<br>C. It prevents bias and increases objectivity<br>D. It reduces cost<\/p>\n\n\n\n<p>\u2705 <strong>Answer:<\/strong> C. It prevents bias and increases objectivity<\/p>\n","protected":false},"excerpt":{"rendered":"<p>1. In integration testing, a stub is used to: A. Replace a called module temporarilyB. Replace a calling moduleC. Execute system-level testingD. Simulate user input \u2705 Answer: A. Replace a called module temporarily 2. In integration testing, a driver is used to: A. Simulate low-level modulesB. Simulate high-level modulesC. Replace missing test casesD. Debug performance [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":7617,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[88],"tags":[100,101,90,91],"class_list":["post-1270","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-istqb-quiz","tag-istqb-online-quiz","tag-istqb-practice-test","tag-istqb-quiz","tag-istqb-skill-test"],"_links":{"self":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/1270","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/comments?post=1270"}],"version-history":[{"count":3,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/1270\/revisions"}],"predecessor-version":[{"id":31120,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/1270\/revisions\/31120"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/media\/7617"}],"wp:attachment":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/media?parent=1270"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/categories?post=1270"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/tags?post=1270"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}