Question 797 of 1,000
Mobile and Malware ForensicseasyMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is that static analysis examines code without execution, while dynamic analysis executes the sample. This distinction is fundamental because static analysis focuses on the malware’s structure—disassembling its code, extracting strings, and inspecting headers—to understand its intent without ever running the file, whereas dynamic analysis observes the malware’s runtime behavior in a controlled sandbox or debugger, revealing actions like file modifications or network connections that static analysis cannot capture. On the Computer Hacking Forensic Investigator CHFI exam, this question tests your ability to differentiate between these two core forensic methodologies, often appearing as a straightforward concept check; a common trap is confusing static analysis with dynamic by assuming both involve execution, or misidentifying which technique reveals behavioral artifacts. To remember the difference, think of static as “still” and dynamic as “doing”—static reads the blueprint, dynamic watches the building move.

CHFI Mobile and Malware Forensics Practice Question

This CHFI practice question tests your understanding of mobile and malware forensics. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

Which of the following is a key difference between static and dynamic malware analysis?

Question 1easymultiple choice
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Static analysis examines code without execution, dynamic analysis executes the sample

Static malware analysis involves examining the malware's code (e.g., disassembly, strings, headers) without executing it, while dynamic analysis runs the sample in a controlled environment (e.g., sandbox, debugger) to observe its runtime behavior. Option C correctly captures this fundamental distinction: static analysis is code-centric and non-executional, whereas dynamic analysis is behavior-centric and executional.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Static analysis executes the malware, dynamic does not

    Why it's wrong here

    It's the opposite: dynamic executes, static does not.

  • Static analysis requires an internet connection, dynamic does not

    Why it's wrong here

    Neither inherently requires internet; dynamic may simulate network services.

  • Static analysis examines code without execution, dynamic analysis executes the sample

    Why this is correct

    Static involves disassembly and code review; dynamic involves running the malware.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Static analysis is always automated, dynamic is manual

    Why it's wrong here

    Both can be automated or manual.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse the terms 'static' and 'dynamic' by associating 'static' with 'not moving' (incorrectly thinking it means no analysis) or misremembering which one involves execution, leading them to pick Option A.

Detailed technical explanation

How to think about this question

Under the hood, static analysis leverages tools like IDA Pro or Ghidra to parse PE headers (e.g., IMAGE_FILE_HEADER, IMAGE_OPTIONAL_HEADER) and extract import/export tables, while dynamic analysis uses API monitoring (e.g., via Detours or API Monitor) to capture calls like CreateProcess or WriteFile at runtime. A real-world scenario: a zero-day ransomware sample might evade static signature detection by obfuscating strings, but dynamic analysis can reveal its file encryption behavior by monitoring file system activity in a sandboxed VM.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A practitioner preparing for the CHFI exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related CHFI practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free CHFI practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this CHFI question test?

Mobile and Malware Forensics — This question tests Mobile and Malware Forensics — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Static analysis examines code without execution, dynamic analysis executes the sample — Static malware analysis involves examining the malware's code (e.g., disassembly, strings, headers) without executing it, while dynamic analysis runs the sample in a controlled environment (e.g., sandbox, debugger) to observe its runtime behavior. Option C correctly captures this fundamental distinction: static analysis is code-centric and non-executional, whereas dynamic analysis is behavior-centric and executional.

What should I do if I get this CHFI question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 24, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This CHFI practice question is part of Courseiva's free EC-Council certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CHFI exam.