The -r file.pcap argument instructs TShark to read packets from the specified capture file, while -Y applies a Wireshark display filter . The expression "http or udp" therefore displays packets recognized as HTTP or packets using UDP.
Traditional HTTP traffic is unencrypted and can be dissected directly as HTTP. HTTPS normally carries HTTP inside TLS encryption and therefore is not displayed merely because the filter specifies http. DNS commonly operates over UDP, particularly for standard queries and responses, so ordinary DNS traffic satisfies the udp portion of the expression. Consequently, B is the best answer in the context of the available choices.
A technical distinction is important: the expression does not mean "HTTP or DNS specifically." The udp portion matches UDP traffic generally, which can include protocols other than DNS. Nevertheless, within the examination scenario, the intended comparison is plaintext HTTP versus encrypted HTTPS together with standard UDP-based DNS.
Wireshark's documentation distinguishes display filters from capture filters, and TShark is the command-line network traffic analyzer within the Wireshark suite. CS0-004 places packet-analysis capabilities within Security Operations.
Study Guide Reference: Security Operations # Packet Analysis # Wireshark/TShark # PCAP Analysis # Display Filters # HTTP, UDP, and DNS.

AI usage policies establish organizational boundaries for how artificial intelligence systems may be selected, accessed, configured, and used. They allow an organization to obtain operational benefits from AI while controlling risks involving confidential information, intellectual property, regulated data, model outputs, external AI services, and inappropriate automation. A strong policy can define approved platforms, prohibited data categories, validation requirements, human oversight, retention rules, acceptable use, and escalation procedures.
Prompt engineering is a technical method for constructing inputs that produce more useful model responses. It can improve output quality but does not establish enterprise-wide safeguards for protecting business objectives or sensitive information. A non-disclosure agreement establishes contractual confidentiality obligations between parties; it cannot govern the full technical and operational use of AI systems. An incident response policy determines how security incidents are managed and escalated, but it is reactive and not designed to establish routine AI governance.
CS0-004 explicitly addresses AI within Security Operations. The objectives identify AI risks including hallucinations, data exposure, model poisoning, and malicious prompts and identify governance considerations including legal or regulatory compliance and AI usage policies . AI use cases include log analysis, artifact comparison, incident investigation, event correlation, and automation.
Study Guide Reference: Security Operations # AI in Security Operations # AI Risks # Governance # AI Usage Policies # Data Protection.

The recurring weekly conference call is intended to manage and facilitate team coordination . The analyst's stated objectives are to understand workflow processes and the capabilities of the engineers participating in the cybersecurity improvement project. Regular coordination meetings provide a structured mechanism for sharing operational updates, clarifying responsibilities, identifying dependencies, communicating blockers, aligning technical activities, and understanding which personnel possess the expertise required for particular tasks.
Nothing in the scenario indicates an incident requiring formal incident-response training. Training would normally involve exercises, tabletop scenarios, simulations, procedures, or instruction designed to build response capability. There is also no vendor involvement, so a vendor information session would not satisfy the stated objective. Likewise, no customer request is identified.
The distinguishing clue is the combination of a cross-functional task force, workflow understanding, skills visibility, and recurring communication . These elements support internal project coordination rather than external communication or formal instruction.
Within CySA+, reporting and communication extends beyond writing final reports. Analysts must communicate effectively with technical teams, coordinate activities with relevant stakeholders, provide appropriate status information, and ensure security work is understood and actionable across organizational functions.
Study Guide Reference: Reporting and Communication # Stakeholder Communication # Team Coordination
# Roles and Responsibilities # Workflow Management # Cross-Functional Collaboration.

The analyst should prioritize tlindy because the activity associated with that account presents the strongest anomaly in the supplied access-log evidence. Web access-log analysis is fundamentally contextual: an analyst compares source information, request behavior, authentication activity, timestamps, response codes, geographic indicators, user-agent characteristics, and established behavioral expectations to determine which entry warrants immediate investigation.
The fact that the organization is explicitly identified as being based in the United States is an important contextual clue. Geographic or behavioral activity inconsistent with the expected operating profile of an account can raise investigative priority, particularly when combined with unusual authentication or web- request characteristics. Importantly, geographic deviation alone does not prove compromise; VPN services, business travel, cloud infrastructure, and remote-working arrangements can produce legitimate anomalies.
The correct SOC action is therefore investigation rather than immediate attribution.
This question tests the analyst's ability to distinguish normal activity from anomalous activity using log context , rather than simply searching for a particular HTTP status code or username. CySA+ expects analysts to correlate multiple data points before establishing whether activity represents an indicator of compromise.
The uploaded examination material identifies tlindy as the account requiring first investigation.
Study Guide Reference: Security Operations # Log Analysis # Web Application Logs # Behavioral Indicators # Anomaly Detection # User and Entity Context.

Reimaging the disk is a recovery activity because it restores the compromised endpoint to a trusted operational state after malicious activity has been identified and contained. Reimaging replaces the affected operating environment with a known-good system image, removing uncertainty about hidden persistence mechanisms, modified system files, unauthorized software, or other residual effects of compromise.
Verification that malicious activity occurred belongs to the detection and analysis stage. Taking the system offline is a containment measure intended to prevent additional propagation, command-and-control communication, or damage. Writing the final report occurs during post-incident documentation and lessons- learned activities rather than operational restoration.
NIST's Recover function focuses on restoring affected assets and operations and verifying that restored systems are suitable for return to normal business use. A clean reimage is particularly appropriate where the integrity of the compromised operating system cannot be reliably established through selective malware removal.
After rebuilding, analysts should verify configuration, patch levels, security controls, credentials, and monitoring before reconnecting the machine to production.
Study Guide Reference: Incident Response and Management # Recovery # Reimaging # Known-Good Baselines # Restoration Validation # Return to Production.