Overview
Module: Download Clients & Indexers
Activity type: Homework / independent application
Objective: Explain why Prowlarr centralizes indexer definitions for compatible media-management applications.
Requirements
Draw a production architecture showing Prowlarr, two compatible automation applications, a download client, administrative access, DNS, certificate termination, backups, and trust boundaries.
Create a field checklist for onboarding an authorized indexer, including endpoint ownership, protocol, credentials, categories, rate limits, privacy policy, retention policy, and legal approval.
Using only the local teaching service, add logging that records the t parameter and requested categories, then compare capability and search requests generated by Prowlarr.
Write a recovery plan that identifies which Prowlarr files must be backed up, how secrets are protected, how restore validation is performed, and how configuration drift is detected.
Explain why an indexer can pass a connectivity test but still produce no usable results for an application.
Submit / record
- [ ] Evidence artifacts (secrets redacted)
- [ ] Spiral connections written
- [ ] Ready for topic quiz