36574640
Descripción
Test por Pascal Bartl, actualizado hace más de 1 año
|
Creado por Pascal Bartl
hace más de 2 años
|
|
Pregunta 1
Pregunta
How can you recursively delete pages (a page and its subpages) in one go? (3)
Respuesta
-
To delete pages with subpages, you have to enable recursive page deletion in the “User Settings”
-
The context menu in the page tree features a “Delete” entry to delete a page and its subpages
-
Open the page properties, select tab “Resources”, and execute “Delete page with subpages”
-
The backend module “Web → List” lets users delete pages and their subpages in one go
-
The “Site Management” module lets users recursively delete pages in one go
-
Click on the parent page in the page tree and drag’n drop the page into the “Delete” area on the right-hand side
Pregunta 2
Pregunta
How can you create multiple pages in one go? (1)
Respuesta
-
This is not possible in TYPO3; you have to create one page at a time
-
By highlighting the parent page in the page tree, followed by executing the “page generator” function at the top right
-
By right-clicking the page icon in the page tree, followed by selecting the item “More options → Create multiple pages” from the context menu
-
By accessing the “Web→ Functions” module, and then executing the “Multiple Page Creation” function
Pregunta 3
Pregunta
What are your options to determine the ID of a page in the TYPO3 backend? (2)
Respuesta
-
Enable the global configuration “Show page IDs” in the Admin Tools
-
Moving the mouse pointed over the page icon in the page tree shows the page ID as a tool tip
-
The “Pagetree Overview” in the “Web → Info” module contains a column that shows the page IDs
-
Enter the following User TSconfig to display the page ID in the page tree: options.pageTree.showPageIdWithTitle = 1
-
Install and activate the extension “Advanced file metadata” to show the page IDs in the Filelist module
Pregunta 4
Pregunta
Which statement(s) about the RTE are correct? (3)
Respuesta
-
RTE stands for “Random Text Encryption” and is a security feature
-
RTE stands for “Rich Text Editor”
-
The RTE is a system extension that can be replaced as required
-
Only backend users with administrator privileges can use the RTE
-
The RTE can be configured using a YAML file
-
Non-administrator backend users can disable the RTE by applying the following User TSconfig: mod.rte.enabled = 0
Pregunta 5
Pregunta
Which steps are required to add a CKEditor plugin from the ckeditor.com website to your TYPO3 instance? (3)
Respuesta
-
Enable the add-on in the TYPO3 backend under the “Admin Tools”
-
Download the add-on as a ZIP file from ckeditor.com
-
Add the path to the extracted file(s) to the YAML configuration file as “externalPlugins”
-
If the add-on requires any configuration, update your YAML configuration file accordingly
-
Configure the permissions to allow backend users to use the additional plugin
-
Execute the following Composer command to clear caches: composer dumpautoload
Pregunta 6
Pregunta
You created a new configuration preset for the CKEditor using a custom YAML file but the preset isn’t available. What could cause this issue? (1)
Respuesta
-
The preset’s name does not start with “ckeditor”
-
The old CKEditor configuration is still cached and must be cleared by deleting the content of the following folder: var/cache/data/ckeditor/
-
The preset hasn’t been activated in the “Admin Tools”
-
The preset’s file path hasn’t been added to the following global configuration: $GLOBALS['TYPO3_CONF_VARS']['RTE']['Presets']
Pregunta 7
Pregunta
Which of the following are best practices for configuring the CKEditor in TYPO3? (2)
Respuesta
-
Edit the configuration files in the system extension’s path directly
-
Use the configuration file Full.yaml provided by the TYPO3 Core as an example only, as it is not intended for production use
-
Use the XML format for custom configuration presets
-
Encrypt your custom configuration presets for security reasons
-
Store custom configuration presets in the path fileadmin/ckeditor/presets/
-
Store custom configuration presets in a Site Package extension
Pregunta 8
Pregunta
How can you disable the RTE for a specific page in the TYPO3 backend? (1)
Respuesta
-
This is not possible as the CKEditor is part of the TYPO3 Core
-
By activating the “Disable Rich Text Editor” checkbox in the page properties
-
By adding the following global configuration to the file typo3conf/AdditionalConfiguration.php: $GLOBALS['TYPO3_CONF_VARS']['BE']['richTextEditor'] = 0
-
By adding the following TypoScript code to the Page TSconfig: RTE.default.disabled = 1
Pregunta 9
Pregunta
What is the most efficient and recommended approach to implement forms in TYPO3? (1)
Respuesta
-
As the TYPO3 Core does not provide any form functionality, you have to use a third-party extension
-
By adding HTML code such as <form>...</form> to an HTML content element
-
By using the Form Framework that can be installed/activated as a system extension
-
By using an external service such as Google Forms, Microsoft Forms, or Cognito Forms
Pregunta 10
Pregunta
What are “finishers” in TYPO3’s Form Framework? (2)
Respuesta
-
Finishers validate the data entered and submitted by users
-
Finishers are the first step in a form workflow as they build the HTML output of a form in the frontend
-
Finishers are the last step in a form workflow to process the form data submitted by a user
-
Only one finisher per form can be configured by backend users
-
A typical finisher could be a redirect to a specific page in the system
Pregunta 11
Pregunta
What are “validators” in TYPO3’s Form Framework? (2)
Respuesta
-
Validators check the data entered and submitted by users
-
Validators are the last step in a form workflow to store the data in the database
-
Validators make sure that a translation of the form labels exists in multi-language websites
-
Not all validators are available for every form element
-
Each form element can only have one validator to check the input data
Pregunta 12
Pregunta
How do you customize the frontend templates of a form implemented by the Form Framework in TYPO3? (1)
Respuesta
-
By editing the Fluid template files of the system extension: typo3/sysext/form/Resources/Private/Frontend/*
-
By overriding the default paths to the template files using TypoScript: plugin.tx_form.view.templateRootPaths.10 = ...
-
By setting the path to the template files for each form in the backend module: “Web → Forms → Settings → Templates”
-
By creating a custom configuration file in YAML and setting the template root path as rendering options
Pregunta 13
Pregunta
What is the recommended format and location of configuration files for forms of the Form Framework? (1)
Respuesta
-
As PHP files in the file system under fileadmin/forms/
-
As PHP files in the file system under typo3/sysext/form/Configuration/Form/
-
As YAML files in a site package extension in the path Configuration/Form/
-
As YAML files in the file system under config/forms/
-
As YAML files in the file system under fileadmin/Configuration/Forms/
-
As XLIFF/XML files in a site package extension in the path Resources/Private/
Pregunta 14
Pregunta
Which statements about custom templates for forms of the Form Framework are correct? (3)
Respuesta
-
Only frontend templates can be customized by configuring a custom path
-
Only backend templates can be customized by configuring a custom path
-
Custom layouts, templates, and partials can be used by configuring a custom path
-
Backend and frontend templates can be customized by configuring a custom path
-
All layouts, templates, and partials can be overridden by editing the TYPO3 Core files
-
Custom templates should be stored in a site package extension
Pregunta 15
Pregunta
Which statements about the backend module “Workspaces” are correct? (3)
Respuesta
-
The “Workspaces” module builds the user interface for the versioning concept in TYPO3
-
A single workspace is a specific state in the TYPO3 backend
-
If the “Workspaces” module is disabled or deleted, backend users can’t publish any content changes
-
Administrator privileges are required for backend users to access any workspaces
-
The “Workspaces” module allows multiple backend users to edit content elements at the same time
-
Changes made in a workspace can be published automatically through a Scheduler task
Pregunta 16
Pregunta
What is the name of the default workspace once you installed and activated the workspace module the first time? (1)
Respuesta
-
“Draft”
-
“Live”
-
“Standard”
-
“Default”
-
“Test”
-
“Demo”
Pregunta 17
Pregunta
How can you show changes made in a workspace to your client before publishing them? (1)
Respuesta
-
Ask the client to access the website with the argument ?preview=true
-
Create a backend user for the client and ask the client to log-in
-
Create a frontend user for the client and ask the client to log-in
-
Generate a preview link and share the link with the client
Pregunta 18
Pregunta
How many custom workspaces can you create? (1)
Respuesta
-
TYPO3 features exactly 4 workspaces and you can’t add more
-
You can create up to 2 custom workspaces
-
You can create up to 8 custom workspace
-
You can create up to 16 custom workspaces
-
The number of custom workspaces is not limited
Pregunta 19
Pregunta
Which of the following workspace stages exist by default? (2)
Respuesta
-
Stage “Editing”
-
Stage “Review”
-
Stage “Updating”
-
Stage “Deleted”
-
Stage “Ready to publish”
-
Stage “Rejected”
Pregunta 20
Pregunta
You are using workspaces and you are working in the backend as an administrator user. Some functions are missing. What could cause this issue? (1)
Respuesta
-
Workspaces automatically deactivate some system extensions in the system
-
Some modules are only visible in the “Live” workspace
-
Some parts of the module “Workspace” haven’t been developed yet
-
You haven’t enabled the missing modules in the Extension Manager
¿Quieres crear tus propios Tests gratis con GoConqr? Más información.