releasable example exam

Author: Snooz82

website/docs/example-exam/Example-exam.mdx

@@ -1,10 +1,7 @@
 import Quiz from '@site/src/components/Quiz/Quiz';
 
-# Test the features thing
+# Example Questions
 
-<Quiz name="TestExample" src="test.md"/>
-
-
-# Example Questions from Pieter
+This example exam should give you the oportunity to check you knowledge and to get an impression what kind of questions may be asked in the real examination for RFCP®.
 
 <Quiz name="Example" src="Example.md"/>

website/src/components/Quiz/quizComponents.ts

@@ -1,6 +1,6 @@
 /*
 * This file is automatically generated and will be overridden when running the build process.
-* Generated on: 11/1/2025, 11:13:28 PM
+* Generated on: 11/22/2025, 1:09:21 PM
 */
 
 export interface QuizPage {
@@ -20,11 +20,6 @@ export const quizPages: QuizPage[] = [
     "id": "docs-example-exam",
     "name": "example-exam",
     "quizzes": [
-      {
-        "id": "example-exam#testexample",
-        "name": "TestExample",
-        "src": "test.md"
-      },
       {
         "id": "example-exam#example",
         "name": "Example",

website/static/quizzes/Example.md

@@ -1,6 +1,6 @@
 ---
 shuffleQuestions: false
-shuffleAnswers: false
+shuffleAnswers: true
 ---
 
 ### Which THREE of the following statements about Robot Framework are correct?
@@ -21,12 +21,14 @@ shuffleAnswers: false
 
 - [ ] Use of complex nested structures is not possible.
     > Robot Framework avoids complex nested structures but they can be used.
-- [ ] Use of specialized symbols and character sequences.
-    > Specialized symbols and character sequences are kept to a minimum.
-- [X] Use of natural language-like keywords.
+- [ ] Focus on the use of specialized symbols and character sequences as syntax.
+    > Specialized symbols and character sequences are kept to a minimum to improve readability. Robot Framework emphasizes clarity over complexity.
+- [X] String first syntax where all arguments are strings unless explicitly stated otherwise.
+    > Unquoted strings are considered as strings, while variables need special syntax like `{variable}` or integers like `${42}`.
 - [ ] There are no programming control flows such as if statements and for loops.
-    > Control flows are present in Robot Framework but a lot can be done without them.
-- [X] Reliance on a tabular format.
+    > Control flows are present in Robot Framework as described in `LO-5.2.X` .
+- [X] Reduced use of special characters.
+    > Compared to programming languages the focus is on reducing special characters, making the syntax human-readable and user-friendly.
 
 ### Which of the following statements is TRUE for `*** Test Cases ***` or `*** Tasks ***` section?
 
@@ -61,13 +63,16 @@ shuffleAnswers: false
 
 > LO-2.3.2 Explain the execution artifacts generated by Robot Framework.
 
-- [ ] Configuration files
+- [ ] Configuration files (`robot.yaml`)
     > Configuration files are not generated as a result of test execution, but are rather part of the project setup and development.
-- [x] Log files
-- [ ] Resource files
+- [x] Log files (`log.html`)
+    > A detailed log file that provides an HTML view of the execution, including keyword-level details.
+- [ ] Resource files (`keywords.resource`)
     > Resource files are used by Robot Framework but are not created as execution artifacts; they are components used by tests.
-- [x] Report files
-- [x] Output files
+- [x] Report files (`report.html`)
+    > A summary report that gives an overview of the execution results, including statistics of tests|tasks executed, passed, and failed.
+- [x] Output files (`output.xml`)
+    > A machine-readable file containing ALL logged execution details, limited by the given log-level.
 
 
 ### Match the correct prefixes to different variable access types
@@ -76,29 +81,32 @@ shuffleAnswers: false
 
 Given the following prefixes:
 ```
-1. @
-2. $
-3. %
-4. &
+1. `@`
+2. `$`
+3. `%`
+4. `&`
 ```
-Put the list below in the correct order to match the given prefixes
+
+Match the variable prefixes to their correct descriptions:
+
+_(Use Drag&Drop to match)_
 
 1. Store multiple values in a list structure
 2. Store values as a single entity
 3. Read access to an environment variable.
 4. Store key-value pairs in a dictionary structure.
 
 
-### Which TWO of the following statements are key characteristics of Test|Task|Teardown
+### Which TWO of the following statements are key characteristics of `Test Teardown` and `Task Teardown` ?
 
 > LO-4.2.2-1 Recall key characteristics, benefits, and syntax of Test|Task Teardown
 
-- [x] When Test|Task Teardown fails, the test|task is marked as failed in reports and logs.
-- [ ] Test|Task Teardown runs only when the Test|Task passes.
-    > Runs always.
-- [x] All keywords within the Test|Task Teardown are executed, even when one of them fails.
-- [ ] Test|Task Teardown must be set separately for each test|task.
-    > Can be set glob
+- [x] When `Test|Task Teardown` fails, the test|task is marked as failed in reports and logs.
+- [ ] `Test|Task Teardown` runs only when the Test|Task passes.
+    > Teardowns run always, even if a preceding keyword fails.
+- [x] All keywords within the `Test|Task Teardown` are executed, even when one of them fails.
+- [ ] `Test|Task Teardown` must be set separately for each test|task.
+    > You can use the setting `Test Teardown` or `Task Teardown` in the `*** Settings ***` section to define a teardown for all tests|tasks in the suite which do not have a locally define Teardown with the `[Teardown]` setting.
 
 
 
@@ -107,19 +115,19 @@ Put the list below in the correct order to match the given prefixes
 > LO-4.4 Recall the purpose of Test|Task Tags in Robot Framework
 
 1. [ ] Tags are case-sensitive labels used for grouping suites and tests|tasks.
-    > Tags are case-insensitive and only used for tests|tasks.
+    > Tags are case-insensitive and only used for tests|tasks or keywords.
 1. [ ] Tags are assigned to suites to create statistical summary of the suite results.
-    > Assigned to tests|tasks.
-1. [x] "Tags offer a simple mechanism for classifying and controlling the execution of tests|tasks."
-1. [ ] "Only pre-defined tags, such as `smoke`, `regression`, and `critical` can be assigned to tests|tasks"
+    > Tags are assigned to tests|tasks, not to suites, even though a default can be configured in the suite setting, which result in automatic tagging of all tests|tasks within that suite.
+1. [x] Tags offer a simple mechanism for classifying and controlling the execution of tests|tasks.
+1. [ ] Only pre-defined tags, such as `smoke`, `regression`, and `critical` can be assigned to tests|tasks
     > Tags are free-form text labels.
 
 
 ### In the given scenario which of the test cases logs only a single entry
 
-__Read__ the keyword explaination carefully to understand the given scenario!
+_Read_ the keyword explaination carefully to understand the given scenario!
 
-#### Log Many
+## _Keyword:_ Log Many
 
 **Arguments**
 
@@ -133,7 +141,7 @@ Logs the given messages as separate entries using the INFO level.
 Supports also logging list and dictionary variable items individually.
 ```
 
-#### Variables
+## _Variables_:
 
 The following Variables are available to each test case.
 
@@ -177,10 +185,10 @@ The following Variables are available to each test case.
 
 > LO-5.1.6 Recall that Robot Framework provides access to execution information via Built-In variables
 
-1. [ ] "It is an absolute path to the directory where the current suite or resource file is located."
+1. [ ] An absolute path to the directory where the current suite or resource file is located.
     > Description for `${CURDIR}`
-1. [x] It is an absolute path to the directory where test execution was started from.
-1. [ ] It is an absolute path to the directory where output files are written.
-    > Description for `${OUTPUT_DIR}`.
-1. [ ] It is an absolute path to the system temporary directory.
+1. [x] An absolute path to the directory where test execution was started from.
+1. [ ] An absolute path to the directory where output files are written.
     > Description for `${OUTPUT_DIR}`.
+1. [ ] An absolute path to the system temporary directory.
+    > Description for `${TEMPDIR}`.