Cisco 200-201 Practice Test 16 - Prepaway
Practice Exams:

Pass Cisco 200-201 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium Bundle
$29.98
$79.99 $109.97

200-201 Premium Bundle


  • Premium File 526 Questions & Answers. Last update: Nov 10, 2026
  • Training Course 21 Lectures
  • Study Guide 965 Pages

Cisco 200-201 Practice Test 16

Question 150

In fictional Pinehurst Finance, the security architecture team is working during an incident investigation following an overnight alert. The investigation concerns: A sensor generates almost no HTTP content alerts after internal traffic moves to encrypted tunnels. Supporting evidence: Packet capture shows only outer encrypted tunnel packets at the collection point. Which paired action and independently measurable verification is most defensible?

  1. For Pinehurst Finance, security architecture team: Action: Add supported redundant authentication capacity and verify application dependency failover. Independent proof: The dashboard stays usable during an approved primary-proxy outage test.
  2. For Pinehurst Finance, security architecture team: Action: Combine permitted endpoint/application logs with flow metadata or approved decryption at authorized points. Independent proof: A simulated malicious application request is correlated to a host event without assuming invisible plaintext.
  3. For Pinehurst Finance, security architecture team: Action: Perform a bounded hypothesis-led hunt combining endpoint, identity and network observations. Independent proof: A documented search confirms or rejects the persistence hypothesis using independent artifacts.
  4. For Pinehurst Finance, security architecture team: Action: Tune the baseline with approved workload context and corroborate anomalies with security events. Independent proof: Scheduled backup activity no longer opens false incidents while injected attack behavior still alerts.

Explanation

Correct Answer

B:

Encryption protects content but also limits payload visibility for out-of-path sensors. The action is to combine permitted endpoint/application logs with flow metadata or approved decryption at authorized points; the independent test is that a simulated malicious application request is correlated to a host event without assuming invisible plaintext.

Incorrect Answers

A:

Action: Add supported redundant authentication capacity and verify application dependency failover. Independent proof: The dashboard stays usable during an approved primary-proxy outage test. It misses the relevant dependency because encryption protects content but also limits payload visibility for out-of-path sensors. Instead verify that a simulated malicious application request is correlated to a host event without assuming invisible plaintext.

C:

The proposed pair addresses Action: Perform a bounded hypothesis-led hunt combining endpoint, identity and network observations. Independent proof: A documented search confirms or rejects the persistence hypothesis using independent artifacts. Here packet capture shows only outer encrypted tunnel packets at the collection point. The bounded response is combine permitted endpoint/application logs with flow metadata or approved decryption at authorized points with proof that a simulated malicious application request is correlated to a host event without assuming invisible plaintext.

D:

The alternative action and test—Action: Tune the baseline with approved workload context and corroborate anomalies with security events. Independent proof: Scheduled backup activity no longer opens false incidents while injected attack behavior still alerts—would measure a different issue. This case requires combine permitted endpoint/application logs with flow metadata or approved decryption at authorized points and confirmation that a simulated malicious application request is correlated to a host event without assuming invisible plaintext.

Question 151

In fictional Horizon Data, the security governance group is working while validating a production security control during a scheduled change. The investigation concerns: SOC events from short-lived containers appear under the host address with no workload owner. Evidence: The host-based collector does not attach container ID, image and orchestrator metadata. Which scoped security response best addresses this situation?

  1. For Horizon Data, security governance group: Enable supported cloud-native flow and workload telemetry and ingest it into the SOC platform.
  2. For Horizon Data, security governance group: Reassess risk using likelihood, business impact, exposure and validated mitigations.
  3. For Horizon Data, security governance group: Enrich detection telemetry with approved workload identifiers and orchestrator context.
  4. For Horizon Data, security governance group: Restrict the report to verified payroll roles and review historic access events.

Explanation

Correct Answer

C:

The host-based collector does not attach container ID, image and orchestrator metadata. Security visibility across ephemeral workloads needs context beyond the underlying host IP. The case-specific correction is to enrich detection telemetry with approved workload identifiers and orchestrator context. Preserve this constraint during the change: Identifiers must be protected from spoofing and reconciled with short workload lifecycles.

Incorrect Answers

A:

Another possible response is to enable supported cloud-native flow and workload telemetry and ingest it into the SOC platform. The case evidence instead shows that the host-based collector does not attach container ID, image and orchestrator metadata. Security visibility across ephemeral workloads needs context beyond the underlying host IP.

B:

Reassess risk using likelihood, business impact, exposure and validated mitigations. This does not address the reported incident: SOC events from short-lived containers appear under the host address with no workload owner. The host-based collector does not attach container ID, image and orchestrator metadata. The case-specific correction is to enrich detection telemetry with approved workload identifiers and orchestrator context.

D:

One alternative would be to restrict the report to verified payroll roles and review historic access events. The observed evidence instead shows that the host-based collector does not attach container ID, image and orchestrator metadata. The more relevant correction is to enrich detection telemetry with approved workload identifiers and orchestrator context.

Question 152

In fictional Horizon Data, the security governance group is working while validating a production security control during a scheduled change. The investigation concerns: SOC events from short-lived containers appear under the host address with no workload owner. Which specific observation most directly establishes the stated issue before remediation?

  1. The relevant observation for Horizon Data is: Cloud routing and packet captures show the workload traffic never crosses the monitored premises interface.
  2. The relevant observation for Horizon Data is: The risk register includes technical severity but omits asset criticality, exposure and compensating controls.
  3. The relevant observation for Horizon Data is: File permissions reveal company-wide read access on the protected report share.
  4. The relevant observation for Horizon Data is: The host-based collector does not attach container ID, image and orchestrator metadata.

Explanation

Correct Answer

D:

The host-based collector does not attach container ID, image and orchestrator metadata. That observation distinguishes the reported incident because security visibility across ephemeral workloads needs context beyond the underlying host IP. The appropriate response is to enrich detection telemetry with approved workload identifiers and orchestrator context.

Incorrect Answers

A:

The relevant observation for Horizon Data is: Cloud routing and packet captures show the workload traffic never crosses the monitored premises interface. It does not account for the observation the host-based collector does not attach container ID, image and orchestrator metadata in the reported situation.

B:

For Horizon Data, another diagnostic finding is: The risk register includes technical severity but omits asset criticality, exposure and compensating controls. This would indicate another failure; here the host-based collector does not attach container ID, image and orchestrator metadata. Security visibility across ephemeral workloads needs context beyond the underlying host IP.

C:

At Horizon Data, a different observation is: File permissions reveal company-wide read access on the protected report share. It concerns another dependency. This incident is distinguished by the host-based collector does not attach container ID, image and orchestrator metadata. Security visibility across ephemeral workloads needs context beyond the underlying host IP.

Question 153

In fictional Horizon Data, the security governance group is working while validating a production security control during a scheduled change. The investigation concerns: SOC events from short-lived containers appear under the host address with no workload owner. Analysts propose: Enrich detection telemetry with approved workload identifiers and orchestrator context. Which independent result would demonstrate successful mitigation?

  1. The acceptance test for Horizon Data would show: A controlled container event is attributed to its current image, pod and owner.
  2. The acceptance test for Horizon Data would show: A controlled cloud workload connection appears with source, destination and timestamp in analysis.
  3. The acceptance test for Horizon Data would show: The revised priority shows a repeatable rationale tied to asset and attack-path evidence.
  4. The acceptance test for Horizon Data would show: An unauthorized test account is denied while authorized payroll reviewers retain expected access.

Explanation

Correct Answer

A:

Verify the change by checking that a controlled container event is attributed to its current image, pod and owner. The original clue was the host-based collector does not attach container ID, image and orchestrator metadata. The test is meaningful because security visibility across ephemeral workloads needs context beyond the underlying host IP.

Incorrect Answers

B:

Even verifying the acceptance test for Horizon Data would show: A controlled cloud workload connection appears with source, destination and timestamp in analysis leaves the reported failure unproven. An acceptance test must show that a controlled container event is attributed to its current image, pod and owner.

C:

The alternative outcome is the acceptance test for Horizon Data would show: The revised priority shows a repeatable rationale tied to asset and attack-path evidence. It may validate a separate setting, but not the required action: enrich detection telemetry with approved workload identifiers and orchestrator context. The required observation is a controlled container event is attributed to its current image, pod and owner.

D:

The acceptance test for Horizon Data would show: An unauthorized test account is denied while authorized payroll reviewers retain expected access. The evidence relevant to this incident is the host-based collector does not attach container ID, image and orchestrator metadata. Confirm the corresponding recovery result: A controlled container event is attributed to its current image, pod and owner.

Question 154

In fictional Horizon Data, the security governance group is working while validating a production security control during a scheduled change. The investigation concerns: SOC events from short-lived containers appear under the host address with no workload owner. The decisive record is: The host-based collector does not attach container ID, image and orchestrator metadata. Which security concept best explains the appropriate engineering decision?

  1. The applicable security reasoning for Horizon Data is: Network sensors have limited visibility outside the traffic path they observe.
  2. The applicable security reasoning for Horizon Data is: Security visibility across ephemeral workloads needs context beyond the underlying host IP.
  3. The applicable security reasoning for Horizon Data is: Vulnerability severity is not the same as organization-specific business risk.
  4. The applicable security reasoning for Horizon Data is: Confidentiality means information is disclosed only to authorized identities.

Explanation

Correct Answer

B:

The underlying rule is that security visibility across ephemeral workloads needs context beyond the underlying host IP. The host-based collector does not attach container ID, image and orchestrator metadata. A suitable correction is to enrich detection telemetry with approved workload identifiers and orchestrator context.

Incorrect Answers

A:

The applicable security reasoning for Horizon Data is: Network sensors have limited visibility outside the traffic path they observe. The decisive observation, the host-based collector does not attach container ID, image and orchestrator metadata, requires a different explanation: Security visibility across ephemeral workloads needs context beyond the underlying host IP.

C:

A different principle is: the applicable security reasoning for Horizon Data is: Vulnerability severity is not the same as organization-specific business risk. The causal link actually supported by the host-based collector does not attach container ID, image and orchestrator metadata is security visibility across ephemeral workloads needs context beyond the underlying host IP.

D:

The applicable security reasoning for Horizon Data is: Confidentiality means information is disclosed only to authorized identities. However, it does not explain the host-based collector does not attach container ID, image and orchestrator metadata. The applicable principle is that security visibility across ephemeral workloads needs context beyond the underlying host IP.

Question 155

In fictional Horizon Data, the security governance group is working while validating a production security control during a scheduled change. The investigation concerns: SOC events from short-lived containers appear under the host address with no workload owner. Supporting evidence: The host-based collector does not attach container ID, image and orchestrator metadata. Which paired action and independently measurable verification is most defensible?

  1. For Horizon Data, security governance group: Action: Enable supported cloud-native flow and workload telemetry and ingest it into the SOC platform. Independent proof: A controlled cloud workload connection appears with source, destination and timestamp in analysis.
  2. For Horizon Data, security governance group: Action: Reassess risk using likelihood, business impact, exposure and validated mitigations. Independent proof: The revised priority shows a repeatable rationale tied to asset and attack-path evidence.
  3. For Horizon Data, security governance group: Action: Enrich detection telemetry with approved workload identifiers and orchestrator context. Independent proof: A controlled container event is attributed to its current image, pod and owner.
  4. For Horizon Data, security governance group: Action: Restrict the report to verified payroll roles and review historic access events. Independent proof: An unauthorized test account is denied while authorized payroll reviewers retain expected access.

Explanation

Correct Answer

C:

The underlying clue is the host-based collector does not attach container ID, image and orchestrator metadata. Correct it by enrich detection telemetry with approved workload identifiers and orchestrator context and confirm that a controlled container event is attributed to its current image, pod and owner.

Incorrect Answers

A:

Action: Enable supported cloud-native flow and workload telemetry and ingest it into the SOC platform. Independent proof: A controlled cloud workload connection appears with source, destination and timestamp in analysis. The pair does not resolve the observed the host-based collector does not attach container ID, image and orchestrator metadata. Use enrich detection telemetry with approved workload identifiers and orchestrator context and verify a controlled container event is attributed to its current image, pod and owner.

B:

The alternate plan combines Action: Reassess risk using likelihood, business impact, exposure and validated mitigations. Independent proof: The revised priority shows a repeatable rationale tied to asset and attack-path evidence. The identified fault is the host-based collector does not attach container ID, image and orchestrator metadata. Closing it requires a controlled container event is attributed to its current image, pod and owner.

D:

The alternative proposal is Action: Restrict the report to verified payroll roles and review historic access events. Independent proof: An unauthorized test account is denied while authorized payroll reviewers retain expected access. It does not address the current evidence: the host-based collector does not attach container ID, image and orchestrator metadata. The appropriate action is enrich detection telemetry with approved workload identifiers and orchestrator context.

Question 156

In fictional Cedarstone Transit, the security architecture team is working during an incident investigation following an overnight alert. The investigation concerns: SOC events from short-lived containers appear under the host address with no workload owner. Evidence: The host-based collector does not attach container ID, image and orchestrator metadata. Which scoped security response best addresses this situation?

  1. For Cedarstone Transit, security architecture team: Enable supported cloud-native flow and workload telemetry and ingest it into the SOC platform.
  2. For Cedarstone Transit, security architecture team: Reassess risk using likelihood, business impact, exposure and validated mitigations.
  3. For Cedarstone Transit, security architecture team: Restrict the report to verified payroll roles and review historic access events.
  4. For Cedarstone Transit, security architecture team: Enrich detection telemetry with approved workload identifiers and orchestrator context.

Explanation

Correct Answer

D:

SOC events from short-lived containers appear under the host address with no workload owner. The clue the host-based collector does not attach container ID, image and orchestrator metadata supports the bounded action: Enrich detection telemetry with approved workload identifiers and orchestrator context. Confirm that a controlled container event is attributed to its current image, pod and owner. Preserve this constraint during the change: Identifiers must be protected from spoofing and reconciled with short workload lifecycles.

Incorrect Answers

A:

Enable supported cloud-native flow and workload telemetry and ingest it into the SOC platform. It could be useful for another problem, but it does not change the host-based collector does not attach container ID, image and orchestrator metadata. The response needs to enrich detection telemetry with approved workload identifiers and orchestrator context.

B:

An alternative action is reassess risk using likelihood, business impact, exposure and validated mitigations. This incident instead involves the host-based collector does not attach container ID, image and orchestrator metadata. Confirm the scoped change through a controlled container event is attributed to its current image, pod and owner.

C:

Restrict the report to verified payroll roles and review historic access events. That would not correct the reported the host-based collector does not attach container ID, image and orchestrator metadata. The supported response is to enrich detection telemetry with approved workload identifiers and orchestrator context.

Question 157

In fictional Cedarstone Transit, the security architecture team is working during an incident investigation following an overnight alert. The investigation concerns: SOC events from short-lived containers appear under the host address with no workload owner. Which specific observation most directly establishes the stated issue before remediation?

  1. The relevant observation for Cedarstone Transit is: The host-based collector does not attach container ID, image and orchestrator metadata.
  2. The relevant observation for Cedarstone Transit is: Cloud routing and packet captures show the workload traffic never crosses the monitored premises interface.
  3. The relevant observation for Cedarstone Transit is: The risk register includes technical severity but omits asset criticality, exposure and compensating controls.
  4. The relevant observation for Cedarstone Transit is: File permissions reveal company-wide read access on the protected report share.

Explanation

Correct Answer

A:

The host-based collector does not attach container ID, image and orchestrator metadata. Security visibility across ephemeral workloads needs context beyond the underlying host IP. This finding supports the targeted response: Enrich detection telemetry with approved workload identifiers and orchestrator context.

Incorrect Answers

B:

The relevant observation for Cedarstone Transit is: Cloud routing and packet captures show the workload traffic never crosses the monitored premises interface. That finding does not isolate the reported issue: SOC events from short-lived containers appear under the host address with no workload owner. The determining evidence is the host-based collector does not attach container ID, image and orchestrator metadata.

C:

For Cedarstone Transit, that alternative describes: The risk register includes technical severity but omits asset criticality, exposure and compensating controls. The actual diagnostic record shows the host-based collector does not attach container ID, image and orchestrator metadata instead. The difference matters because security visibility across ephemeral workloads needs context beyond the underlying host IP.

D:

At Cedarstone Transit, another potential finding is: File permissions reveal company-wide read access on the protected report share. That would not establish the cause here. The host-based collector does not attach container ID, image and orchestrator metadata. The case-specific correction is to enrich detection telemetry with approved workload identifiers and orchestrator context.

Question 158

In fictional Cedarstone Transit, the security architecture team is working during an incident investigation following an overnight alert. The investigation concerns: SOC events from short-lived containers appear under the host address with no workload owner. Analysts propose: Enrich detection telemetry with approved workload identifiers and orchestrator context. Which independent result would demonstrate successful mitigation?

  1. The acceptance test for Cedarstone Transit would show: A controlled cloud workload connection appears with source, destination and timestamp in analysis.
  2. The acceptance test for Cedarstone Transit would show: A controlled container event is attributed to its current image, pod and owner.
  3. The acceptance test for Cedarstone Transit would show: The revised priority shows a repeatable rationale tied to asset and attack-path evidence.
  4. The acceptance test for Cedarstone Transit would show: An unauthorized test account is denied while authorized payroll reviewers retain expected access.

Explanation

Correct Answer

B:

A controlled container event is attributed to its current image, pod and owner. This measures whether the response corrected the host-based collector does not attach container ID, image and orchestrator metadata rather than merely completing a configuration step.

Incorrect Answers

A:

A test that the acceptance test for Cedarstone Transit would show: A controlled cloud workload connection appears with source, destination and timestamp in analysis would not demonstrate closure of this condition. The needed proof is a controlled container event is attributed to its current image, pod and owner.

C:

The acceptance test for Cedarstone Transit would show: The revised priority shows a repeatable rationale tied to asset and attack-path evidence. That does not demonstrate the case-specific success condition: a controlled container event is attributed to its current image, pod and owner. Security visibility across ephemeral workloads needs context beyond the underlying host IP.

D:

The acceptance test for Cedarstone Transit would show: An unauthorized test account is denied while authorized payroll reviewers retain expected access. That result does not test the original problem, identified by the host-based collector does not attach container ID, image and orchestrator metadata. Recovery must show that a controlled container event is attributed to its current image, pod and owner.

Question 159

In fictional Cedarstone Transit, the security architecture team is working during an incident investigation following an overnight alert. The investigation concerns: SOC events from short-lived containers appear under the host address with no workload owner. The decisive record is: The host-based collector does not attach container ID, image and orchestrator metadata. Which security concept best explains the appropriate engineering decision?

  1. The applicable security reasoning for Cedarstone Transit is: Network sensors have limited visibility outside the traffic path they observe.
  2. The applicable security reasoning for Cedarstone Transit is: Vulnerability severity is not the same as organization-specific business risk.
  3. The applicable security reasoning for Cedarstone Transit is: Security visibility across ephemeral workloads needs context beyond the underlying host IP.
  4. The applicable security reasoning for Cedarstone Transit is: Confidentiality means information is disclosed only to authorized identities.

Explanation

Correct Answer

C:

Security visibility across ephemeral workloads needs context beyond the underlying host IP. The reported symptom arises where the host-based collector does not attach container ID, image and orchestrator metadata. Address it through enrich detection telemetry with approved workload identifiers and orchestrator context.

Incorrect Answers

A:

At Cedarstone Transit, another security reasoning is: Network sensors have limited visibility outside the traffic path they observe. The present evidence is the host-based collector does not attach container ID, image and orchestrator metadata, which instead follows from security visibility across ephemeral workloads needs context beyond the underlying host IP.

B:

The applicable security reasoning for Cedarstone Transit is: Vulnerability severity is not the same as organization-specific business risk. This describes another relationship, not the cause of SOC events from short-lived containers appear under the host address with no workload owner. Security visibility across ephemeral workloads needs context beyond the underlying host IP.

D:

At Cedarstone Transit, a different security reasoning is: Confidentiality means information is disclosed only to authorized identities does not account for the host-based collector does not attach container ID, image and orchestrator metadata. This case is governed by security visibility across ephemeral workloads needs context beyond the underlying host IP.

Question 160

In fictional Cedarstone Transit, the security architecture team is working during an incident investigation following an overnight alert. The investigation concerns: SOC events from short-lived containers appear under the host address with no workload owner. Supporting evidence: The host-based collector does not attach container ID, image and orchestrator metadata. Which paired action and independently measurable verification is most defensible?

  1. For Cedarstone Transit, security architecture team: Action: Enable supported cloud-native flow and workload telemetry and ingest it into the SOC platform. Independent proof: A controlled cloud workload connection appears with source, destination and timestamp in analysis.
  2. For Cedarstone Transit, security architecture team: Action: Reassess risk using likelihood, business impact, exposure and validated mitigations. Independent proof: The revised priority shows a repeatable rationale tied to asset and attack-path evidence.
  3. For Cedarstone Transit, security architecture team: Action: Restrict the report to verified payroll roles and review historic access events. Independent proof: An unauthorized test account is denied while authorized payroll reviewers retain expected access.
  4. For Cedarstone Transit, security architecture team: Action: Enrich detection telemetry with approved workload identifiers and orchestrator context. Independent proof: A controlled container event is attributed to its current image, pod and owner.

Explanation

Correct Answer

D:

Enrich detection telemetry with approved workload identifiers and orchestrator context. Validation requires a controlled container event is attributed to its current image, pod and owner rather than relying on a successful configuration save. Security visibility across ephemeral workloads needs context beyond the underlying host IP.

Incorrect Answers

A:

Action: Enable supported cloud-native flow and workload telemetry and ingest it into the SOC platform. Independent proof: A controlled cloud workload connection appears with source, destination and timestamp in analysis. It misses the relevant dependency because security visibility across ephemeral workloads needs context beyond the underlying host IP. Instead verify that a controlled container event is attributed to its current image, pod and owner.

B:

The proposed pair addresses Action: Reassess risk using likelihood, business impact, exposure and validated mitigations. Independent proof: The revised priority shows a repeatable rationale tied to asset and attack-path evidence. Here the host-based collector does not attach container ID, image and orchestrator metadata. The bounded response is enrich detection telemetry with approved workload identifiers and orchestrator context with proof that a controlled container event is attributed to its current image, pod and owner.

C:

The alternative action and test—Action: Restrict the report to verified payroll roles and review historic access events. Independent proof: An unauthorized test account is denied while authorized payroll reviewers retain expected access—would measure a different issue. This case requires enrich detection telemetry with approved workload identifiers and orchestrator context and confirmation that a controlled container event is attributed to its current image, pod and owner.

Understanding Cisco Cybersecurity Operations Fundamentals (CBROPS) (200-201) Practice Tests