MCQs

Disclaimer:

Educational Use Only:

The website links provided are to be used strictly for educational and knowledge-gaining purposes only.

No Misuse:

Do not misuse the links or the information contained therein for any commercial, illegal, or unethical activities.

Respect for Websites and Businesses:

Respect the intellectual property and business interests of the websites and their owners. Do not attempt to alter, copy, or redistribute content without proper authorization.

Acknowledge Value of Knowledge:

Recognize and value the knowledge and resources shared by these websites. Use the information responsibly and ethically.

No Endorsement:

The provision of these links does not imply endorsement of the linked sites, their content, or their products and services. Users are responsible for evaluating the suitability and accuracy of the information.

User Responsibility:

By accessing these links, you agree to use the information at your own risk and to comply with all applicable laws and website terms of use.

1. In cloud computing, what does a “Critical” severity classification indicate?
   a. A minor configuration issue
   b. Easily discoverable vulnerability with direct data or code access potential
   c. Minor inconvenience affecting non-critical systems
   d. Cosmetic UI error
   Answer: b. Easily discoverable vulnerability with direct data or code access potentialcloud.google
2. What severity is assigned to an incident with significant risk to sensitive data and critical infrastructure?
   a. Medium
   b. Low
   c. High
   d. Trivial
   Answer: c. Highaldridge
3. Which severity level is considered the most impactful in incident management frameworks in cloud operations?
   a. Severity 3
   b. Severity 2
   c. Severity 1
   d. Severity 4
   Answer: c. Severity 1atlassian+1
4. Which of the following best describes a “Low” severity finding?
   a. Widespread data loss
   b. Minor incident with low impact, mostly inconvenience
   c. Full system outage
   d. Immediate security breach
   Answer: b. Minor incident with low impact, mostly inconveniencegivainc+1
5. If a database is only accessible internally but can be accessed due to weak passwords, which severity applies?
   a. Critical
   b. Medium
   c. High
   d. Unspecified
   Answer: c. Highcloud.google
6. The most severe cloud security incidents typically result in:
   a. Minor process delays
   b. Widespread damage and severe consequences
   c. Temporary network latency
   d. Increased system logs
   Answer: b. Widespread damage and severe consequencesaldridge
7. Which metric is not usually involved in determining incident severity in cloud environment policy assessments?
   a. Access Complexity
   b. Authentication
   c. UI Preferences
   d. Exploit Level
   Answer: c. UI Preferencesknowledgebase.paloaltonetworks
8. What does SEV 2 typically represent in cloud incident frameworks?
   a. Aesthetic bug
   b. A major incident with significant impact, but not system-wide
   c. Complete system loss
   d. Minor delayed response
   Answer: b. A major incident with significant impact, but not system-wideatlassian+1
9. A configuration error preventing security findings generation is classified as:
   a. Critical
   b. Medium
   c. Low
   d. Unknown
   Answer: a. Criticalcloud.google
10. In severity models, what does a lower numerical value indicate?
    a. Higher severity and impact
    b. Lower priority
    c. Lower risk
    d. Non-applicable
    Answer: a. Higher severity and impactgivainc+1
11. If incident severity is based on attack exposure scores and high-value resources are involved, what may happen?
    a. Severity level decreases
    b. Severity level increases
    c. Severity becomes “Unspecified”
    d. Severity is removed
    Answer: b. Severity level increasescloud.google
12. What incident type would a minor system glitch with little impact be categorized as?
    a. SEV 1
    b. SEV 2
    c. SEV 3
    d. SEV 0
    Answer: c. SEV 3atlassian+1
13. Which aspect does not directly influence severity categorization in cloud policies?
    a. Likelihood of attack
    b. Collateral Damage Potential
    c. Screen Color
    d. Impact on Confidentiality
    Answer: c. Screen Colorknowledgebase.paloaltonetworks
14. What is a typical consequence of a critical level incident in cloud computing?
    a. Minor performance hiccup
    b. Complete loss of access to critical systems
    c. Accidental log deletion
    d. Irrelevant warning
    Answer: b. Complete loss of access to critical systemsaldridge
15. What describes a SEV 1 (Severity 1) incident?
    a. Low impact, minor inconvenience
    b. Major incident with significant impact
    c. Critical incident with very high impact
    d. Cosmetic error
    Answer: c. Critical incident with very high impactzenduty+1
16. How does a “Medium” severity differ from a “High” severity?
    a. Medium is easily discoverable and highly exploitative
    b. Medium has moderate impact; high can lead to significant breaches
    c. Medium is rare, high is common
    d. Medium incidents are always ignored
    Answer: b. Medium has moderate impact; high can lead to significant breachesaldridge+1
17. Which description fits a “Major” severity incident?
    a. System glitch fixed casually
    b. Partial failure of critical service, significant business impact
    c. Unrelated network report
    d. Test-only incident
    Answer: b. Partial failure of critical service, significant business impactgrafana+1
18. What severity level is generally assigned to a cosmetic bug in a cloud platform?
    a. Critical
    b. High
    c. Medium
    d. Low
    Answer: d. Lowlaunchableinc
19. Severity classification helps cloud teams to:
    a. Randomly prioritize
    b. Assess incident impact and prioritize responses
    c. Ignore incidents
    d. Focus on individual preferences
    Answer: b. Assess incident impact and prioritize responsescloud.google
20. Which is a key attribute for determining cloud incident severity according to Prisma Cloud?
    a. Access Vector
    b. Application Language
    c. Graphic Resolution
    d. User Preference
    Answer: a. Access Vectorknowledgebase.paloaltonetworks
21. In cloud security, what would be an example of a “Critical” incident?
    a. Public SSH access with no password
    b. Minor visual bug
    c. Intermittent log error
    d. Outdated browser warning
    Answer: a. Public SSH access with no passwordcloud.google
22. What is the primary purpose for clearly defining severity levels in cloud incident management?
    a. Increase cost
    b. Standardize response and triage
    c. Confuse teams
    d. Generate unnecessary alerts
    Answer: b. Standardize response and triagecloud.google+1
23. Which level represents “Unspecified severity”?
    a. No impact, default placeholder
    b. Maximum threat
    c. Known outcome
    d. Documented issue
    Answer: a. No impact, default placeholdercloud.google
24. According to best practices, what comes after defining severity levels in incident management?
    a. Ignore priority
    b. Assign incident priorities based on severity
    c. Skip metrics
    d. Eliminate logging
    Answer: b. Assign incident priorities based on severitygivainc
25. What is not a recommended use of severity categories in cloud computing?
    a. Explaining urgency of issues
    b. Setting business impact scales
    c. Maximizing confusion
    d. Organizing triage
    Answer: c. Maximizing confusionatlassian+1
26. What is the impact of a SEV 2 incident as per Atlassian’s guidelines?
    a. No user sees any effect
    b. Major for a subset or a vital function disabled
    c. Random log errors
    d. Requires no response
    Answer: b. Major for a subset or a vital function disabledatlassian
27. What is a defining characteristic of a “High” severity cloud incident?
    a. Direct data breach is possible
    b. Only test systems affected
    c. Notification only, no risk
    d. Lowest possible priority
    Answer: a. Direct data breach is possiblealdridge+1
28. What role does “Exploitability” play in policy severity assessment?
    a. Central in classifying severity
    b. Not considered
    c. Only affects numeric values
    d. Used for priorities, not severity
    Answer: a. Central in classifying severityknowledgebase.paloaltonetworks
29. Which severity level would a ransomware attack typically receive?
    a. Low
    b. High
    c. Medium
    d. Unspecified
    Answer: b. Highaldridge
30. What does assigning a “Minor” incident severity signify?
    a. Critical outage
    b. Limited impact, possibly user inconvenience
    c. Fundamental breach
    d. Immediate executive escalation
    Answer: b. Limited impact, possibly user inconveniencegivainc+1
31. Besides impact, what other dimension helps define severity levels according to industry frameworks?
    a. Urgency
    b. Color coding
    c. Documentation length
    d. Number of on-call staff
    Answer: a. Urgencyxmatters+1
32. The severity level of a security alert in Microsoft Defender for Cloud is assigned based on:
    a. Specific trigger and likely impact
    b. UI configuration
    c. Previous alert actions
    d. Network color scheme
    Answer: a. Specific trigger and likely impactlearn.microsoft
33. What best describes a SEV 3 incident?
    a. Complete outage
    b. Major breach
    c. Minor inconvenience
    d. Financial disaster
    Answer: c. Minor inconveniencezenduty+1
34. What should teams do with the “Other” classification after a period of incident reviews?
    a. Eliminate by better specifying its contents
    b. Increase its usage
    c. Ignore incidents
    d. Assign all issues to “Other”
    Answer: a. Eliminate by better specifying its contentsgivainc
35. In incident management, what does the term “impact-based classification” mean?
    a. Severity levels based on business impact
    b. Random assignment by staff
    c. User surveys
    d. Visual similarity
    Answer: a. Severity levels based on business impactuscloud
36. What describes a “Medium” severity cloud incident?
    a. Easily exploitable and devastating
    b. Modest business/process impact
    c. Always leads to SEV 1 escalation
    d. System-wide failure
    Answer: b. Modest business/process impactcloud.google+1
37. According to standard best practices, what is necessary after classifying severity and setting priorities?
    a. Establishing root cause
    b. Ignoring further follow up
    c. Disbanding response teams
    d. Random checks
    Answer: a. Establishing root causegivainc
38. What kind of incident would likely remain at its original default severity in most cloud tools?
    a. Resolved bugs
    b. Active vulnerabilities with no change in exposure
    c. Features updates
    d. Resolved outages
    Answer: b. Active vulnerabilities with no change in exposurecloud.google
39. What is the usual numerical ordering for cloud incident severities?
    a. Highest number = most severe
    b. Lowest number = most severe
    c. Alphabetical by description
    d. Random based on time
    Answer: b. Lowest number = most severezenduty+2
40. What important metric is often tracked to determine the efficacy of incident response to various severity levels?
    a. Response time
    b. System font
    c. Documentation style
    d. Window size
    Answer: a. Response timegivainc
41. When should SEV 1 and 2 incidents be addressed, as per industry guidelines?
    a. During regular business hours only
    b. Only on weekends
    c. Immediately, regardless of time
    d. When convenient
    Answer: c. Immediately, regardless of timeatlassian
42. In what cases could the severity of a cloud vulnerability change over time?
    a. If attack exposure score changes
    b. When code is properly commented
    c. Only if assigned by an intern
    d. Randomly after logging
    Answer: a. If attack exposure score changescloud.google
43. What is the function of well-defined severity levels in cloud operations?
    a. Enable rapid response
    b. Make reports longer
    c. Confuse teams
    d. Shift focus
    Answer: a. Enable rapid responsegivainc
44. Which incident would NOT likely be classified as “Critical”?
    a. Complete infrastructure failure
    b. UI typo
    c. Widespread patient data breach
    d. Exploited zero-day vulnerability
    Answer: b. UI typoaldridge
45. Who benefits the most from clear severity categorization?
    a. Sales department
    b. Incident management and triage teams
    c. Only executives
    d. Marketing
    Answer: b. Incident management and triage teamscloud.google+1
46. What could indicate the need to adjust an organization’s severity classification schema?
    a. Repeated “Other” incidents
    b. Sufficient specificity for all issues
    c. Increasing system uptime
    d. More test cases
    Answer: a. Repeated “Other” incidentsgivainc
47. What is likely to occur if severity levels are poorly defined?
    a. Delays in resolution
    b. Faster incident triage
    c. Reduced business impact
    d. Automated resolution
    Answer: a. Delays in resolutiongivainc
48. In which scenario is “Medium” severity downgraded to “Low”?
    a. Never, always remains medium
    b. If attack exposure score decreases accordingly
    c. Only for outages
    d. If test environments only are involved
    Answer: b. If attack exposure score decreases accordinglycloud.google
49. What is a main goal of adjusting severity classification schemes frequently?
    a. Improvement and accuracy in incident response
    b. Status quo maintenance
    c. Reduce updates
    d. Limit investigation
    Answer: a. Improvement and accuracy in incident responsegivainc
50. Which of these is an incorrect use of severity classification in cloud computing?
    a. Organizing and triaging incidents for rapid recovery
    b. Consistently identifying business risks
    c. Assigning incident levels to random non-IT issues
    d. Establishing clear alerting
    Answer: c. Assigning incident levels to random non-IT issuescloud.google+1

1. https://cloud.google.com/security-command-center/docs/finding-severity-classifications
2. https://aldridge.com/understanding-the-different-severity-levels/
3. https://www.atlassian.com/incident-management/kpis/severity-levels
4. https://www.givainc.com/blog/incident-classification/
5. https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000scJiCAI&lang=en_US
6. https://zenduty.com/blog/incident-severity-levels/
7. https://grafana.com/docs/grafana-cloud/alerting-and-irm/irm/configure/incident-settings/severity-levels/
8. https://www.launchableinc.com/blog/bug-severity-levels-from-high-impact-to-minor-annoyances/
9. https://cloud.google.com/blog/products/devops-sre/devops-best-practices-add-severity-levels-to-alerts
10. https://www.atlassian.com/incident-management
11. https://www.xmatters.com/blog/a-guide-to-incident-severity-levels
12. https://learn.microsoft.com/en-us/azure/defender-for-cloud/alerts-overview
13. https://www.uscloud.com/microsoft-support-glossary/severity-levels/
14. https://www.splunk.com/en_us/blog/learn/incident-severity-levels.html
15. https://www.xmatters.com/blog/best-practices-for-managing-incidents-at-varying-severity-levels
16. https://www.geeksforgeeks.org/severity-in-testing-vs-priority-in-testing/
17. https://docs.qualys.com/en/vm/latest/knowledgebase/severity_levels.htm
18. https://techdocs.broadcom.com/us/en/symantec-security-software/endpoint-security-and-management/endpoint-security/sescloud/Endpoint-Detection-and-Response/About-Incidents/understanding-the-severity-and-priority-levels-of-incidents.html
19. https://www.cloudpanel.io/blog/server-incident-management-interface/
20. https://docs.oracle.com/en/industries/communications/cloud-native-core/2.0.3/rel_notes/severity-definitions.html