Fixed issue #224 - provide answers to the questions

Author: rcastley

content/en/s4r/3-quick-tour/3-apm-home/2-apm-home.md

@@ -24,7 +24,14 @@ To easily differentiate between multiple applications, Splunk uses **environment
 
 * Verify that the time window we are working with is set to the last 15 minutes (**-15m**).
 * Change the environment to the workshop one by selecting its name from the drop-down box and make sure that is the only one selected.
-* What can you conclude from the **Top Services by Error Rate** chart?
+{{< tabs >}}
+{{% tab title="Question" %}}
+**What can you conclude from the *Top Services by Error Rate* chart?**
+{{% /tab %}}
+{{% tab title="Answer" %}}
+**The *paymentservice* has a high error rate**
+{{% /tab %}}
+{{< /tabs >}}
 <!--
 * Click on the Explore Tile in the Function Pane. This will bring us to the automatically generated map of our services. This map shows how the services interact together based on the trace data being sent to Splunk Observability Cloud.
 -->

content/en/s4r/3-quick-tour/5-synthetics-home/2-synthetics-home.md

@@ -24,7 +24,14 @@ To continue our tour, let's look at the result of our workshop's automatic brows
 
 * Note, On the Synthetic Tests Page, the first pane will show the performance of your site for the last day, 8 days and 30 days. As shown in the screenshot above, only if a test started far enough in the past, the corresponding chart will contain valid data. For the workshop, this depends on when it was created.
 * In the Performance KPI drop-down, change the time from the default 4 hours to the 1 last hour.  
-* What can you conclude from the dotted chart, how often are these tests run, and from where?
+{{< tabs >}}
+{{% tab title="Question" %}}
+**How often is the test run, and from where?**
+{{% /tab %}}
+{{% tab title="Answer" %}}
+**The test runs at a 1-minute round robin interval from Frankfurt, London and Paris**
+{{% /tab %}}
+{{< /tabs >}}
 {{% /notice %}}
 
 Now let’s examine the infrastructure our application is running on using **Splunk Infrastructure Monitoring (IM)**.

content/en/s4r/5-rum/1-rum-dashboard.md

@@ -16,18 +16,18 @@ Make sure you select your workshop by ensuring the drop-downs are set/selected a
 
 Next, click on the **[NAME OF WORKSHOP]-workshop** above the **Page Views / JavaScript Errors** chart.
 
-This will bring up a dashboard view breaking down the metrics by **UX Metrics**, **Front-end Health**, **Back-end Health** and **Custom Events** and compares them to  the same metrics historically (1 hour by default). <!-- For more detailed information on the metrics collected by Splunk RUM see [**here**](https://docs.splunk.com/observability/en/gdi/get-data-in/rum/browser/rum-browser-data-model.html#rum-browser-data). -->
+This will bring up a dashboard view breaking down the metrics by **UX Metrics**, **Front-end Health**, **Back-end Health** and **Custom Events** and compares them to the same metrics historically (1 hour by default). <!-- For more detailed information on the metrics collected by Splunk RUM see [**here**](https://docs.splunk.com/observability/en/gdi/get-data-in/rum/browser/rum-browser-data-model.html#rum-browser-data). -->
 
 ![RUM Dashboard](../images/rum-dashboard.png)
 
-* **UX Metrics**, This tab groups the *Web vitals* an other user interface metrics together.  
+* **UX Metrics**, This tab groups the *Web vitals* and other user interface metrics.
 * **Front-end Health**, This tab shows metrics regarding how the website behaved in the browsers.  
-* **Back-end Health**, In this tab you can find thh metric related to overall network behavior.
+* **Back-end Health**, In this tab you can find the metric related to overall network behavior.
 * **Custom Events**, In this tab we find metrics related to Custom Events added to the website by the developer to track behaviour.
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 
 * Click through each of the tabs (**UX Metrics**, **Front-end Health**, **Back-end Health** and **Custom Events**)
-* Find the chart that clearly show there is an issue with the application. (Hint, its a Custom Event)
+* Find the chart that clearly shows there is an issue with the application. Hint, it's a Custom Event.
 
 {{% /notice %}}

content/en/s4r/6-apm/2-apm-service-dashboard.md

@@ -22,8 +22,14 @@ We will be using these charts later on in the workshop. Click the back button in
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 
-* In the Service Map hover over the **paymentservice**. What can you conclude from the popup service chart?
-
+{{< tabs >}}
+{{% tab title="Question" %}}
+**In the Service Map hover over the **paymentservice**. What can you conclude from the popup service chart?**
+{{% /tab %}}
+{{% tab title="Answer" %}}
+**The error percentage is very high.**
+{{% /tab %}}
+{{< /tabs >}}
 {{% /notice %}}
 
 ![APM Service Chart](../images/apm-service-popup-chart.png)

content/en/s4r/6-apm/3-apm-tag-spotlight.md

@@ -13,8 +13,14 @@ Request/Error charts display the total number of requests, errors, and root caus
 
 {{% notice title="Exercise" style="green" icon="running" %}}
 
-* What can you conclude from the data you are seeing?
-* Which chart helped you come to this conclusion?
+{{< tabs >}}
+{{% tab title="Question" %}}
+**Which chart exposes the tag that identifies what the problem is?**
+{{% /tab %}}
+{{% tab title="Answer" %}}
+**The *version* chart. The number of requests against `v350.10` matches the number of errors.**
+{{% /tab %}}
+{{< /tabs >}}
 
 {{% /notice %}}
 

content/en/s4r/6-apm/4-apm-service-breakdown.md

@@ -15,7 +15,14 @@ More story here ...
 * Click on **gold** to select it.
 * Click on {{% button style="grey"  %}}Breakdown{{% /button %}} and select `version`.
 * Repeat this for **silver** and **bronze**.
-* What can you conclude from what you are seeing?
+{{< tabs >}}
+{{% tab title="Question" %}}
+**What can you conclude from what you are seeing?**
+{{% /tab %}}
+{{% tab title="Answer" %}}
+**Every tenant is being impacted by `v350.10`**
+{{% /tab %}}
+{{< /tabs >}}
 
 {{% /notice %}}
 
@@ -26,8 +33,7 @@ You will now see the **paymentservice** broken down by `tenant.level` and each t
 {{% notice title="Exercise" style="green" icon="running" %}}
 
 * Click on any one of the red dotted lines coming from the **checkoutservice** to `v350.10`.
-* Take a look at the **Service-to-Service Requests & Errors** chart.
-* What percentage of errors are there?
+* Repeat the same for `v350.9` and notice the difference in the error rate.
 
 {{% /notice %}}
 

content/en/s4r/6-apm/6-apm-waterfall.md

@@ -12,7 +12,14 @@ Each span in Splunk APM captures a single operation. Splunk APM considers a span
 {{% notice title="Exercise" style="green" icon="running" %}}
 
 * Click on the {{% button style="red"  %}}!{{% /button %}} next to the **paymentservice** span in the waterfall.
-* What is the error message being reported in the span metadata?
+{{< tabs >}}
+{{% tab title="Question" %}}
+**What is the error message being reported in the span metadata?**
+{{% /tab %}}
+{{% tab title="Answer" %}}
+**Invalid request**
+{{% /tab %}}
+{{< /tabs >}}
 
 {{% /notice %}}
 

content/en/s4r/7-log-observer/2-log-entry.md

@@ -39,9 +39,16 @@ graph LR;
 {{% notice title="Exercise" style="green" icon="running" %}}
 
 * Click on an error entry in the log table (make sure it says `hostname: "paymentservice-xxxx"` in case there is a rare error from a different service in the list too.
-* Based on the message, what would you tell the development teams to fix in order to resolve the issue?
-
-  ![Log Message](../images/log-observer-log-message.png)
+{{< tabs >}}
+{{% tab title="Question" %}}
+**Based on the message, what would you tell the development teams to do to resolve the issue?**
+{{% /tab %}}
+{{% tab title="Answer" %}}
+**Either fix the issue in `v350.10` or rollback to `v350.9`**
+{{% /tab %}}
+{{< /tabs >}}
+
+![Log Message](../images/log-observer-log-message.png)
 
 {{% /notice %}}