I85PREP
⌘ K
ISTQB CT-MAT study materials
ISTQB CT-MAT study resources

ISTQB CT-MAT practice questions

One question at a time. Build your ISTQB CT-MAT understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Mobile Application Testing (official domain breakdown not stated in source)

A retail app team wants to test how their Android build behaves when the device loses connectivity in a tunnel and regains it a few seconds later. Which test type is most directly aimed at this scenario?

  1. Localization testing with a pseudo-locale enabled
  2. Interrupt testing focused on network loss and recovery Correct answer.
  3. Installability testing on a clean device image
  4. Accessibility testing with TalkBack enabled

Explanation

Interrupt testing verifies how a mobile app handles events that suspend or disturb its execution, such as incoming calls, notifications, or loss of network connectivity. Testing the tunnel scenario means simulating the interruption and checking that the app recovers state and resumes data flow correctly. The other options address installation, translation, and assistive-technology concerns rather than interruption handling.

Question 2Mobile Application Testing (official domain breakdown not stated in source)

Which characteristic makes emulator-based testing a poor substitute for real-device testing of a camera-dependent feature?

  1. Emulators always require an internet connection to execute tests
  2. Emulators cannot run the app's production build artifact
  3. Emulators cannot display the app's user interface at all
  4. Emulators typically simulate hardware with stubs rather than real sensors and optics Correct answer.

Explanation

Emulators and simulators approximate device hardware, but sensors such as cameras, GPS, and biometric readers are usually stubbed or partially simulated. Real-device testing is needed where actual hardware behavior, image quality, and sensor timing matter. Emulators do run production builds and render the UI, so the other claims are false.

Question 3Mobile Application Testing (official domain breakdown not stated in source)

A test manager must choose a device coverage strategy for a global consumer app. Which approach best balances risk and cost for the first test cycle?

  1. Select a risk-based matrix of representative OS versions, screen sizes, and manufacturers Correct answer.
  2. Test only on the newest flagship device from each major manufacturer
  3. Test exclusively on low-end devices to stress performance
  4. Test only on the single device model owned by the test team

Explanation

Device fragmentation means no team can test every model, so coverage is chosen by risk: popular OS versions, common screen densities, key manufacturers, and business-critical markets. A representative matrix spreads coverage across the factors most likely to expose defects. Single-device or single-tier strategies leave large risk areas untested.

Question 4Mobile Application Testing (official domain breakdown not stated in source)

In mobile test automation, what is the primary role of a device cloud?

  1. It provides remote access to a large pool of real devices for automated and manual test execution Correct answer.
  2. It guarantees that the app passes all compatibility tests
  3. It replaces the need for any automated test scripts
  4. It compiles the app for every target platform automatically

Explanation

A device cloud hosts many real devices that can be reserved and driven remotely, which expands coverage beyond what a team can own. It is an execution environment, not a substitute for test design or a guarantee of results. Build compilation is handled by the build pipeline, not the device cloud.

Question 5Mobile Application Testing (official domain breakdown not stated in source)

A tester wants to verify that an app correctly handles the OS killing its process while it is in the background. Which technique is most appropriate?

  1. Rotate the device repeatedly during a foreground session
  2. Run the app under a debugger with all breakpoints enabled
  3. Compare screenshots of the app in portrait and landscape
  4. Send the app to the background, force-stop it from the OS settings, then relaunch and check restored state Correct answer.

Explanation

Mobile operating systems may terminate backgrounded processes to reclaim memory, so apps must persist and restore state. Simulating that termination and relaunching verifies the app's lifecycle and persistence handling. Rotation and screenshot comparison test layout adaptation, not process death.

Question 6Mobile Application Testing (official domain breakdown not stated in source)

Why is testing on a device with a slow or unstable network important for a mobile app that synchronizes data?

  1. Because network conditions are identical across all carriers and regions
  2. Because slow networks make the app run faster on subsequent launches
  3. Because synchronization logic is only executed when the network is fast
  4. Because mobile networks vary widely and expose timeout, retry, and partial-sync defects Correct answer.

Explanation

Real mobile users encounter variable latency, packet loss, and intermittent connectivity, which stress timeout handling, retry logic, and conflict resolution. Testing under throttled or unstable conditions reveals defects that a fast lab network masks. Network conditions are not uniform, and sync logic runs regardless of speed.

Question 7Mobile Application Testing (official domain breakdown not stated in source)

A team records a UI test once and replays it on many Android and iOS devices. Which challenge is most characteristic of this cross-platform automation approach?

  1. Object locators and UI hierarchies differ between platforms, so scripts often need platform-specific abstraction Correct answer.
  2. Mobile operating systems forbid automated UI interaction
  3. Recorded scripts cannot be replayed on any device other than the recording device
  4. Replay tools eliminate the need for assertions in test scripts

Explanation

Android and iOS expose different view hierarchies and locator strategies, so a single recorded flow rarely replays unchanged across platforms. Robust frameworks abstract locators and platform differences behind a shared page or screen layer. Automation is permitted by the platforms, and assertions remain essential.

Question 8Mobile Application Testing (official domain breakdown not stated in source)

Which activity is an example of usability testing specific to mobile applications?

  1. Checking that primary actions are reachable with one thumb on a large phone screen Correct answer.
  2. Reviewing the source code for unused variables
  3. Verifying that the database schema matches the data model
  4. Confirming that the server returns HTTP 200 for the login endpoint

Explanation

Mobile usability focuses on context of use, including one-handed reachability, touch target size, and gesture discoverability on varied screen sizes. Thumb-reach checks are a characteristic mobile usability concern. Schema, endpoint, and code checks are functional or structural, not usability-focused.

Question 9Mobile Application Testing (official domain breakdown not stated in source)

An app must be tested for right-to-left languages. Which defect is most likely to be found only through RTL localization testing?

  1. A translated string exceeds the maximum length allowed by the database column
  2. Icons that imply direction, such as back arrows, still point the wrong way in RTL layout Correct answer.
  3. A background service fails to restart after a reboot
  4. A numeric field accepts letters instead of digits

Explanation

RTL localization mirrors layout direction, so directional icons, progress indicators, and alignment must be mirrored too; otherwise they mislead users. This defect class appears only when the RTL locale is exercised. String length, input validation, and service restart are unrelated to text direction.

Question 10Mobile Application Testing (official domain breakdown not stated in source)

Which statement best describes the purpose of a mobile app smoke test executed on a newly received build?

  1. It measures code coverage of the automated suite
  2. It proves the app meets all non-functional performance targets
  3. It quickly confirms that critical paths work so deeper testing is worth starting Correct answer.
  4. It replaces regression testing for the release

Explanation

A smoke test is a fast, shallow check of the most critical functions that decides whether a build is stable enough for further testing. It is a gate, not proof of quality, and it does not substitute for regression or performance testing. Coverage measurement is a separate activity.

Question 11Mobile Application Testing (official domain breakdown not stated in source)

A payment screen must be tested for security on a mobile device. Which practice most directly reduces risk of sensitive data exposure?

  1. Allowing screenshots of the payment screen in the recent-apps list
  2. Storing session tokens in plain shared preferences so tests can read them
  3. Verifying that sensitive values are masked in logs and not persisted unencrypted Correct answer.
  4. Disabling transport security so traffic can be inspected in production builds

Explanation

Mobile security testing checks that credentials and tokens are not written to logs or stored unencrypted, since rooted devices and backups can expose them. Masking and encryption reduce the attack surface. Disabling transport security or exposing screenshots increases risk rather than testing for it.

Question 12Mobile Application Testing (official domain breakdown not stated in source)

What distinguishes a hybrid mobile app from a native app in terms of testing focus?

  1. Native apps cannot be tested with automation tools
  2. Hybrid apps never require device testing
  3. Hybrid apps have no user interface to test
  4. Hybrid apps embed web content in a native container, so testing must cover both web views and native bridges Correct answer.

Explanation

Hybrid apps combine a native shell with web content, so testers must cover web rendering, JavaScript behavior, and the bridge between web and native layers. Native apps are pure platform code and are fully automatable. Both app types have UIs and require device testing.

Question 13Mobile Application Testing (official domain breakdown not stated in source)

A test analyst is estimating effort for a mobile regression suite. Which factor most increases the number of test executions required?

  1. The length of the product backlog
  2. The number of user stories written per sprint
  3. The number of supported OS versions multiplied by the number of device models in the matrix Correct answer.
  4. The number of developers on the team

Explanation

In mobile testing, the same test case often must run on each OS version and device combination in the coverage matrix, so executions scale with that product. Team size, backlog length, and story count affect planning but not the combinatorial device dimension directly.

Question 14Mobile Application Testing (official domain breakdown not stated in source)

Which is the clearest example of a battery-related non-functional test for a mobile app?

  1. Verifying that the app's icon appears on the home screen
  2. Checking that the app's login form rejects invalid passwords
  3. Measuring the app's power consumption during a one-hour background sync Correct answer.
  4. Confirming that push notifications arrive within five seconds

Explanation

Battery consumption is a non-functional attribute, and measuring power draw during realistic usage reveals wake-lock or polling defects. Login validation, icon presence, and notification latency are functional or separate performance concerns. Power measurement is the direct battery test.

Question 15Mobile Application Testing (official domain breakdown not stated in source)

A tester needs to validate that an app handles a device orientation change without losing entered form data. Which test design is most effective?

  1. Launch the app and immediately close it
  2. Install the app twice on the same device
  3. Enter data in the form, rotate the device, and verify the data and layout remain correct Correct answer.
  4. Compare the app's install size across two builds

Explanation

Configuration changes such as rotation can recreate the activity and discard unsaved state, so the test must enter data, trigger rotation, and assert both data retention and layout adaptation. Launch-close, double install, and size comparison do not exercise orientation handling.

Question 16Mobile Application Testing (official domain breakdown not stated in source)

Which statement about testing on real devices versus emulators is most accurate for evaluating touch gestures such as pinch and multi-finger swipe?

  1. Emulators cannot simulate any multi-touch input
  2. Real devices are generally needed because gesture timing and pressure behave differently from simulated input Correct answer.
  3. Gestures behave identically on emulators and real devices in all cases
  4. Touch gestures are not testable through automation

Explanation

Emulators can inject multi-touch events, but real hardware captures the timing, pressure, and physical variability that affect gesture recognition. Evaluating gesture quality therefore favors real devices, especially for complex or precise gestures. Gestures are automatable through the platform frameworks.

Question 17Mobile Application Testing (official domain breakdown not stated in source)

Why should a mobile test strategy include testing on the minimum supported OS version as well as the latest?

  1. Because older OS versions may lack newer APIs and behave differently, exposing compatibility defects Correct answer.
  2. Because the minimum version is always the most popular
  3. Because apps must run only on the latest OS version
  4. Because OS version has no effect on app behavior

Explanation

The supported range defines a compatibility contract; APIs, permissions, and rendering differ across versions, so defects often surface at the boundaries. Testing both the minimum and latest versions targets the highest-risk ends of the range. The other statements contradict how fragmentation actually behaves.

Question 18Mobile Application Testing (official domain breakdown not stated in source)

An app uses push notifications. Which test case best verifies correct behavior when the user taps a notification while the app is fully terminated?

  1. Tap the notification with the app in the foreground and check that no duplicate screen opens
  2. Disable notifications and confirm that none arrive
  3. Change the device language and confirm that notifications are translated
  4. Terminate the app, receive a notification, tap it, and verify the app launches to the correct deep-linked screen Correct answer.

Explanation

Notification handling differs by app state, and the terminated state is the most error-prone because the app must cold-start and route to the intended screen. The test therefore kills the app, delivers the notification, taps it, and asserts correct deep-link navigation. Foreground, disabled, and localization cases cover different risks.

Question 19Mobile Application Testing (official domain breakdown not stated in source)

A team wants to reduce flakiness in mobile UI automation. Which practice addresses the most common cause of intermittent failures?

  1. Replacing fixed sleeps with explicit waits for element state and synchronizing with app idleness Correct answer.
  2. Increasing the device screen brightness
  3. Adding fixed sleep statements of ten seconds before every action
  4. Running the suite only once per release

Explanation

Flakiness in mobile UI automation usually stems from timing: elements are not yet present, visible, or idle when the script acts. Explicit waits tied to element state and app idleness replace arbitrary sleeps and make tests deterministic. Fixed sleeps slow suites and still fail under variable load.

Question 20Mobile Application Testing (official domain breakdown not stated in source)

Which test is most representative of installability and upgrade testing on mobile?

  1. Installing a previous version, upgrading to the current build, and verifying user data is preserved Correct answer.
  2. Reviewing the app's privacy policy text
  3. Measuring frame rate during scrolling
  4. Checking that the app's REST API returns valid JSON

Explanation

Upgrade testing verifies that installing a new build over an older one preserves data and settings and completes cleanly. It is a core installability concern specific to distributed mobile apps. API contracts, policy text, and frame rate belong to other test types.

Question 21Mobile Application Testing (official domain breakdown not stated in source)

An app must work when the device grants only approximate location instead of precise location. Which test approach best covers this permission nuance?

  1. Test only after revoking every permission permanently
  2. Test only with all permissions granted at install time
  3. Test with precise granted, approximate granted, and permission denied, verifying graceful degradation Correct answer.
  4. Test only on emulators with mocked coordinates

Explanation

Modern mobile OS versions let users grant reduced or approximate permissions, so the app must degrade gracefully across grant levels. A matrix of precise, approximate, and denied states exposes fallback defects. Testing a single grant state or only mocked coordinates misses this behavior.

Question 22Mobile Application Testing (official domain breakdown not stated in source)

Which metric is most appropriate to assess the responsiveness of a mobile app's list scrolling under load?

  1. Frame rendering time and dropped-frame rate during scrolling Correct answer.
  2. Number of automated test cases executed per hour
  3. Number of open defects in the backlog
  4. Lines of code in the list adapter

Explanation

Responsiveness of rendering is measured in frames: frame time and dropped frames directly reflect perceived smoothness. Execution throughput, code size, and defect counts are process measures that do not describe UI responsiveness. Frame metrics are the standard performance indicator here.

Question 23Mobile Application Testing (official domain breakdown not stated in source)

A team plans to use crowdtesting for a consumer app launch. Which outcome is the most realistic benefit?

  1. Guaranteed discovery of every defect before release
  2. Complete replacement of security testing by crowd reports
  3. Diverse real-world devices, networks, and usage contexts exercised by many testers Correct answer.
  4. Elimination of the need for any in-house regression suite

Explanation

Crowdtesting brings breadth: many testers on many real devices and networks in varied contexts, which is valuable for fragmentation and usability issues. It cannot guarantee complete defect discovery and does not replace structured regression or specialist security testing. Breadth complements, rather than substitutes for, in-house testing.

Question 24Mobile Application Testing (official domain breakdown not stated in source)

Which situation best illustrates the need for testing app behavior after an OS update on a previously certified device?

  1. A developer refactors a helper class without behavior change
  2. The marketing team updates the app store description
  3. A new OS version changes background execution limits, causing the app's sync service to be killed early Correct answer.
  4. The team adds a new unit test to the repository

Explanation

OS updates can change platform behavior such as background execution, permissions, and API deprecations, so previously passing devices may regress. Re-testing after an OS update targets that risk. Store text, unit tests, and safe refactors do not represent OS-induced behavioral change.

Question 25Mobile Application Testing (official domain breakdown not stated in source)

A tester is designing tests for an app that supports dark mode. Which check is most specific to dark mode testing?

  1. Verifying that the app installs on a clean device
  2. Verifying that text and icons retain sufficient contrast against dark backgrounds Correct answer.
  3. Verifying that the login endpoint returns a token
  4. Verifying that push notifications are delivered

Explanation

Dark mode changes color schemes, so contrast, legibility, and asset rendering against dark backgrounds are the specific risks. Functional checks such as token issuance, installation, and notification delivery are independent of the theme. Contrast validation is the dark-mode-specific concern.

Question 26Mobile Application Testing (official domain breakdown not stated in source)

A tester must verify that a mobile app pauses media playback when a phone call arrives and resumes afterwards. Which test type is being performed?

  1. Localization testing
  2. Compatibility testing
  3. Performance testing
  4. Interrupt testing Correct answer.

Explanation

Interrupt testing verifies how an app behaves when the device receives competing events such as incoming calls, SMS, alarms, or low-battery alerts. The focus is on graceful pause, resume, and state retention rather than on device coverage or language support.

Question 27Mobile Application Testing (official domain breakdown not stated in source)

Which artifact is the primary input for deriving mobile test conditions during test analysis?

  1. Test conditions are derived from the device procurement budget
  2. Test conditions are derived from the test basis, such as requirements, user stories, and design documents Correct answer.
  3. Test conditions are derived from the defect density report of the development team
  4. Test conditions are derived from the execution log of the previous release

Explanation

In ISTQB terms, test analysis uses the test basis, which includes requirements, user stories, design specifications, and risk analyses, to identify test conditions. Execution logs and metrics inform later activities but do not define what must be tested.

Question 28Mobile Application Testing (official domain breakdown not stated in source)

An app stores a user's session token in plain text inside shared external storage. Which risk does this most directly create?

  1. The token will be rejected by the server because it is stored externally
  2. Another app with storage permission can read the token and impersonate the user Correct answer.
  3. The token will expire faster than a token kept in internal storage
  4. The app will fail to launch on devices without external storage

Explanation

Data stored in shared external storage may be readable by other applications that hold storage permissions, allowing token theft and session hijacking. Secure storage such as the platform keystore or private app sandbox is the expected mitigation.

Question 29Mobile Application Testing (official domain breakdown not stated in source)

Which activity belongs to test design rather than test execution in a mobile project?

  1. Logging a defect found during the login test
  2. Running the login test case on a physical device
  3. Re-running the failed login test after a fix
  4. Specifying the expected result for a login test case Correct answer.

Explanation

Test design produces test cases and their expected results from the identified test conditions. Running tests, logging defects, and retesting are execution activities.

Question 30Mobile Application Testing (official domain breakdown not stated in source)

A tester wants to confirm that a freshly built APK can be installed, launched, and used for a basic login on a clean device. Which test is most appropriate?

  1. A smoke test of the build Correct answer.
  2. A localization test of the build
  3. A stress test of the build
  4. A full regression test of the build

Explanation

A smoke test is a shallow, broad check that the critical functions work and the build is stable enough for deeper testing. It is executed on a clean install immediately after receiving a build.

Question 31Mobile Application Testing (official domain breakdown not stated in source)

Which statement correctly distinguishes verification from validation in a mobile testing context?

  1. Verification checks that the app meets user needs, while validation checks that it was built according to its specification
  2. Verification checks that the app was built according to its specification, while validation checks that it meets user needs in real use Correct answer.
  3. Verification is performed only on emulators, while validation is performed only on real devices
  4. Verification is performed by developers, while validation is performed by end users

Explanation

Verification confirms conformance to specified requirements, whereas validation confirms fitness for purpose from the user's perspective. Both can be performed by testers and on any environment.

Question 32Mobile Application Testing (official domain breakdown not stated in source)

A test manager needs to report how much of the planned mobile test suite has actually been run before a release decision. Which metric is most directly relevant?

  1. Requirement volatility
  2. Test execution progress Correct answer.
  3. Defect removal efficiency
  4. Mean time between failures

Explanation

Test execution progress compares executed tests with planned tests and directly indicates how much of the suite has run. The other metrics describe defect handling, requirement change, or reliability rather than execution coverage.

Question 33Mobile Application Testing (official domain breakdown not stated in source)

Which item is a typical entry criterion for starting system testing of a mobile release?

  1. The marketing campaign for the app has been approved
  2. The build has passed smoke testing and the test environment with target devices is available Correct answer.
  3. All defects in the project have been closed
  4. The product owner has signed the release notes

Explanation

Entry criteria define the preconditions that must hold before a test level or phase can begin, such as a stable build and an available test environment. Closing every defect or approving marketing material is not a prerequisite for system testing.

Question 34Mobile Application Testing (official domain breakdown not stated in source)

A tester writes a test case for a mobile checkout flow. Which element makes the expected result sufficiently specific?

  1. The checkout works as expected
  2. The app behaves correctly after payment
  3. The order confirmation screen displays the total of 49.99 and the order appears in the account history Correct answer.
  4. The confirmation is shown without errors

Explanation

A good expected result is observable and precise, stating concrete values and states so that pass or fail can be judged objectively. Vague phrases such as works correctly cannot be verified.

Question 35Mobile Application Testing (official domain breakdown not stated in source)

A team must test a banking app on 40 device and OS combinations but has only five physical devices. Which approach best balances risk coverage and cost?

  1. Prioritize combinations by usage analytics and risk, and use a device cloud for the remainder Correct answer.
  2. Test every combination on emulators only and skip real devices entirely
  3. Reduce the test suite to a single smoke test on all 40 combinations
  4. Test only the newest flagship device and assume the others behave the same

Explanation

Risk-based prioritization combined with cloud device access concentrates effort on the most likely and most damaging combinations while still covering the rest. This addresses both coverage and budget constraints.

Question 36Mobile Application Testing (official domain breakdown not stated in source)

A test case must verify that a user can complete a purchase when the app is offline and the transaction syncs after connectivity returns. Which test technique is most suitable for designing the connectivity scenarios?

  1. Equivalence partitioning of screen resolutions
  2. Boundary value analysis on the price field
  3. Pairwise testing of font sizes
  4. Decision table testing over connectivity and authentication states Correct answer.

Explanation

A decision table models combinations of conditions such as online or offline and authenticated or not, producing the rules that determine expected sync behavior. The other techniques address numeric boundaries, display attributes, or configuration pairing.

Question 37Mobile Application Testing (official domain breakdown not stated in source)

A tester finds that a defect occurs only on devices running the oldest supported OS version. What is the most appropriate next action?

  1. Downgrade the app so it no longer supports the oldest OS version
  2. Close the defect because the latest OS works correctly
  3. Record the OS version, device model, and steps in the defect report so it can be reproduced Correct answer.
  4. Report the defect without environment details to keep the report short

Explanation

A defect report must contain enough environment information for developers to reproduce the failure. OS version and device model are essential for defects that are configuration-specific.

Question 38Mobile Application Testing (official domain breakdown not stated in source)

Which pairing of test level and typical mobile test objective is correct?

  1. Component testing verifies an individual module such as a payment calculation unit Correct answer.
  2. Acceptance testing verifies internal code structure
  3. Component testing verifies end-to-end user journeys across the app and backend
  4. System testing verifies a single function in isolation

Explanation

Component testing targets isolated units such as a calculation module, while system and acceptance testing address integrated behavior and business needs. Matching levels to their objectives is a core part of test planning.

Question 39Mobile Application Testing (official domain breakdown not stated in source)

A mobile app displays prices with two decimals in English but shows the wrong currency symbol and grouping in some locales. Which test approach most efficiently finds such defects?

  1. Increase the number of devices while keeping the locale fixed
  2. Run the purchase scenario once with the default device settings
  3. Run the same purchase scenario with locale and currency settings varied across supported markets Correct answer.
  4. Repeat the purchase scenario many times to check for flakiness

Explanation

Localization defects appear only when locale and currency settings change, so test data must vary those inputs. Repeating the same configuration or adding devices without varying locale will not expose formatting problems.

Question 40Mobile Application Testing (official domain breakdown not stated in source)

A test analyst must select test cases for a regression suite before a minor mobile bug-fix release. Which selection basis is most defensible?

  1. All test cases ever written for the app, regardless of relevance
  2. Only the test cases that passed most recently
  3. Tests covering changed areas, high-risk functions, and previously failing features Correct answer.
  4. Test cases chosen at random to save analysis time

Explanation

Regression selection should be driven by change impact and risk, including areas with a history of defects. This keeps the suite focused while protecting the most important behavior.

Question 41Mobile Application Testing (official domain breakdown not stated in source)

A team wants to know whether a new onboarding flow reduces the drop-off rate compared with the previous flow. Which approach provides the strongest evidence?

  1. A usability inspection performed by one designer
  2. A code review of the new onboarding screens
  3. A unit test of the onboarding validation logic
  4. An A/B test comparing completion rates of the two flows with real users Correct answer.

Explanation

An A/B test measures actual user behavior and completion rates for both variants, providing quantitative evidence of the effect. Reviews, unit tests, and single-expert inspections do not measure real user drop-off.

Question 42Mobile Application Testing (official domain breakdown not stated in source)

Which practice best supports traceability between mobile requirements and test cases?

  1. Recording only the execution status of each test case
  2. Storing all test cases in a spreadsheet without requirement references
  3. Naming test cases after the tester who wrote them
  4. Assigning a unique identifier to each requirement and referencing it in the related test cases Correct answer.

Explanation

Traceability requires a stable identifier on each requirement that is referenced by the tests covering it, enabling coverage analysis and impact assessment. Naming conventions or status records alone do not link tests to requirements.

Question 43Mobile Application Testing (official domain breakdown not stated in source)

A tester must decide whether a crash found during exploratory testing of a beta build is worth reporting immediately. Which factor is most relevant to that decision?

  1. The date on which the module was originally written
  2. The seniority of the tester who found the crash
  3. The severity of the impact on users and how frequently the crashing path is likely to be taken Correct answer.
  4. The number of lines of code in the crashing module

Explanation

Prioritizing a defect depends on its impact on users and the likelihood of the failing scenario occurring. Code size, tester seniority, and module age do not indicate business or user risk.

Question 44Mobile Application Testing (official domain breakdown not stated in source)

Which test case most directly verifies that a mobile app respects the platform's permission model for camera access?

  1. Deny camera permission and confirm the app explains the limitation and offers no camera features Correct answer.
  2. Rotate the device while the camera preview is open
  3. Grant camera permission and confirm that a photo can be taken
  4. Open the camera screen on three different device models

Explanation

Permission-model testing focuses on the denied and restricted paths, verifying that the app degrades gracefully and informs the user. The granted path is normal functionality rather than permission handling.

Question 45Mobile Application Testing (official domain breakdown not stated in source)

A mobile game runs smoothly for ten minutes and then gradually slows down until it is killed by the OS. Which type of testing is most likely to reveal the cause?

  1. Localization testing of in-game text
  2. Long-duration soak testing with memory and resource monitoring Correct answer.
  3. Compatibility testing across screen sizes
  4. Functional testing of the game menu

Explanation

Gradual degradation over time suggests a resource leak, which soak or endurance testing with monitoring is designed to expose. Functional, localization, and compatibility tests do not run long enough or measure resource trends.

Question 46Mobile Application Testing (official domain breakdown not stated in source)

A team must test an app that uses biometric login on devices where the biometric sensor is temporarily locked after too many failed attempts. Which test design element is essential?

  1. A step that disables the device screen lock entirely
  2. An expected result that the app crashes safely
  3. A precondition that sets the sensor to the locked state and an expected fallback to passcode or password Correct answer.
  4. A precondition that the user has never enrolled a biometric

Explanation

The scenario requires reproducing the locked-sensor state and verifying the documented fallback authentication path. Without that precondition and expected fallback, the test cannot exercise the intended behavior.

Question 47Mobile Application Testing (official domain breakdown not stated in source)

A test manager observes that the same UI automation test passes on one device cloud run and fails on the next with no code change. Which action best addresses this root cause class?

  1. Investigate synchronization and wait strategy, then replace fixed sleeps with condition-based waits Correct answer.
  2. Mark the test as passed whenever it fails intermittently
  3. Add more devices to the cloud to average out the failures
  4. Rewrite the test in a different programming language

Explanation

Intermittent mobile UI failures are commonly caused by timing and synchronization problems, so replacing fixed sleeps with explicit condition-based waits addresses the underlying cause. Averaging, ignoring, or rewriting does not fix synchronization.

Question 48Mobile Application Testing (official domain breakdown not stated in source)

A regulated app must demonstrate that testing followed a documented process with approvals at each stage. Which test work product is most important to maintain?

  1. A test plan with defined entry and exit criteria, approvals, and traceability records Correct answer.
  2. An informal chat log of daily testing discussions
  3. A list of tester preferences for device models
  4. A screenshot gallery of the app on various devices

Explanation

Auditable processes require documented plans, criteria, approvals, and traceability that show what was decided and verified. Screenshots, preferences, and informal chats do not evidence controlled process adherence.

Question 49Mobile Application Testing (official domain breakdown not stated in source)

A team must decide whether a defect found only on a device with a notched display and gesture navigation is a product risk or a test environment issue. Which analysis is most sound?

  1. Classify it as a product defect immediately because any failure is a defect
  2. Classify it as a test environment issue because only one device showed it
  3. Ignore it because notched displays are a minority of the market
  4. Confirm reproduction on a second device with the same display and navigation characteristics before classifying it as a product defect Correct answer.

Explanation

Before classifying a configuration-specific failure as a product defect, the tester should confirm it reproduces on comparable hardware to rule out a faulty device or setup. This distinguishes genuine product risk from environment noise.

Question 50Mobile Application Testing (official domain breakdown not stated in source)

An app supports both light and dark themes and uses custom-drawn charts. Which test approach best targets theme-specific rendering defects?

  1. Capture and compare chart rendering in both themes at defined states, checking contrast and color-dependent data series Correct answer.
  2. Verify that the theme toggle changes the setting value
  3. Check that the app installs correctly with the dark theme selected
  4. Run the chart test once in the default theme

Explanation

Theme-specific rendering defects appear as poor contrast or indistinguishable data series, so visual comparison across both themes at defined states is needed. Merely toggling a setting or testing one theme cannot reveal them.