Sample questions
Mq Network Conditioning Offline ValidationDifficulty 1
On the Android emulator, launching with -netdelay umts -netspeed umts does what?
- aApplies UMTS-level latency/throughput as a named preset✓
- bBlocks all outbound traffic except DNS lookups
- cForces the emulator to use the host's real cellular modem
- dDisables Wi-Fi so only the emulated radio is active
Explanation:-netdelay only accepts a small set of named profiles (gprs, edge, umts, none) — narrower than -netspeed's set (gsm, hscsd, gprs, edge, umts, hsdpa, lte, evdo, full); gsm is valid for -netspeed but not for -netdelay. Both flags apply a rough latency/bandwidth envelope at boot — they don't touch DNS, real modems, or Wi-Fi.
Mq Network Conditioning Offline ValidationDifficulty 2
Running adb shell svc wifi disable on a test device does which of these?
- aPuts the device fully in airplane mode, disabling every radio
- bOnly blocks Wi-Fi traffic for the app under test, leaving other apps connected
- cTurns off the Wi-Fi radio via the system's connectivity service✓
- dEnables Wi-Fi if it was previously off, acting as a toggle
Explanation:svc wifi disable/enable calls the system ConnectivityService directly, exactly like the Settings toggle — it is a one-way command (disable or enable), not a per-app filter and not a full airplane-mode switch.
Mq Network Conditioning Offline ValidationDifficulty 2
To fully enable airplane mode from adb (not just Wi-Fi), why is adb shell settings put global airplane_mode_on 1 alone usually not enough?
- aThe command requires root and silently fails without it
- bIt only works on physical devices, never on emulators
- cThe radios don't react until the airplane-mode broadcast intent is also sent✓
- dIt disables Wi-Fi but leaves mobile data always on regardless
Explanation:Since Android 4.2, just flipping the global setting doesn't move the radios; you also need am broadcast -a android.intent.action.AIRPLANE_MODE --ez state true so the system actually applies it — a common gotcha in scripted network-conditioning setups.
Mq Network Conditioning Offline ValidationDifficulty 1
What is the iOS Network Link Conditioner primarily used for in mobile testing?
- aRecording every HTTP request the app makes to disk for later replay
- bSimulating latency, bandwidth caps, and packet loss system-wide✓
- cRewriting DNS responses for a specific bundle identifier
- dAutomatically retrying failed requests inside the app under test
Explanation:It's a system-level traffic-shaping tool (a Developer Settings toggle on-device, or a preference pane on macOS) that applies a chosen profile's latency/bandwidth/loss characteristics to all network traffic, not just one app.
Mq Network Conditioning Offline ValidationDifficulty 2
Selecting the "100% Loss" profile in Network Link Conditioner during a test means what for the app?
- aEvery packet on the shaped link is dropped✓
- bEvery request succeeds but responses are delayed by a fixed large amount
- cOnly DNS resolution fails while TCP connections still succeed
- dHalf of all requests are dropped at random, simulating an unstable link
Explanation:100% Loss simulates total packet loss on the shaped link — the profile teams use to exercise pure offline handling without physically toggling airplane mode.
Mq Network Conditioning Offline ValidationDifficulty 2
To intercept a mobile app's HTTPS traffic with mitmproxy or Charles running on a laptop, what must be configured on the device first?
- aThe app's build must be recompiled with a hardcoded proxy address
- bPoint the device's Wi-Fi proxy at the laptop's IP and port✓
- cThe device must be rooted or jailbroken before any proxying is possible
- dThe laptop must be on a different subnet than the device
Explanation:Setting the device's Wi-Fi proxy to the proxy tool's IP:port routes the app's HTTP(S) traffic through it — no root/jailbreak or app rebuild is required just to route traffic (decrypting HTTPS needs a separate CA cert step).