[Nov 10, 2024] AD0-E906 Exam Brain Dumps - Study Notes and Theory
Pass Adobe AD0-E906 Test Practice Test Questions Exam Dumps
NEW QUESTION # 25
A consultant is working with a customer's Marketing department on an Adobe Workfront engagement. The customer has already had a successful deployment of Workfront in the IT department. This installation has been extremely simple, with a single system administrator, five custom statuses used by the IT department, and some templates and reports. The director of Marketing is adamant that the Marketing department will not be using anything created for IT. The engagement cannot disrupt the existing installation.
Which approach should the consultant take?
- A. Create team for Marketing and IT, create a tear administrator fix each, and share each department's resources with the team
- B. Create companies for Marketing and IT create a system administrator for each, and share each department's resources with the company
- C. Create groups for Marketing and it. create a group administrator for each, and share each department's resources with the group
Answer: C
Explanation:
In this scenario, the best approach is to create separate groups for Marketing and IT within the same Workfront instance. Each group will have its own group administrator, and each department's resources (e.g., custom statuses, templates, reports) can be isolated and managed independently by the group admins.
This solution ensures that:
The existing IT setup is not disrupted.
The Marketing department can have its own customized Workfront environment without overlapping with IT's configurations.
This approach avoids creating unnecessary complexity (as in Option A with companies) or restricting functionality (as in Option B with teams).
Refer to Workfront documentation on group management to learn how to implement group-specific configurations in a single instance.
NEW QUESTION # 26
An organization uses a dropdown custom field for the type of creative assets that their internal studio produces. The studio managers use a report grouped by type of asset to determine which assets have been produced by the studio. A decision has been made to concentrate purely on digital work.
which action will prevent the print media options from being selected, while allowing historical data to display on the report?
- A. Hide the print choices on the dropdown field
- B. Remove the print choices on the dropdown field
- C. Move the print choices to the end of the dropdown list
Answer: A
Explanation:
In this case, the organization wants to prevent users from selecting print media options for new entries while still displaying historical data in reports. The best way to achieve this is to hide the print choices in the dropdown field. This approach ensures that:
Historical data remains unaffected: Since you are only hiding the options and not removing them, existing records with those print media values will continue to display in reports and other views.
No selection of new print options: By hiding these options, users will no longer be able to select them for new records, effectively preventing any further print media classifications.
Removing the print options (Option B) would delete historical data associated with them, which is not desirable for reporting. Moving them to the end of the list (Option C) doesn't restrict users from selecting them, which does not meet the objective of focusing solely on digital work.
This practice aligns with Adobe Workfront's best practices for managing dropdown fields, where options can be hidden but not removed, thus preserving the integrity of historical data while controlling future input.
For more details, refer to the Custom Fields section in Workfront's documentation, specifically around managing dropdown options and preserving historical data visibility in reports.
NEW QUESTION # 27
A project manager wants to ensure that all documents within a certain project are shared with a designated team in Workfront What is the correct option for carrying out this action?
- A. Link all the necessary document from Experience Manager to the designated project
- B. Share one of the documents the others will inherit the same access levels
- C. Find the project where these document all reside and share it with the entire team
Answer: C
Explanation:
In Workfront, the best way to ensure that all documents within a project are shared with a designated team is to share the entire project. By sharing the project, all documents and related assets within that project are automatically made available to the designated team members according to the project's access permissions.
Option C is incorrect because sharing one document does not automatically inherit the same access levels for the other documents. Option A suggests linking documents from AEM, but the question pertains to sharing documents within Workfront itself.
Refer to Workfront's documentation on document sharing for detailed instructions on how to share all project-related assets with teams.
NEW QUESTION # 28
An implementation consultant needs to configure metadata mapping between Adobe Workfront custom form fields and Adobe Experience Manager metadata properties. Which Iwo types of custom forms can the implementation consultant use to define these mappings? (Choose two)
- A. Document
- B. Program
- C. Portfolio
- D. Issue
Answer: A,D
Explanation:
When configuring metadata mapping between Adobe Workfront custom form fields and Adobe Experience Manager metadata properties, you can use Issue and Document custom forms to define these mappings. These types of forms are commonly used for tracking and managing work items and documents, both of which need to have their metadata synchronized between the two systems.
Issue custom forms: Used for tracking work requests, such as issues or tasks.
Document custom forms: Specifically used for managing metadata related to documents, which can be mapped directly to AEM assets.
Options C (Portfolio) and D (Program) are not typically used for metadata mapping related to assets or documents.
Refer to Workfront Enhanced Connector documentation for more information on mapping custom forms to AEM metadata properties.
NEW QUESTION # 29
An implementation consultant is configuring the enhanced connector Project Linked holders feature for a customer. The customer wants the linked folder structure to be defined using the workfront Portfolio name. Workfront Program name. Workfront Project name, and the project type. The project type is a project custom form field defined by the following:
What Linked Folder Structure defines this correctly?
- A. Portfolio,Program,Name,projectType
- B. Portfolio,Program,project,Program, project Type
- C. Portfolio,Program,Name.DE:projectType
Answer: A
Explanation:
In this case, the customer wants to define the linked folder structure based on the Workfront Portfolio name, Program name, Project name, and Project Type. The Project Type is a custom form field with specific choices like "Campaign," "Product Launch," etc.
The correct format to define the folder structure in AEM based on these elements would be:
Portfolio, Program, Name, projectType: This structure will create a hierarchical folder system in AEM where the folders are nested by Portfolio, Program, Project Name, and Project Type (which is pulled from the custom form field).
Option A includes an incorrect syntax with "DE
," which is not necessary, and Option C repeats the "Program" and misorders the fields.
Refer to Workfront Enhanced Connector documentation for further guidance on defining folder structures using custom form fields.
NEW QUESTION # 30
An AEM server is overloaded with too many concurrently running workflows. The developer decides to reduce the number of concurrent workflows. What should be configured?
- A. The number of threads in scheduler
- B. Launchers for each workflow
- C. Maximum Parallel jobs in OSGI console
Answer: C
Explanation:
In AEM, to limit the number of concurrent workflows running at the same time, you need to adjust the Maximum Parallel Jobs setting in the OSGI console. This setting controls how many workflow jobs can be processed simultaneously, and reducing this number will lower the load on the server by limiting the number of workflows that can run concurrently.
This setting can be found under the Day CQ Workflow - Workflow Engine configuration in the OSGI Web Console.
Options B and C refer to specific workflows and threads, but they do not directly address the overall system limit on concurrent workflow executions.
Refer to the AEM documentation on workflow scaling and performance for more information on how to adjust these settings in the OSGI configuration.
NEW QUESTION # 31
A web designer creates interactive web content via a URL. which needs to be approved I he user doing the reviewing has a Manager proofing permission profile in Adobe workfront. which they are currently accessing through the latest version of the Chrome browser. As part of the feedback process, the reviewer is required to leave comments on one page of the arte being reviewed before leaving the approval status. The Designer must be tagged in any updates required which tool should be used to accomplish this?
- A. Desktop Proofing viewer
- B. Web Proofing viewer
- C. Legacy Proofing, viewer
Answer: B
Explanation:
In this scenario, the reviewer needs to leave comments on an interactive web content URL and tag the designer. The Web Proofing viewer is the appropriate tool for reviewing interactive web content in Adobe Workfront. The Web Proofing viewer allows users to:
Review and comment on web-based content directly in the browser.
Tag users in comments and updates.
Approve or reject the content with the necessary feedback.
Option A (Desktop Proofing viewer) is typically used for offline or downloadable content, and Option C (Legacy Proofing viewer) refers to an outdated tool that lacks modern proofing functionalities.
Refer to Workfront's proofing documentation for more information on using the Web Proofing viewer for interactive content.
NEW QUESTION # 32
An implementation consultant wants to configure the enhanced connector inside a customer's Adobe Experience Manager environment. The customer needs the following functionality, automatic creation of project linked folders, comments syncing, and the automatic publishing of assets. How should the consultant navigate to the enhanced connector configuration screens?
- A. Tools > Cloud Services > Workfront Toots Configuration, select the configuration, and select Properties in the action bar.
- B. Tools > Asset> Workfront Tools Configuration, select the configuration, and select Properties in the action bar.
- C. Tools > Workfront Tools> Workfront Tools Configuration, select the configuration, and select Properties in the action bar
Answer: C
Explanation:
To configure the Enhanced Connector in AEM, including features like automatic project-linked folder creation, comment syncing, and automatic publishing of assets, you should navigate to:
Tools > Workfront Tools > Workfront Tools Configuration: This is where you can access and configure the connector settings within AEM. From there, selecting the configuration and choosing Properties in the action bar allows you to adjust the required settings.
Options B and C reference incorrect paths (Cloud Services and Assets), which are not used for the Enhanced Connector configuration.
Refer to AEM's Enhanced Connector documentation for step-by-step instructions on accessing and configuring the connector.
NEW QUESTION # 33
An implementation consultant wants to configure the enhanced connector inside a customer's Adobe Experience Manager environment. The customer needs to sync comments on linked documents from Adobe Workfront to Adobe Experience Manager.
how should this request be implemented?
- A. Select the Event Subscriptions tab inside the enhanced connector configuration properties, and click Enable Workfront Event Subscriptions
- B. Select the Event Subscriptions tab inside the enhanced connector configuration properties, and click Unable Comment Sync.
- C. Select the Advanced tab Inside the enhanced connector configuration properties, and click Enable Comment Sync.
Answer: A
Explanation:
To synchronize comments on linked documents from Adobe Workfront to Adobe Experience Manager, you need to enable Workfront Event Subscriptions in the enhanced connector configuration properties. Event Subscriptions allow AEM to track changes and updates from Workfront, including comment synchronization.
Workfront Event Subscriptions ensure that comments made in Workfront on linked documents are automatically synced to AEM.
Option A incorrectly references the Advanced tab, and Option C incorrectly states "Unable" instead of "Enable" Comment Sync.
Refer to AEM Enhanced Connector documentation on Event Subscriptions for step-by-step configuration.
NEW QUESTION # 34
A user wants to send a new version of a document they have uploaded to Workfront (o make sure that this latest version is now available in Adobe Experience Manager Assets. This document has previously been uploaded into both Workfront and the AEM.
How should the user accomplish this?
- A. Select the document in Workfront. select New Version, choose the Experience Manager integration, upload the revised version
- B. Select the document in workfront. make sure it has the same name as the previous version, click Send to. Choose. The experience Manager integration
- C. Select the document in Workfront rename to include the version number. click Send to. choose the experience Manager integration
Answer: A
Explanation:
To upload a new version of a document and ensure it is available in AEM Assets, the user must select the New Version option in Workfront. This triggers the version control process where the updated file can be uploaded.
By choosing the Experience Manager integration after selecting New Version, the system ensures that the latest version of the document is sent to AEM Assets, where it will replace the previous version without losing version history.
This workflow supports maintaining version control between Workfront and AEM, ensuring that the most current version of the asset is always available in both systems.
Refer to the Workfront-AEM Enhanced Connector Guide for further details on version control and document updates between Workfront and AEM.
NEW QUESTION # 35
A developer modified the default image metadata schema to include a text field with the property 'myProject:photographer'. While testing, the developer edited the metadata of an asset and entered the name 'Sabastiao Salgado' onto the custom field. However, the developer encountered an Issue and noticed that the value of the custom field does not display on a component.
What is a possible cause of this issue?
- A. The namespace 'myProject is not registered.
- B. The text field does not accept special characters
- C. the properly 'myProject:photgrapher already exists and is causing conflicts.
Answer: A
Explanation:
The issue of the custom field not displaying correctly on a component is likely because the namespace 'myProject' is not registered in AEM. AEM requires that custom namespaces be registered before they can be used for storing metadata properties. Without registering the myProject namespace, the system cannot properly recognize the custom property, leading to issues displaying the value.
Namespace registration: Custom namespaces like myProject need to be defined in AEM before they can be used to store properties.
Option A is incorrect because the text field should accept special characters, and Option B is incorrect unless there is already a conflicting property name, which is not indicated in this scenario.
Refer to AEM documentation on namespace registration for steps on how to register a custom namespace in AEM.
NEW QUESTION # 36
A user wants to create watermarked renditions of only some of the assets in AEM Assets. Which workflow strategy should be used to achieve this goal?
- A. Create a new workflow model that includes the Add Watermark process, and run this workflow on the desired assets.
- B. implement a new workflow process to generate a watermarked rendition of an asset. Modify the DAM Update Asset workflow model to include this workflow process.
- C. Modify the DAM update Asset workflow model to include the Add Watermark process.
Answer: A
Explanation:
To create watermarked renditions for only some of the assets in AEM, the best approach is to create a new workflow model that includes the Add Watermark process. This new workflow can be selectively applied to specific assets as needed, rather than modifying the global DAM Update Asset workflow which would affect all assets.
Selective application: By creating a custom workflow model, users can choose which assets will go through the watermarking process, providing more control and preventing unnecessary watermarking of all assets.
Option B and C suggest modifying the existing DAM Update Asset workflow, which could result in watermarking all assets, not just the desired ones, and is not flexible for specific asset selection.
Refer to AEM's workflow documentation for more information on creating custom workflows and adding watermark processes.
NEW QUESTION # 37
A large enterprise purchased Adobe workfront during a 'Land & Expand' Workfront campaign The legal department saw the Workfront document approval functionality and felt it would be good for their department. They know that to be effective, they must be in the same instance as marketing.
The partner lead wants to collaborate with sales on how to approach this opportunity, when discussing with the marketing team, there was immediate pushback and the marketing manager refused to consider Workfront s group admin features.
Which first step would motivate marketing to endorse a single Workfront Instance across the enterprise?
- A. A demo to marketing tailored for multiple groups
- B. Training marketing on group admin functions
- C. Executive/Stakeholder Engagement
Answer: C
Explanation:
To motivate Marketing to endorse a single Workfront instance across the enterprise, the best first step is to initiate Executive/Stakeholder Engagement. By getting senior leadership or key stakeholders from both the legal and marketing departments involved, it helps align the goals of the organization and illustrates the value of a unified system.
Executive engagement can help overcome resistance from individual departments (such as Marketing) by emphasizing the strategic importance of having a centralized system and showcasing the benefits for the entire organization.
Options A (training on group admin functions) and B (demo tailored for multiple groups) are useful but would not be as impactful as engaging executives to drive the initiative from the top down.
Refer to Workfront's adoption and implementation strategies for more information on how to engage stakeholders effectively.
NEW QUESTION # 38
An AEM Developer needs to create a log file for the project.
Which next step should the developer take?
- A. Create a log file under /apps/systemconfiguration... specific runmodp folder(s).
- B. Ask AMS/DevOps for admin access to ceate a log file via console.
- C. Create a log file under /apps/myprotect/configuration.... specific rubmode folder(s).
Answer: C
Explanation:
When creating a log file in AEM, the proper practice is to configure it under the /apps/myproject/configuration path for the specific runmode folders (e.g., config.dev, config.stage, config.prod). This ensures that the log file configuration is applied based on the environment.
Runmode-specific configuration ensures that logs are generated for the correct environment (development, staging, production), following best practices for AEM development.
Option A suggests using the /apps/systemconfiguration path, which is not the recommended location for project-specific configurations. Option B suggests asking for admin access, but developers typically create logs through code configuration rather than direct access to the console.
Refer to AEM's logging configuration documentation for details on setting up logs for specific environments.
NEW QUESTION # 39
Metadata mappings between Adobe Workfront and the AEM have been configured A user wants to send a document and its metadata from Adobe Workfront to Adobe Experience Manager Assets.
How should the user accomplish this?
- A. Select the document in Workfront click Send to. choose the experience Manager integration, choose the metadata to synch
- B. Select the document in workfront. choose New Version, choose the experience Manager integration, choose the metadata to synch
- C. Select the document in Workfront. click Send to, choose the Experience Manager integration, and metadata will synch automatically
Answer: C
Explanation:
When metadata mappings between Adobe Workfront and AEM are configured, the process of sending a document along with its metadata from Workfront to Adobe Experience Manager (AEM) Assets is streamlined. The user selects the document in Workfront, clicks "Send to," and chooses the Experience Manager integration.
The metadata fields that have been mapped are automatically synchronized along with the document. There is no need for manual selection of metadata at this stage, as the integration ensures that all configured mappings are applied.
This functionality is part of the enhanced connector, which simplifies the workflow between Workfront and AEM Assets by automating the synchronization of mapped metadata fields during the document transfer.
For more details, refer to Adobe's documentation on Workfront for Experience Manager Enhanced Connector, which outlines how automatic metadata synchronization works during document transfers.
NEW QUESTION # 40
A company uploads several images that represent products Each product is associated with a unique SKU number. The product owner wants the ability to search for multiple products by SKU number.
Which two steps must be completed to do this? (Choose two.)
- A. Customize the Assets Admin Search rail to include a Single Property Predicate and configure the property name to the SKU number
- B. Customize the mage metadata schema and add a new Single Line Text Held for the SKU number
- C. Customize the mage metadata schema and add a new Multi Value Text field for the SKU number
- D. Customize the Assets Admin Search rail lo Include a Multi Value Properly Predicate and configure the property name to the SKU number
Answer: B,D
Explanation:
To enable the search of products by SKU number in AEM, two main configurations are required:
Multi Value Property Predicate: By using a Multi Value Property Predicate, users can search for multiple SKU numbers at once. This is crucial if product owners need to query for multiple products simultaneously.
Single Line Text Field for SKU: SKU numbers are typically unique, so adding a Single Line Text field to the image metadata schema for SKU numbers ensures that each image has its own SKU field for accurate identification during searches.
Option D is incorrect because SKUs are usually single, unique identifiers, so a Multi Value Text field isn't necessary for each SKU.
Refer to AEM's documentation on customizing metadata schemas and Assets Admin Search to implement these features.
NEW QUESTION # 41
A user wants to create watermarked renditions of only some of the assets in AEM Assets. Which workflow strategy should be used to achieve this goal?
- A. Create a new workflow model that includes the Add Watermark process, and run this workflow on the desired assets.
- B. implement a new workflow process to generate a watermarked rendition of an asset. Modify the DAM Update Asset workflow model to include this workflow process.
- C. Modify the DAM update Asset workflow model to include the Add Watermark process.
Answer: A
NEW QUESTION # 42
A company calculates the benefit of a request based on the answers to 4 questions on a request custom form, this benefit value Is used to approve the request The values can be 0 through 15. Projects are then char ted in benefit groups as follows:
Level 1:0
Level 2: 1 - 5
Level 3: 6 10
Level 4 11-15
- A. Use a calculated expression on the protect custom field to calculate the benefit value
- B. Use a value expression on the view to link to the source request object
- C. Use text mode on the grouping with an aggregator formula to link to the project form
- D. In addition to the calculated value on the request, what other calculation should be created to achieve this reporting
Answer: B
Explanation:
In this scenario, the company is looking to group projects based on a benefit calculation from a custom form. The most efficient way to achieve this grouping and reporting structure in Adobe Workfront is by creating a value expression on the view. This method allows you to dynamically link the benefit value from the request object to other reporting structures, including the project object.
Value Expression on View: The value expression acts as a direct link between the custom form's calculated field and the reporting or view settings, enabling the system to pull the benefit value dynamically from the request.
Request Object Linking: By linking to the source request object through the value expression, it allows for seamless integration of calculated values into the project reporting view, ensuring that the benefit groups (Level 1-4) can be reported accurately based on the defined thresholds (0, 1-5, 6-10, 11-15).
This approach is more efficient compared to creating multiple calculated fields across different objects, and it allows for better maintainability and adaptability in future changes.
References from Adobe Workfront documentation emphasize the use of value expressions in reports and views for linking and utilizing calculated fields across different objects, enhancing the flexibility and power of custom reporting capabilities. Text mode is not necessary here because it is primarily used for custom formatting or more advanced use cases that don't involve simple value transfers between objects.
For more detailed information, you can refer to the official Workfront Help documentation on Custom Forms and Advanced Reporting Techniques in Adobe Workfront, where calculated fields and value expressions are thoroughly covered.
NEW QUESTION # 43
A customer wants to support translations on AEM Cloud Service environment. They have an existing third party vendor who will provide a pre-build package that must be deployed to AEM so it can be leveraged as port of the workflow process.
How should the developer deploy this third party library onto AEM Cloud Service?
- A. Host the package in a remote public or private repository (password protected) and reference it as part of pon.xml so it is included as part of Cloud Manager deployment
- B. Get the third party library as AEM package form the translation vendor and directly install it to Production environment using CRX Package Manager.
- C. Store the package as part of the customer code repository under the <url>file;$(mnven.multiModuleProjectDirectory)/install</url> folder and deploy it using Cloud Manager.
Answer: C
Explanation:
In Adobe Experience Manager (AEM) as a Cloud Service, deployments are handled through Cloud Manager, and all code, including third-party libraries, must be part of the versioned code repository. To deploy the third-party package provided by the vendor, it needs to be included as part of the AEM project's codebase under the install folder within the repository:
The package should be stored in the <url>file;$(maven.multiModuleProjectDirectory)/install</url> directory.
Once stored, the deployment will be handled through Cloud Manager's deployment pipeline.
This ensures the third-party package is included in the standard deployment process and follows AEMaaCS's immutable infrastructure model, which ensures that changes to environments are made only through deployments using Cloud Manager.
Option B is incorrect because installing a package directly to production via CRX Package Manager is not allowed in AEM as a Cloud Service. Option C would work for self-hosted AEM instances but not for AEMaaCS, where dependencies must be part of the Maven build.
For more information, refer to AEMaaCS deployment best practices and the Cloud Manager documentation.
NEW QUESTION # 44
As part of the configuration of the Enhanced Connector configuration, an Experience Manager user Group needs to be created for all users of workfront who use the enhanced connector.
How are the Workfront users added to this group?
- A. Automatically via the Enhanced Connector
- B. Using the import People option in Workfront
- C. From the Adobe Admin Console
Answer: A
Explanation:
When configuring the Workfront Enhanced Connector in AEM, Workfront users who will use the connector are automatically added to a corresponding AEM user group via the connector. This automatic process ensures that permissions and group assignments are correctly synced between Workfront and AEM without manual intervention.
Option A (using the Import People option in Workfront) refers to importing users into Workfront, not syncing users to AEM. Option C (from the Adobe Admin Console) is related to managing users in the Adobe platform but not specifically for the Enhanced Connector.
Refer to AEM and Workfront Enhanced Connector documentation for more information on user synchronization and group management.
NEW QUESTION # 45
A customer finds an Ul issue with component (/apps/<customer-project>/<component-name>) on AEM page It needs to be fixed urgently to avoid miscommunication. The developer has been asked to urgently make the change in AEM production.
How should the developer deploy the change to an AEM Cloud Service production environment?
- A. Fix the component on local AEM and create an AEM package for that specific component that can be deployed to Production using package Manager as a one-off urgent fix
- B. Fix the Ul issue as part of the customer code base and deploy the change to immutable repository using Cloud Manage' pipeline
- C. Due to the urgency of the request. Make the Ul fix directly to the component on AEM Production using CRXOE and then make same change to customer code bate
Answer: B
Explanation:
In AEM Cloud Service, the correct approach to making changes, even urgent ones, is to update the codebase and deploy it through the Cloud Manager pipeline. This ensures that the change is part of the version-controlled, immutable repository and follows best practices for deployment.
Immutable infrastructure: AEMaaCS does not allow direct modifications to production environments (e.g., via CRXDE Lite). All changes must be deployed through Cloud Manager, ensuring consistency and traceability.
Making changes directly on production via CRXDE or deploying one-off fixes using the Package Manager (Options B and C) violates AEMaaCS's immutable infrastructure principle and is not supported.
Refer to Adobe Cloud Manager's documentation for best practices on deploying urgent fixes in AEM as a Cloud Service.
NEW QUESTION # 46
A user creates a custom metadata schema that includes a multi value text field After modifying the file that the metadata has been applied to, the user discovers that the property corresponding to the multi value text field contains a new value.
what caused the value to become populated?
- A. The multi value text field is configured as a required field in the metadata schema.
- B. Another field in the metadata schema maps to the same property as the multi value text field
- C. The multi value text field was simultaneously updated by a different ACM Assets user.
Answer: B
Explanation:
If the multi-value text field is being populated unexpectedly, the most likely cause is that another field in the metadata schema is mapped to the same property. When multiple fields are mapped to the same property in AEM, any updates to either field will overwrite or modify the property, leading to the unexpected population of values.
This can happen due to schema misconfiguration, where fields unintentionally share the same JCR property path.
Option B is incorrect because the value being required would not cause it to be populated automatically. Option C suggests simultaneous updates by different users, which is unlikely to cause the issue described.
Check the metadata schema configuration to ensure fields are mapped to distinct properties.
NEW QUESTION # 47
......
Verified AD0-E906 dumps Q&As - AD0-E906 dumps with Correct Answers: https://lead2pass.prep4sureexam.com/AD0-E906-dumps-torrent.html