サンプル問題 1： What is the hierarchical relationship between a Queue Topic and Topic Group?
A: Topic Group is the parent; Queue Topic is the child.
B: Queue Topics and Topic Groups have no parent-child relationship
C: Queue Topic is the parent; Topic Group is the child.
正解：A
Explanation: In Adobe Workfront, the hierarchical relationship between Queue Topics and Topic Groups is that Topic Group is the parent, and Queue Topic is the child. This means that a Topic Group can contain multiple Queue Topics, but a Queue Topic is always part of a Topic Group. This structure helps organize and categorize different types of requests or issues within Workfront, making it easier to manage and track them. Reference The hierarchy between Queue Topics and Topic Groups is frequently highlighted in Workfront documentation and training materials, reinforcing that Topic Groups serve as the broader category under which specific Queue Topics fall
サンプル問題 2： A project manager needs to share a Custom Form that was created to support their portfolio. What should the project manager understand about this requirement?
A: Sharing is not an editable function with Custom Forms. When a new form is created, it is permanently visible to everyone in the system
B: Sharing is possible for a Custom Form author to limit who can view, share, and edit by person, role, group, team, and company.
C: Sharing is possible, but only at the user object level and only within the same team. These restrictions exist for data security purposes
正解：B
Explanation: In Adobe Workfront, Custom Forms can be shared by their authors with specific permissions. The author of a Custom Form has the ability to control who can view, share, and edit the form. These permissions can be set for individuals, roles, groups, teams, and even across the entire company. This functionality is critical for maintaining control over who can access and modify the forms, ensuring that only authorized users have the appropriate level of access. Reference This information is consistent with the permissions settings outlined in the Workfront documentation and in various training resources provided by Adobe.
サンプル問題 3： A Workfront developer is tasked with building a new custom form to collect project requests. The form will display different sets of options based on different selections, which requires the use of display logic and skip logic in the form. What are two considerations the developer should take into account when building the conditional logic in the form? (Choose two.)
A: When copying an old form with display logic or skip logic, the logic is not copied to the new custom form.
B: When editing objects in bulk, the custom fields display in the Edit objects box. excluding the fields that are skipped or hidden
C: Custom fields not included in a display logic statement show on a custom form by default.
D: Skip logic does not work with a widget or section break in the form
正解：A, D
Explanation: When building a custom form in Adobe Workfront that uses display logic and skip logic, developers need to consider the following: When copying an old form: If you copy an existing custom form that includes display logic or skip logic, these logic settings will not be transferred to the new form. The logic needs to be manually recreated in the new form to ensure it functions as intended. Skip logic limitations: Skip logic does not operate effectively with certain elements like widgets or section breaks within the form. This limitation means that skip logic cannot be applied to control the visibility or behavior of these elements, potentially impacting how the form is structured and functions. Reference These considerations are detailed in advanced reporting and form customization documentation and have been highlighted in various Workfront admin training sessions.
