Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,090 of 9,090 pages
About the help in other languages
All help pages

Lesson 3.5: Multisite, written test

A twelve-question written test for the end of the Multisite and site packages course, on siteaccesses, matching by URL, host and port, SiteURL, trusted proxies, logs and caches per site, settings per site in extensions…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/trainers/assessments/module-03-administration-courses/multisite-written-test.md

On this page

Lesson 3.5: Multisite, written test

This test closes the Multisite and site packages course. Its core is the siteaccess: what it is, how a request finds one, and what has to agree (settings, web server, DNS, certificate) for a second site to work. It also asks when a second installation is the better choice.

Note

This is the trainer's own assessment, not an official certification.

At a glance

CourseAssessments and practical exercises
ModuleModule 3: Assessing the administration courses
Duration40 minutes (5 briefing, 25 test, 10 going through the answers)
LevelAdvanced
AudienceLearners at the end of the Multisite and site packages course
PrerequisitesThe Multisite and site packages course; Lesson 1.2 for the trainer

Learning objectives

Learners who pass this test have shown that they can:

  • define a siteaccess and name the three usual ways of matching one;
  • configure and check host matching, including behind a proxy;
  • keep logs, caches and INI caches apart per site;
  • place settings for all siteaccesses of a site inside an extension;
  • choose between one installation with several siteaccesses and several installations.

Trainer's notes

How to run it

  1. Hand out the questions without the key; 25 minutes.
  2. Go through the answers with 10.2 and Multisite on one installation on the projector.

Common questions

Our course did not cover cross-site links. Drop question 10.

Pitfalls

  • Learners who only used URL matching. Questions 3 to 6 need host matching; make sure the course showed it, at least on the projector.

The test

  1. What is a siteaccess, in one sentence with its three parts?
  2. What is the shipped MatchOrder, and what does it mean?
  3. Name one advantage of host matching over URL matching for production.
  4. You set up host matching, but both host names reach the same siteaccess. What do you check in HostMatchMapItems[]?
  5. A test host www.example.com.test.local should reach the siteaccess of www.example.com. Which setting and value allow it, and what is the risk?
  6. The site is behind a load balancer on another machine and treats HTTPS requests as plain HTTP. Which setting is missing?
  7. What is [SiteSettings] SiteURL used for?
  8. Several sites share one installation. Which setting makes each site cache its INI files in its own directory?
  9. An extension serves the siteaccesses example__eng and example__ger. Where do settings go that apply to both?
  10. A link from site A to an article of site B comes out with site A's path in front and leads nowhere. Which extension fixes this?
  11. Two different customers want one site each. One installation with two siteaccesses, or two installations? Why?
  12. After changing siteaccess settings, which cache do you clear?
Answers
  1. One way into the installation: a name, a set of settings in settings/siteaccess/<name>/, and a rule for which requests it answers (10.2).
  2. uri;host;port: the ways a request is matched, tried in that order (10.2).
  3. A host name per siteaccess suits production and HTTPS certificates per host (Multisite on one installation).
  4. The host name the browser sends must be exactly the one listed, without a port and in lower case (10.2).
  5. HostMatchMethod=start (or the method start on that one entry); start also takes hosts you did not mean, so use it only where the web server answers for your own hosts only (Siteaccess host and language matching).
  6. The load balancer's address in [HTTPHeaderSettings] TrustedProxies[] (10.2).
  7. The site's address, used in mails, feeds, sitemaps and by exp:benchmark (10.2).
  8. [FileSettings] INICacheDir=site (Multisite on one installation).
  9. In the extension's settings/override__example/ (for the group) or settings/override/ (for every siteaccess of the extension) (Per-site settings inside extensions).
  10. ezurlmultisite (Multisite cross-site links).
  11. Two installations: different customers need operating-system isolation, separate load and separate backups (Multisite on one installation).
  12. The INI cache: php bin/php/ezcache.php --clear-tag=ini --allow-root-user (10.2).

Scoring

  • One point per question; question 1 needs all three parts, question 5 the setting and the risk.
  • Pass: 8 of 12 points or more, with questions 4 and 11 correct.

Further reading

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x