1000*2=2000, 2000*2=4000, 3000*2=6000. All within range, no overflow.
Step 3: Re-evaluate multiplication and overflow
Actually, 3000*2=6000 is within int16 range, but 3000*2=6000 is correct. However, the original code output is [-11272 -9520 -7120] due to overflow because 3000*2=6000 is within range, but 1000*2=2000, 2000*2=4000, 3000*2=6000 are all within range. So the output should be [2000 4000 6000].
Final Answer:
[2000 4000 6000] -> Option D
Quick Check:
Multiplied values within int16 range [OK]
Hint: Check if multiplied values fit dtype range [OK]
Common Mistakes:
Assuming overflow always happens
Confusing int16 range limits
Expecting error on multiplication
4. The following code causes unexpected results. What is the main issue?
A. int8 dtype cannot hold values larger than 127, causing overflow.
B. The array should be created with dtype='float32' instead.
C. The array elements must be strings, not integers.
D. NumPy arrays cannot have negative values.
Solution
Step 1: Check int8 value limits
int8 stores values from -128 to 127. Values 300, 400, 500 exceed this range.
Step 2: Understand overflow effect
Values wrap around due to overflow, causing unexpected negative or incorrect numbers.
Final Answer:
int8 dtype cannot hold values larger than 127, causing overflow. -> Option A
Quick Check:
int8 max 127, overflow if exceeded [OK]
Hint: Check dtype range before assigning large values [OK]
Common Mistakes:
Thinking float32 fixes integer overflow
Believing array elements must be strings
Assuming NumPy disallows negatives
5. You have a large dataset of 1 million numbers ranging from 0 to 255. Which dtype choice will optimize memory and performance without losing data accuracy?
hard
A. Use dtype='int64' for maximum integer size.
B. Use dtype='float64' to handle all numbers precisely.
C. Use dtype='uint8' since it covers 0 to 255 exactly.
D. Use dtype='bool' to save memory.
Solution
Step 1: Analyze data range and dtype options
Data ranges from 0 to 255, which fits exactly in unsigned 8-bit integer (uint8).
Step 2: Choose dtype that fits range and saves memory
uint8 uses 1 byte per number, saving memory and speeding up calculations compared to int64 or float64.
Step 3: Exclude unsuitable options
int64 and float64 use more memory than needed; bool cannot store numbers beyond 0 or 1.
Final Answer:
Use dtype='uint8' since it covers 0 to 255 exactly. -> Option C
Quick Check:
uint8 fits 0-255 perfectly, best for memory [OK]
Hint: Match dtype range exactly to data range [OK]
Common Mistakes:
Choosing larger dtypes unnecessarily
Using float for integer-only data
Using bool for numeric data
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.