React Native Risk Assessment & Management 4

Question 1

What risk arises from using `console.log` statements in a production React Native build?

Accepted Answer

Sensitive data may be exposed in device logs and it degrades JS thread performance

Answer

Production logs can leak sensitive data and incur unnecessary JS thread overhead; they should be stripped via Babel transforms.

Question 2

A React Native app's CI pipeline runs only unit tests with mocked native modules. What risk does this testing strategy leave unaddressed?

Accepted Answer

Integration failures between JavaScript code and actual native module implementations on real devices

Answer

Mocked native modules cannot detect mismatches between the JS bridge contract and the actual native implementation, requiring device/emulator testing.

Question 3

Which risk does using a single shared Redux store for all screens in a large React Native app introduce?

Accepted Answer

Unrelated state changes can trigger unnecessary re-renders across the entire component tree

Answer

A monolithic store with poorly-memoized selectors causes cascading re-renders; use `reselect` and split reducers to isolate state changes.

Question 4

What is the primary risk of not code-signing a React Native Android release APK before distributing it outside the Play Store?

Accepted Answer

Users receive no integrity guarantee — the APK could be tampered with and repackaged with malware

Answer

Unsigned or improperly-signed APKs have no cryptographic integrity guarantee, enabling trivial repackaging attacks.

Question 5

Which approach best mitigates the risk of React Native's JavaScript thread being blocked by heavy computation?

Accepted Answer

Offload CPU-intensive work to a Web Worker via react-native-workers or a native module

Answer

Moving CPU-heavy work off the JS thread prevents frame drops and UI freezes caused by blocking the single-threaded JS runtime.

React Native Practice Test

React Native Practice Test

React Native Risk Assessment & Management 4