feat(logs): add mcq (#145)

Author: amyheather

pages/guide/model/logs.qmd

@@ -1687,6 +1687,54 @@ print(log_contents, sep = "\n")
 
 ## Test yourself
 
+<div class="h3-tight"></div>
+
+### Quiz
+
+```{r}
+#| echo: false
+library(webexercises) # nolint: library_call_linter
+```
+
+::: {.callout-note}
+
+## Why are logs useful when building and verifying a DES model?
+
+```{r}
+#| output: asis
+#| echo: false
+cat(longmcq(c(
+  answer = paste0(
+    "They let you see when key events occur (e.g. arrivals, consultations), ",
+    "helping you spot bugs and check that the model behaves as intended."
+  ),
+  "They replace the need for any formal validation or testing."
+)))
+```
+
+:::
+
+::: {.callout-note}
+
+## Why is logging designed to be optional, rather than always on?
+
+```{r}
+#| output: asis
+#| echo: false
+cat(longmcq(c(
+  "Because logs are only useful during sensitivity analysis.",
+  "Because DES models cannot run correctly if any logging is enabled.",
+  answer = paste0(
+    "Because detailed logs are helpful for short test runs and debugging but ",
+    "would be excessive and slow for long runs or many replications."
+  )
+)))
+```
+
+:::
+
+### Activity
+
 Try **adding logs to your model**. Experiment with different log messages and parameter options, then run your code and observe how the logs reflect your changes at each step.
 
 If you extend your model (for example, with different patient types, destinations, or additional resources), continue making use of logs. Logging is especially valuable during **model development** - it helps you check that each part of your logic works as intended and makes it easier to troubleshoot issues as your simulation grows in complexity.