Nordlicht Reisen GmbH, a fictional travel agency, has an ARM template in JSON format from lesson 3.1. New templates, however, are to be written in Bicep, because the files are easier to read. You are to convert the old template to Bicep, adapt the Bicep file and deploy it. The exam names exactly this: read, change and deploy a Bicep file and convert an ARM template to Bicep.
Prior knowledge. K3 module 3.2 teaches the Bicep language (lesson 3.2.2), modules and reuse (3.2.3), and what-if and its limits (3.2.4). This lesson doesn't repeat that. It covers what the exam requires: reading, changing, deploying, exporting and converting files. The ARM template itself and the deployment modes are covered in lesson 3.1 of this course.
Bicep and ARM: a connection
Microsoft describes Bicep as a transparent abstraction over the ARM template. At deployment, the Bicep program translates the file into an ARM template in JSON format. Everything that is valid in a template (resource types, API versions, properties) is also valid in Bicep. Bicep manages dependencies between resources itself when a resource uses the symbolic name of another; dependsOn is then usually unnecessary. Parameters, variables and outputs may appear anywhere in the file, not only in a fixed section.