From Azure Security Center, you enable Azure Container Registry vulnerability scanning of the images in Registry1. You perform the following actions: - Push a Windows image named Image1 to…

Question

Options

• AImage4
• BImage2
• CImage1
• DImage3
• EImage5

• A
  4% (1)
• B
  79% (19)
• C
  8% (2)
• D
  8% (2)

Explanation

Explanation

Azure Container Registry vulnerability scanning only supports Linux-based images - Windows container images are not scanned. This immediately eliminates Image1 (Windows), Image3 (Windows), and Image4 (modified Windows image), making options A, C, and D incorrect.

Among the Linux images, Image2 (original Linux image) and Image5 (modified Linux image derived from Image2) are both eligible for scanning, as every push of a Linux image to the registry triggers a vulnerability scan - both the base image and any modified versions are scanned independently upon being pushed.

Why distractors are wrong:

• A (Image4): Derived from Image1, which is Windows - not scanned
• C (Image1): Windows image - not scanned
• D (Image3): Windows image - not scanned

Memory Tip: Think "Linux = Scanned, Windows = Skipped" - Azure's vulnerability scanning integrates with Qualys, which only supports Linux container images. If you remember that Windows containers are excluded, you can quickly filter out any Windows-based images in the question, leaving only Linux images (Image2 and Image5) as the correct answers.

No community discussion yet for this question.