Home labs & practical projects

Make a Linux service survive a reboot

A project to do with your own tools, with guidance on what to create and capture.

Local lab Suggested time: 2–3 hoursYour own authorised environment

What you could create

A service works after manual setup but fails after the server restarts. The administrator must make storage, permissions and service configuration persistent.

Example evidence format

Project evidence map (example)

Persistent service configurationScope and inputs

Reboot validation and troubleshooting logDecisions and reasoning

Evidence record (example)

Evidence	What to capture
Persistent service configuration	Show the inputs, scope and decisions behind this record. The service runs with the intended non-administrative identity.
Reboot validation and troubleshooting log	Include the evidence supporting your conclusion. A reboot preserves configuration and data availability.

What you'll need

Local lab

Use a disposable compatible Linux VM and a harmless service with a dedicated data directory. Save a snapshot and a baseline status report.

Project record

Keep the working files for persistent service configuration and record assumptions as you go.

Current reference material

Use the linked provider resources to verify the features, access terms and version relevant to your project.

Access & cost

Uses your own computer. Confirm hardware capacity, software licences and download terms before setup.

Use disposable VMs, containers or a simulator. Keep the lab separate from your everyday machine and work network.

Suggested milestones

1
Plan and investigate
Configure the service account, filesystem permissions and persistent storage mount.
2
Develop your approach
Enable the service and inspect failures using system logs and security context where applicable.
3
Verify and explain
Reboot the VM and validate service access and stored test data.

Evidence worth keeping

Keep clear, organised evidence of your design and any testing you carry out.

1
Persistent service configuration
Show the inputs, scope and decisions behind this record. The service runs with the intended non-administrative identity.
2
Reboot validation and troubleshooting log
Include the evidence supporting your conclusion. A reboot preserves configuration and data availability.

Label design proposals and observed results clearly.

Explain your work

Use these prompts to reflect on your decisions and what you learned.

Which part of your persistent service configuration needed the most judgement?
What observation or assumption changed your approach?
What would you improve, and what have you not verified?

Describe this as a personal project in your portfolio.

Useful resources

Use these resources to deepen your understanding and check key details.

Official certification objectives

Review the current provider requirements and relevant subject areas.

Red Hat Learning Subscription (all courses + labs)

Check relevance, platform versions and current access terms.

Explore external learning resources

Find relevant providers and check features, access requirements and costs.

A useful starting point

Use a disposable compatible Linux VM and a harmless service with a dedicated data directory. Save a snapshot and a baseline status report.

What a good result looks like

The service runs with the intended non-administrative identity.
A reboot preserves configuration and data availability.

Finish the project

Save sanitised evidence, then remove the lab instances or revert to the clean snapshot. Remove temporary accounts and credentials.

Independent home-project guidance, not an official vendor lab or a claim of complete exam coverage. Use your own tools and label the work accurately.