The correct options are Restrict custom Resolution field values in project settings and Restrict a workflow transition to members of a group type custom field.

Team-managed projects use simplified project settings and do not provide project-level controls to restrict Resolution field values. The Resolution field and its allowed values are managed at a broader scope and you cannot configure allowed Resolution values from within a team-managed project.

Team-managed projects also provide simplified workflow capabilities and do not support restricting a transition based on membership in a group-type custom field. Conditions that reference group custom fields for transition restrictions require the more advanced controls found in company-managed projects.

Manage releases and versions from the project features is incorrect because team-managed projects include a Releases feature that lets teams create and manage versions and track releases within the project.

Create cascading select custom fields that depend on another field is incorrect because team-managed projects allow creating custom fields and support dependent or cascading field configurations through the simplified field settings available to the project team.

Set a Timestamp custom field to default to the current time is incorrect because the field configuration in team-managed projects supports default values for date and time fields and you can set a timestamp to default to the current time or to a specified value.

Full AWS Practitioner Certification Question