According to the ServiceNow Resource Management document, users with the pps_resource role can be considered for resource planning, as this role grants access to the Resource Management application and allows the users to view and update their resource allocations. The other options are not correct, as they are not roles that are related to resource planning. The it_project_user role grants access to the Project Portfolio Management application and allows the users to create and update projects. The it_user role grants access to the IT Service Management application and allows the users to manage incidents, problems, and changes. The it_pps_user role grants access to the Project Portfolio Suite application and allows the users to manage portfolios, programs, and projects.

If an it_project_manager does not want to equally distribute hours across the resource plan time frame, the allocation spread should be set to Any. This option allows the it_project_manager to manually enter the hours for each month or quarter in the resource plan. The other options (Even, Back Load, and Front Load) automatically distribute the hours evenly, from the end, or from the start of the time frame, respectively. You can find more information about the allocation spread in the Product Documentation for ServiceNow.

According to the ServiceNow documentation1, a rate card is a table that defines the hourly cost of labor for different roles or resources. A project rate is a fixed rate that is applied to all resources assigned to a project, regardless of their roles or individual rates. Both of these can be used to calculate the planned cost of a resource plan by multiplying the hours allocated to each resource by the corresponding rate. The other options are incorrect because:

A. Demand rate: A demand rate is a rate that is applied to a demand, not a resource plan. It is used to estimate the cost of fulfilling a demand before it is converted into a project2.

C. Default rate: A default rate is a rate that is applied to a resource when no other rate is specified. It is not a valid option for calculating the planned cost of a resource plan, as it is only used as a fallback option3.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/resource-management/concept/c_RateCards.html 2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/concept/c_DemandRate.html 3: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/resource-management/concept/c_DefaultRate.html

According to the ServiceNow documentation1, a demand manager can view and edit the following artifacts from a demand:

Decision: A decision that affects the demand or its outcome2.

Risk: A risk that could impact the demand or its outcome3.

Requirement: A requirement that defines the scope or functionality of the demand4.

The other options are not artifacts of a demand, but rather related entities that can be created from a demand or linked to a demand.

1: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/concept/c_DemandManagement.html 2: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/task/t_CreateADecision.html 3: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/task/t_CreateARisk.html 4: https://docs.servicenow.com/bundle/vancouver-it-business-management/page/product/demand-management/task/t_CreateARequirement.html