# Next Steps

## In this learning path

- [Introduction](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-bootsync/)
- [Understand Arm CCA BootSync and the Boot Injection protocol](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-bootsync/cca-bootsync/)
- [Configure UEFI Secure Boot and disk encryption in Arm CCA Realms](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-bootsync/flow/)
- [Next Steps](https://learn.arm.com/learning-paths/servers-and-cloud-computing/cca-bootsync/_next-steps/)

## Explore related resources
Find more information about the topics in this Learning Path:
- [Arm Confidential Compute Architecture](https://www.arm.com/architecture/security-features/arm-confidential-compute-architecture)
- [Arm Confidential Compute Architecture Open-Source enablement](https://www.youtube.com/watch?v=JXrNkYysuXw)
- [Learn the architecture - Realm Management Extension](https://developer.arm.com/documentation/den0126)
- [Realm Management Monitor Specification](https://developer.arm.com/documentation/den0137/latest/)
- [Realm Host Interface Specification](https://developer.arm.com/documentation/den0148/latest/)
- [ArmCcaBootSync README](https://gitlab.arm.com/linux-arm/edk2-cca/-/blob/cca/4441_measured_boot_v1/ArmVirtPkg/ArmCcaBootSync/Readme.md)

## Review frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

**Do I need networking inside the Realm to deliver boot data?**

No. BootSync operates before the guest operating system has networking and uses the Boot Injection protocol to provide early boot data.

**How do I know BootSync requested variable data?**

In the User Context service log, you’ll see `BIB Variable Data Requested` and the expected `<RPV>_VAR.dat` file name. If the file is missing, BootSync reports `BootSyncNotDone`, and the Realm boots without Secure Boot enabled.

**What result should I expect when Secure Boot is configured but the kernel is unsigned?**

The unsigned kernel is rejected. This confirms that UEFI Secure Boot is enforcing signature verification.

**After I sign the kernel, how do I verify that Secure Boot is enabled?**

The signed kernel boots successfully and the Secure Boot UEFI variable reports `1`. Check that value to confirm the state.

**How do I confirm the encrypted root file system unlocks correctly?**

After BootSync supplies the correct passphrase, the boot log reports `LUKS partition unlocked, switching root`. Run `df -h` and verify that `/dev/mapper/cryptroot` is mounted at `/`.
