What is the rule about block altitude in data management?

• A. It must not be compressed
• B. It may be compressed
• C. It must be increased frequently
• D. It must be kept secret

Answer: (A)

Block altitude data must remain uncompressed. This altitude value is a precise piece of metadata that many systems rely on for exact calculations, indexing, and deterministic processing. If you compress it, you introduce the extra step of decompression to read the value, which adds latency and can create mismatches if different decompression methods are used or if integrity checks assume the original bit pattern. Keeping the altitude uncompressed preserves the exact representation of the data, avoids potential timing or fidelity issues, and fits a design that treats this field as critical for correct operation. The other statements don’t fit: changing altitude data to reflect frequent increases isn’t a general storage rule, and secrecy isn’t the concern here—it's about preserving exact value and quick, reliable access.