Which server software is suitable to run TYPO3 v11 LTS? (2)
Linux, Apache, MySQL, and PHP v5.6 (LAMP stack)
PHP v7.0, PostgreSQL, and Apache web server
PHP v7.4, a web server, and MySQL v5.7
Java, PHP v7.3, and phpMyAdmin
IIS, ASP, SQLite
PHP v7.4, Apache or Nginx, and SQLite or MariaDB
PHP version 7.0 is available on your system. Which versions of TYPO3 can you use? (2)
TYPO3 version 6.2 LTS
TYPO3 version 7 LTS
TYPO3 version 8 LTS
TYPO3 version 9 LTS
TYPO3 version 10 LTS
TYPO3 version 11 LTS
Where in TYPO3 can you find the currently used TYPO3 Core version (in the format x.y.z)? (2)
TYPO3 outputs the exact version as a comment in the HTML source code of the frontend
TYPO3 adds a <meta>-tag that shows the exact version in the HTML source code in the backend
TYPO3 shows the exact version on the login page before you log-in at the TYPO3 backend
The “About TYPO3 CMS” module shows the exact version after logging-in to the backend (if the module is installed/enabled)
The page title shows the exact version after logging-in to the backend
Which resource do you consult to find out if a new version of TYPO3 is available? (1)
http://www.typo3.de
https://get.typo3.org
http://www.typo3blog.org
http://www.cmsmatrix.org
After installing TYPO3 or a third-party extension you get a blank screen (frontend and backend). What do you do? (2)
Delete all files in the var/cache/, var/temp/ and typo3conf/ext/ directories
Review the entries of the PHP error log
Change TYPO3’s application context to “Development”
Log-in to the TYPO3 backend and analyze the error message in the system log
Open the Admin Tools and analyze the TYPO3 error log
Which files are absolutely required so that TYPO3 can be accessed in the frontend? (2)
File typo3conf/LocalConfiguration.php
File index.php in the document root of the web server
File typo3/index.php
File typo3conf/ENABLE_INSTALL_TOOL
Which directories are a mandatory requirement so that TYPO3 can be accessed in the frontend? (2)
Directory typo3conf/
Directory typo3temp/
Directory t3lib/
Directory typo3/
Directory fileadmin/
Directory uploads/
What happens if the web server user does not have write access to the directory typo3temp/? (1)
You won’t be able to to login at the Install Tool
You won’t be able to to login at the TYPO3 backend
The TYPO3 frontend does not come up and shows an error message instead
TYPO3 continues to work without problems as the system automatically creates a fallback directory typo3temp2/
Certain functions in TYPO3 are not executed correctly. Where do you find the PHP configuration in order to review it? (1)
The only option is to review the php.ini file on the command line
The PHP configuration is encrypted for security reasons and can’t be reviewed
Open TYPO3’s internal PHP check by accessing https://example.com/phpinfo
Open the Admin Tools and go to the “Environment” section
The only option is to create a PHP file on the server that has the following content: <?php phpinfo(); ?>
Which file do you have to create manually to allow a TYPO3 installation from scratch? (1)
The file typo3conf/ENABLE_INSTALL_TOOL
The file typo3conf/ENABLE_INSTALL
The file config/install.yaml
The file FIRST_INSTALL
The file INSTALL
How can you access the Install Tool in TYPO3 v11 LTS? (2)
By accessing https://example.com/typo3/install.php
By accessing https://example.com/install
By opening “System → Install” in the TYPO3 backend
By opening “Site Management → Install Tool” in the TYPO3 backend
Install Tool functions appear under “Admin Tools” in the backend, if you have appropriate access privileges
A valid ENABLE_INSTALL_TOOL file is required to open the Install Tool. This file expires 60 minutes after its creation. How can you prevent this from happening? (1)
This cannot be changed, because the lifetime is hardcoded in the TYPO3 Core
By setting keepFile to 1 in the Install Tool under “All Configuration → BE”
By entering the string KEEP_FILE in the file ENABLE_INSTALL_TOOL
By adding an empty file named KEEP_FILE to the typo3conf/ directory
You suspect that certain system requirements in your TYPO3 installation are not met. How do you check this? (3)
You execute the script systemcheck.php on the command line, which is located in the typo3/ directory
You review the environment status provided by the Install Tool
You install the extension “Core Configuration Check” and run the system checks
You review the output of the backend module “System → Reports”
You review the PHP settings provided by the Install Tool
You generate a status report by executing the function “Site Management → System Reports”
How can you check if TYPO3 is able to send emails? (1)
You have to set up a contact form, add the form to a test page, and submit the form
You can send a test email from the Install Tool to an email address of your choice
You can send a test email from the Install Tool but only to @typo3.org email addresses
You can send a test email from the Install Tool but only to email addresses that use the same domain as the TYPO3 instance
You have to write a PHP script containing the PHP mail() function
What is the impact if the web server user can’t write into the var/cache/ directory in a Composer-based TYPO3 installation? (2)
The TYPO3 backend continues to work, but no images are shown
Backend users can’t login at the TYPO3 backend
The frontend does not work anymore (TYPO3 generates an error message)
The TYPO3 CLI (TYPO3 Console) continues to work
Direct access to the Install Tool works as this is the “emergency access”
TYPO3 continues to work, but all Scheduler tasks stop working
Your backend user account has administrator privileges but the backend does not show the “Admin Tools” section. What could cause this? (1)
The ENABLE_INSTALL_TOOL file has not been created
The system was set up using the Composer installation method
The system features multiple administrator accounts and your account is not set as a system maintainer
Access to the Admin Tool section is only available for the backend user “admin”
What is required to see and access Install Tool functions in the TYPO3 backend, if multiple administrator backend users exist? (2)
The TYPO3 backend must be locked for all user, except for administrator users
Multi-factor authentication (MFA) must be configured, enabled, and used
The user must have system maintainer privileges, if the application context is set to “development”
The user must have system maintainer privileges, if the application context is set to “production”
Only backend users with administrator privileges can see and access Install Tool functions
No other administrator users must be logged-in at the backend at the same time
You want to install TYPO3 v11 LTS from scratch into an empty or new directory using Composer. Which commands let you do this? (2)
composer pull typo3/cms version=11
composer get typo3:^11
composer create-project typo3/cms-base-distribution:^11 typo3
composer install typo3/cms:^11
composer require typo3/cms:^11
composer require typo3/minimal:^11
You want to update a Composer package that uses semantic versioning. Which version constraint do you use to get bugfixes only? (2)
=1.2.3
^1.2.3
∼1.2.3
1.2.*
=bugfix
You want to update a Composer package that uses semantic versioning. Which version constraint do you use if you want non-breaking updates only? (1)
*1.2.3
What do you have to or should you do when you update to a new bugfix version of TYPO3, e.g. an update from version 11.5.10 to 11.5.11? (2)
You should delete all TYPO3 caches
You have to empty all database tables whose names begins with cache_
You have to update the reference index in the “System → DB check” module
You have to run the “Update wizard” in the Install Tool
You should check if the website (frontend) is still working as expected (functional test)
Which statement about TYPO3 version updates is correct? (1)
TYPO3 bugfix version updates can be executed in the Admin Tools if the instance is not in “Composer” mode
The TYPO3 Core can not be updated – you have to install it from scratch and migrate the content
The Scheduler contains a task which keeps the TYPO3 Core automatically up-to-date
Every version update requires to lock the backend
