M06 SELF-CHECK

Sources, interfaces, and evidence-based debugging

Five questions · 4/5 to pass · unlimited retry

1. Why must a chip supply limit and a breakout Vin allowance retain their object names?
2. What does a host replay establish in Sensor Monitor?
3. An assistant says that calling a sensor adapter every second proves the adapter returns within one second. What should you do?
4. The fixture parser rejects 28C. Which experiment best tests whether the token violates the existing numeric format?
5. A CP05 sample record has state FAULT, error recovering, and a fresh numeric temperature. What should the reporting exercise's current Boolean be?

Your result

Not attempted

Read the correct answers and explanations

Question 1

They can describe different connection points and supporting circuitry.

A chip document and a breakout guide can both be correct while describing different scopes. Identify the object, connection point, units, and conditions before applying a value.

Question 2

Shared software behavior for the supplied synthetic inputs and timestamps.

Replay executes actual shared logic with controlled software input. Compilation and physical observations are separate evidence categories.

Question 3

Separate scheduling from execution duration and inspect the driver's timeout behavior.

A scheduler decides when to request work. It does not establish the duration or timeout of the called driver. Failed input must not become an invented measurement.

Question 4

Change only a copied fixture's token to 28, run it, and confirm the original remains rejected.

The controlled copy changes the suspected input while holding the code contract constant. Rejection of the original confirms that malformed syntax was not silently accepted.

Question 5

true, because data is fresh while two-sample recovery is still incomplete.

The current flag describes availability/freshness, while state also includes recovery readiness. Use Snapshot.current directly and emit an unquoted JSON Boolean.