Explanation
According to the web search results1, the timecard_admin role is the minimum role that is required to assign a time sheet policy to a user. A time sheet policy is a rule that controls the creation and operation of time sheets for resources who log time against work items. The timecard_admin role can create and modify time sheet policies, time sheet groups, and time sheet periods, as well as approve time sheets or submit time cards on behalf of team members. The other options are incorrect because:
A: ppm_admin: The ppm_admin role is a higher-level role that can access all Project and Portfolio Management modules and features, but it is not the minimum role required for assigning a time sheet policy to a user2.
C: it_project_manager: The it_project_manager role can create and manage projects, but not assign time sheet policies to users3.
D: It is not possible to assign a time sheet policy to a user: This is false, as it is possible to assign a time sheet policy to a user by using the Time Sheet Policy field on the User form4.
1: 3 2:
https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/refer
https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/conc
https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/time-card-management/ref

Explanation
According to the ServiceNow documentation1, the it_program_manager role is needed to group related projects and demands. This role can create and manage programs, which are containers for projects and demands that share a common goal or objective. The other options are incorrect because:
B: it_project_manager: The it_project_manager role can create and manage projects, but not group them into programs2.
C: it_demand_manager: The it_demand_manager role can create and manage demands, but not group them into programs3.
D: it_project_user: The it_project_user role can view and edit project tasks, but not create or manage projects, demands, or programs4.
1:
https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-portfolio-managem
https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/conc
https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/conc
https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/project-management/refer

Explanation
According to the Demand Workbench document, the role that can configure the parameters of the demand workbench that is provided with the base system is it_pps_admin. This role grants access to the Project Portfolio Suite application and allows the user to configure the demand workbench settings, such as the axes, the quadrants, the bubble size, and the color. The other options are not correct, as they are not roles that can configure the parameters of the demand workbench. The all roles option is too broad and does not specify a particular role. The business_stakeholder role grants access to the Business Stakeholder Portal and allows the user to view and submit demands. The it_project_manager role grants access to the Project Portfolio Management application and allows the user to create and update projects.

Explanation
According to the RIDAC (Risk, Issue, Decision, Action, and Request Changes) record entries for a project document, the RIDAC workflow can be modified by using the Workflow Editor, which is a graphical tool that allows you to create and edit workflows. The other options are not correct, as they are not recommended features for modifying the RIDAC workflow. The Project Form is used to create and update project records. The Flow Designer is used to automate processes without coding. The Service Catalog is used to order items and services.

Explanation
According to the Category Configuration document, the default table that stores the idea categories that a user can select from when submitting an idea is im_category. This table contains the predefined categories for ideas, such as Business Process, Customer Service, or IT Service. The other options are not correct, as they are not the tables that store the idea categories. The dmn_demand table stores the demand records that are created from the approved ideas. The im_module table stores the idea modules that are used to group ideas by different criteria. The im_idea_core table stores the core fields of the idea records.