Test
5. Backend Administration (Part 3)
Preguntas del test (18)
1Which components are part of a TYPO3 site configuration? (3)
- ABase URL configuration (e.g. the domain to access the website)
- BBackend user accounts (e.g. administrators and system maintainers)
- CLanguage configuration (which languages are supported by the site)
- DStatic routes of the site (e.g. the robots.txt directive)
- ELocation in the file system (e.g. path to the htdocs-directory)
- FExtensions (e.g. which extensions are available and activated)
2Which statements about the site identifier in the site configuration are correct? (2)
- AThe site identifier must be a numeric value
- BThe site identifier is used in the file system path
- CThe site identifier is always the domain of the website
- DThe site identifier must have a minimum length of 3 characters
- EThe identifier foobar is a valid site identifier
- FThe site identifier must not contain numbers
3Where in the system are site configurations stored? (2)
- AIn the database table sys_configuration
- BIn Composer-based installations as part of the file typo3conf/LocalConfiguration.php
- CIn non-Composer-based installations in the file system as typo3/sysext/core/Configuration/sites.php
- DIn Composer-based installations in the file system as config/sites/<identifier>/config.yaml
- EIn non-Composer-based installations in the file system as typo3conf/sites/<identifier>/config.yaml
4What is the best way to output a static text when a request to /robots.txt is being made? (1)
- ACreate a page with the title robots.txt and add your text in a content element of type “text”
- BStore a file named robots.txt that contains the text in the file system path typo3conf/
- CAdd a static route to the site configuration, choose “static text” as the route type, and enter the text in the text field
- DEnter the text under “Admin Tools → Settings → Installation-Wide Options → Robots exclusion”
5What do you need to consider if you want to set up multiple domains in TYPO3? (2)
- ASet up multiple installations of TYPO3, one instance for each domain
- BCreate multiple site configurations, one configuration for each domain
- CMultiple domains are possible in TYPO3 but content is always shared across them
- DThe workspace functionality must be deactivated to allow multiple domains
- ECreate a site configuration with multiple languages and assign each domain to one language
- FCreate two entry points in the page tree and use them in the site configurations for each domain
6Which statements about languages in site configurations are correct? (2)
- AEach site configuration supports up to 16 languages
- BThe default language English must be removed before any other language can be added
- CA fully qualified domain name can be configured as an entry point per language.
For example: https://example.fr/ - DA language specific suffix can be configured as an entry point per language.
For example: /fr/ - EThe two letter ISO 639-1 code of the language must be configured as the entry point for each language.
For example: fr
7Which statements about the toggle switch “Visible in Frontend” under “Languages” in site configurations are correct? (3)
- AIf disabled, content in this language can not be viewed in the frontend
- BIf disabled, page contents can not be translated into this language in the backend
- CThe toggle switch reflects the configuration property languages.enabled in the site configuration file config.yaml
- DThe toggle switch has no effect if the application context is configured as “Development”
- EOnly one language can be set to not visible in frontend at a time
- FIndependently from the state of the switch, backend users can translate content for the language in the backend
8You 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)
- ABy duplicating the folder typo3conf/sites/example.com/ to
typo3conf/sites/development.local/ - BBy adding the development domain as a second domain record to the root page under “Web → List”
- CBy adding a second site configuration and storing the development domain as the entry point
- DBy deleting all site configurations to remove the limit of one domain
- EBy configuring a “base variant” for the development domain in the site configuration
- ABy duplicating the folder typo3conf/sites/example.com/ to
9How can you rename a file in the Filelist module? (2)
- ABy double-clicking on the file name in the list view of the module
- BAs renaming files would break the data integrity, you have to delete the file and upload the same file under the new name
- CIf the “extended view” is enabled, click on the “rename” icon
- DRight-click on the file icon and select “Rename” from the context menu
- ESelect the file in the backend module “Filelist” and press F2
- FClick on the “actions” icon (three vertical dots) and select “Rename” from the context menu
10How can you use a recycling bin for files? (1)
- ABy activating the system extension “Recycler” that provides this feature
- BBy activating the function in the Page TSconfig:
config.file.recycler = true - CBy creating a folder _recycler_/ in backend module “File → Filelist”
- DBy activating the “Use recycler for files” checkbox in the user settings
- ETYPO3 only features a recycling bin for data records (such as pages and content elements) but not for files
11How 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)
- ABy making sure that the additional information is stored as EXIF data in the image file
- BBy adding a YAML file metadata.yaml that contains the additional meta data information in the same folder as the image
- CBy leveraging the fields provided by the system extension “Filemetadata”
- DBy activating additional file meta data fields under “Admin Tools → Settings → Feature Toggles”
12Which statements about TYPO3’s “home directory” feature are correct? (2)
- ATYPO3 automatically creates a home page for every backend user that shows the user’s profile on the website
- BTYPO3 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/'; - CHome directories in the FAL can be configured for backend users and user groups
- DHome directories appear as an additional mount point in the FAL
- EBackend users can not copy or move files from home directories into any other directory in the FAL
13What are the main benefits of the File Abstraction Layer (FAL) in TYPO3? (2)
- AThe FAL automatically converts .docx files into content elements out of the box
- BBackend users with administrator privileges can use the FAL to install extensions
- CFiles uploaded through the FAL are automatically stored in multiple locations to increase data redundancy
- DMeta data such as a title and a description can be added to images for example
- EThe FAL abstracts physical file assets stored in the system
14How can you create a new backend user? (2)
- AYou cannot create additional backend users in TYPO3, only frontend users
- BBy right-clicking the page with the TYPO3 logo (ID=0) in the page tree and selecting “New → Backend user”
- CIn the “Web → Page” backend module
- DIn the “Web → List” backend module
- EIn the “Admin Tools → Maintenance” backend module
- FIn the “Admin Tools → User admin” backend module
- GIn the “System → Backend Users” backend module
15Which areas and modules of the TYPO3 backend let you configure access permissions for backend users? (3)
- AWhich areas and modules of the TYPO3 backend let you configure access permissions for backend users? (3)
- BThe “System → Backend Users” backend module to configure backend users
- CThe “User Settings” backend module to configure backend users
- DThe “System → Access” backend module to configure access to pages
- EThe “Admin Tools → User Admin” backend module to configure backend users
- FThe “Web → List” backend module to configure backend user groups
16How can you quickly and easily look-up the permissions that users have in the page tree? (1)
- ABy using the “System → Access” backend module
- BBy using the “Info → Access” backend module
- CBy using the “Admin Tools → Access” backend module
- DBy using the “Site Management → Access” backend module
- EBy opening the user settings for each user
17Which actions are required to allow a non-admin backend user to edit the contents of a page but not the page itself? (3)
- ABy configuring the permissions in the “User settings” backend module
- BBy configuring the “Access Lists” of the user and/or user group
- CBy configuring an appropriate file mount
- DBy setting the permissions in the “Web → Access” backend module
- EBy adding the appropriate TypoScript settings in the User TSconfig
- FBy adding the appropriate DB Mount
18How do you restrict the permissions to edit a page and its contents to users with administrator permissions? (2)
- ABy activating the “Admin Lock” toggle switch in the site configuration
- BBy creating the file typo3conf/LOCK_BACKEND
- CBy activating the “Lock” option under “System → Access” for the appropriate page
- DBy adding the following option to the User TSconfig:
config.restrictEditingForNonAdmins = 1 - EBy activating the “Restrict editing by non-Admins” toggle switch in the “Access” tab of the page properties
Información
- Descripción
- El usuario ha eliminado su información de asignaturas Test sobre 5. Backend Administration (Part 3), creado por Usuario eliminado el 23/05/2022.
- Autor
- Usuario eliminado
- Idioma
- English
- Visitas
- 19
- Historial
- Creado el 23 may 2022 · actualizado el 23 may 2022
- Etiquetas
- Valoración
- Aún sin valoraciones Valora este test