WebTech360 – In practice there are many cases where you need to add branching logic to a survey or quiz so that it changes according to the responses of specific questions. In a branching survey or test, follow-up questions appear only if they are relevant to the user's answer.
Add branch to your test
Before you begin, make sure all of your necessary questions have been created.
For each possible response on each question, select 1 destination you want to go to. In this example, if the user answers his question 1 correctly, he will be redirected to question 2. If the user answers wrong, he will go to the bottom of the form where the SUBMIT button is.
Similarly, you can create multiple branches in one test or in your Survey.
The above is a quick guide to the operations to help you branch out your test easily and effectively. Hope can help you work with Microsoft forms more effectively. Good luck.
See also: Instructions for creating automated tests using Microsoft Forms
Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.
Compare YaST and cryptsetup for a new encrypted SLES data volume, choose LUKS1 or LUKS2, and verify unlock and mount behavior safely.
Create, refine, and verify a least-privilege AppArmor profile on SLES 15 SP7, with a clear note on SLES 16’s SELinux default.
Set up RMT on SLES 15, mirror entitled repositories, and verify HTTPS registration and package access from a test client.
Connect SLES 15 to AD with YaST’s SSSD-based logon management, then verify directory lookup, domain login, and Kerberos tickets.
Set up the right Live Patching path for SLES 16.0 or 15 SP7, apply eligible kernel fixes, and confirm what is active without confusing it with a reboot-required kernel update.
Load a custom SLES 15 kernel module without disabling Secure Boot. Match the running kernel, sign the .ko file, enroll a MOK key, and verify loading.
SLES 15 SP5 can migrate online to SP6, but each node must reboot. Use a tested rolling upgrade or blue-green cutover to keep workloads reachable.
Use SUSE’s supported STIG profile to scan SLES 15, test remediation, review remaining findings, and retain assessment evidence.
Trace a failed Cockpit connection through DNS, port 9090, the systemd socket, firewalld, TLS, and login settings using current SUSE guidance.
