Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco 300-220 Exam - Topic 5 Question 3 Discussion

Posted by Holley on Apr 01, 2026 at 02:15 AM

Refer to the exhibit.

A company went through several rounds of restructuring and the previous security team has been let go A new engineer joins and rediscovers all the tools that the previous team left behind. One of the tools Is a Bash script related to monitoring AWS accounts for threats What is the purpose of the script?

Suggested Answer: A

The correct answer is Monitoring failed AWS console login attempts. The Bash script shown in the exhibit is clearly designed to parse AWS CloudTrail logs and extract specific authentication-related events.

Breaking down the script behavior from a professional cloud security perspective:

gunzip -c *.json.gz indicates the script is processing compressed CloudTrail log files, which are typically stored in .json.gz format.

jq -c '.Records[]' parses individual CloudTrail records, a common approach when analyzing AWS activity logs.

The filter conditions explicitly check for:

eventSource == 'signin.amazonaws.com'

eventName == 'ConsoleLogin'

responseElements.ConsoleLogin == 'Failure'

These fields are definitive indicators of failed AWS Management Console login attempts. Additionally, the script extracts contextual fields such as:

Event time

Source IP address

Error message

AWS region

Username

MFA usage status

This data is exactly what security teams use to detect credential abuse, password spraying, brute-force attempts, and compromised IAM accounts. Monitoring failed console logins is a foundational cloud threat hunting activity, especially for identifying early stages of account takeover.

Option B is incorrect because the script does not establish AWS CLI sessions or authenticate to accounts. Option C is incorrect because instance errors would involve services like ec2.amazonaws.com and different event names. Option D is incorrect because the script is analyzing---not archiving---records, and it applies filtering logic rather than storage or lifecycle management.

From a threat hunting and cloud security standpoint, this script supports identity-focused detection, which is critical in AWS environments where IAM misuse is one of the most common initial access vectors. It aligns with MITRE ATT&CK -- Credential Access and Initial Access, particularly techniques involving valid account abuse.

In summary, the script's clear purpose is to monitor failed AWS console login attempts, making Option A the correct and professionally validated answer.


Get Premium 300-220 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
12 comments · newest first
GI
Gilma 3 months ago
C makes sense too, monitoring instance errors is important for uptime.
DO
Dottie 3 months ago
I lean towards B, automating connections. It saves time for engineers.
LA
Laurena 3 months ago
I think it's A, monitoring failed login attempts. That's crucial for security.
DI
Dick 3 months ago
I agree with Marisha, failed logins are a big red flag!
JU
Junita 4 months ago
Wait, are we sure it's not about archiving records? That seems important too.
AN
Angella 4 months ago
C sounds right, monitoring instance errors is crucial.
BE
Berry 5 months ago
I think it's more about automating connection to AWS accounts.
MA
Marisha 6 months ago
It's definitely for monitoring failed AWS console login attempts.
EL
Ellsworth 6 months ago
I vaguely recall something about archiving records, but I don't think that's the main purpose of a monitoring script.
IZ
Izetta 6 months ago
Monitoring for AWS instance errors sounds plausible, but I feel like the focus is more on security breaches.
MI
Milly 7 months ago
I remember a practice question about AWS security that mentioned automating connections, but that doesn't seem to fit here.
GL
Glory 7 months ago
I think the script might be related to monitoring failed AWS console login attempts, but I'm not entirely sure.
0/2000 characters

Save Cancel