Challenge 1: Effective Options in /private After the Merge — Solution Walkthrough The effective Options for /private: FollowSymLinks stays ON, Indexes is OFF. Why FollowSymLinks survives: Apache's context merging is additive, not a full replacement at each step. The /private block only writes "Options -Indexes" -- it never mentions FollowSymLinks at all. The leading minus sign on -Indexes means "remove specifically this one option from whatever set is already in effect," not "replace the entire Options list with just what's written here." Since the parent /var/www/html block already set Options to "Indexes FollowSymLinks," and /private only subtracts Indexes from that inherited set, FollowSymLinks is simply never touched and continues to apply. If /private had instead written a plain "Options FollowSymLinks" (no leading + or -), that WOULD have been a full replacement, and Indexes would already be off anyway just by omission -- but the actual example uses the "-Indexes" subtractive form specifically to demonstrate the merge behavior rather than a replacement. WHY THIS WORKS AS AN ANSWER ------------------------------ This exercise checks that the reader understands Apache's directory context merging is genuinely additive/subtractive per-directive, not "the most specific context wins outright" -- a directive untouched by a more specific context still carries over from a broader one.