The correct answers are: Allow only team leads to view issues that team leads opened and Limit access so that only team leads can view and update urgent issues.

Issue security levels restrict visibility and permissions for individual issues so they are appropriate when you need to limit who can see or update particular issues without changing access for the whole project. This makes issue security well suited to cases where only team leads should view or update specific issues marked urgent or issues opened by team leads.

Prevent team leads from moving issues to other projects is incorrect because moving issues is governed by project and global permissions rather than by issue security levels. Issue security does not stop the Move operation.

Restrict who can view the development panel for an issue is incorrect because the development panel is controlled by application access and integration permissions with developer tools and not by issue security levels. You would adjust app access or integration settings to change that panel visibility.

Hide the entire project from non team leads is incorrect because issue security operates at the issue level and cannot hide an entire project. Project visibility and access are managed through project permissions and project settings.

Full AWS Practitioner Certification Question