Which components are part of a TYPO3 site configuration? (3)
Base URL configuration (e.g. the domain to access the website)
Backend user accounts (e.g. administrators and system maintainers)
Language configuration (which languages are supported by the site)
Static routes of the site (e.g. the robots.txt directive)
Location in the file system (e.g. path to the htdocs-directory)
Extensions (e.g. which extensions are available and activated)
Which statements about the site identifier in the site configuration are correct? (2)
The site identifier must be a numeric value
The site identifier is used in the file system path
The site identifier is always the domain of the website
The site identifier must have a minimum length of 3 characters
The identifier foobar is a valid site identifier
The site identifier must not contain numbers
Where in the system are site configurations stored? (2)
In the database table sys_configuration
In Composer-based installations as part of the file typo3conf/LocalConfiguration.php
In non-Composer-based installations in the file system as typo3/sysext/core/Configuration/sites.php
In Composer-based installations in the file system as config/sites/<identifier>/config.yaml
In non-Composer-based installations in the file system as typo3conf/sites/<identifier>/config.yaml
What is the best way to output a static text when a request to /robots.txt is being made? (1)
Create a page with the title robots.txt and add your text in a content element of type “text”
Store a file named robots.txt that contains the text in the file system path typo3conf/
Add a static route to the site configuration, choose “static text” as the route type, and enter the text in the text field
Enter the text under “Admin Tools → Settings → Installation-Wide Options → Robots exclusion”
What do you need to consider if you want to set up multiple domains in TYPO3? (2)
Set up multiple installations of TYPO3, one instance for each domain
Create multiple site configurations, one configuration for each domain
Multiple domains are possible in TYPO3 but content is always shared across them
The workspace functionality must be deactivated to allow multiple domains
Create a site configuration with multiple languages and assign each domain to one language
Create two entry points in the page tree and use them in the site configurations for each domain
Which statements about languages in site configurations are correct? (2)
Each site configuration supports up to 16 languages
The default language English must be removed before any other language can be added
A fully qualified domain name can be configured as an entry point per language. For example: https://example.fr/
A language specific suffix can be configured as an entry point per language. For example: /fr/
The two letter ISO 639-1 code of the language must be configured as the entry point for each language. For example: fr
Which statements about the toggle switch “Visible in Frontend” under “Languages” in site configurations are correct? (3)
If disabled, content in this language can not be viewed in the frontend
If disabled, page contents can not be translated into this language in the backend
The toggle switch reflects the configuration property languages.enabled in the site configuration file config.yaml
The toggle switch has no effect if the application context is configured as “Development”
Only one language can be set to not visible in frontend at a time
Independently from the state of the switch, backend users can translate content for the language in the backend
You operate your TYPO3 instance under the main URL “example.com”. A second domain “development.local” should become active in development environments. How do you configure this properly? (1)
By duplicating the folder typo3conf/sites/example.com/ to typo3conf/sites/development.local/
By adding the development domain as a second domain record to the root page under “Web → List”
By adding a second site configuration and storing the development domain as the entry point
By deleting all site configurations to remove the limit of one domain
By configuring a “base variant” for the development domain in the site configuration
How can you rename a file in the Filelist module? (2)
By double-clicking on the file name in the list view of the module
As renaming files would break the data integrity, you have to delete the file and upload the same file under the new name
If the “extended view” is enabled, click on the “rename” icon
Right-click on the file icon and select “Rename” from the context menu
Select the file in the backend module “Filelist” and press F2
Click on the “actions” icon (three vertical dots) and select “Rename” from the context menu
How can you use a recycling bin for files? (1)
By activating the system extension “Recycler” that provides this feature
By activating the function in the Page TSconfig: config.file.recycler = true
By creating a folder _recycler_/ in backend module “File → Filelist”
By activating the “Use recycler for files” checkbox in the user settings
TYPO3 only features a recycling bin for data records (such as pages and content elements) but not for files
How can you store additional meta data such as the creator, copyright information, and a geo-location against images uploaded through the Filelist module in TYPO3? (1)
By making sure that the additional information is stored as EXIF data in the image file
By adding a YAML file metadata.yaml that contains the additional meta data information in the same folder as the image
By leveraging the fields provided by the system extension “Filemetadata”
By activating additional file meta data fields under “Admin Tools → Settings → Feature Toggles”
Which statements about TYPO3’s “home directory” feature are correct? (2)
TYPO3 automatically creates a home page for every backend user that shows the user’s profile on the website
TYPO3 automatically creates a home directory in the file system for every backend user if the following configuration was made: $GLOBALS['TYPO3_CONF_VARS']['BE']['userHomePath'] = '1:users/';
Home directories in the FAL can be configured for backend users and user groups
Home directories appear as an additional mount point in the FAL
Backend users can not copy or move files from home directories into any other directory in the FAL
What are the main benefits of the File Abstraction Layer (FAL) in TYPO3? (2)
The FAL automatically converts .docx files into content elements out of the box
Backend users with administrator privileges can use the FAL to install extensions
Files uploaded through the FAL are automatically stored in multiple locations to increase data redundancy
Meta data such as a title and a description can be added to images for example
The FAL abstracts physical file assets stored in the system
How can you create a new backend user? (2)
You cannot create additional backend users in TYPO3, only frontend users
By right-clicking the page with the TYPO3 logo (ID=0) in the page tree and selecting “New → Backend user”
In the “Web → Page” backend module
In the “Web → List” backend module
In the “Admin Tools → Maintenance” backend module
In the “Admin Tools → User admin” backend module
In the “System → Backend Users” backend module
Which areas and modules of the TYPO3 backend let you configure access permissions for backend users? (3)
The “System → Backend Users” backend module to configure backend users
The “User Settings” backend module to configure backend users
The “System → Access” backend module to configure access to pages
The “Admin Tools → User Admin” backend module to configure backend users
The “Web → List” backend module to configure backend user groups
How can you quickly and easily look-up the permissions that users have in the page tree? (1)
By using the “System → Access” backend module
By using the “Info → Access” backend module
By using the “Admin Tools → Access” backend module
By using the “Site Management → Access” backend module
By opening the user settings for each user
Which actions are required to allow a non-admin backend user to edit the contents of a page but not the page itself? (3)
By configuring the permissions in the “User settings” backend module
By configuring the “Access Lists” of the user and/or user group
By configuring an appropriate file mount
By setting the permissions in the “Web → Access” backend module
By adding the appropriate TypoScript settings in the User TSconfig
By adding the appropriate DB Mount
How do you restrict the permissions to edit a page and its contents to users with administrator permissions? (2)
By activating the “Admin Lock” toggle switch in the site configuration
By creating the file typo3conf/LOCK_BACKEND
By activating the “Lock” option under “System → Access” for the appropriate page
By adding the following option to the User TSconfig: config.restrictEditingForNonAdmins = 1
By activating the “Restrict editing by non-Admins” toggle switch in the “Access” tab of the page properties
