C1000-200 flashcards

31 cards. Read the term and the definition here. The deck at the top of this page is optional.

Unverified domain weighting

The vendor's public page for this credential does not publish domain percentages, so candidates should weight study by product surface area rather than a claimed official blueprint.

Self-contained item design

Each exam question supplies all information needed to answer, so no exhibit, screenshot, or external document is required; answers follow from stated facts and product behavior.

Three-way task knowledge

For any administrative task, know the graphical interface path, the command-line equivalent, and the configuration object that is actually modified behind the interface.

Release version check

Menu names, command syntax, and defaults change between product releases, so confirm the targeted version before memorizing interface details for the exam.

Least privilege principle

Grant each account only the permissions required for its job; administrative roles should be reserved for the few accounts that genuinely need them.

Supported interface rule

Apply configuration through the supported administrative interface rather than editing underlying files, because direct edits are unsupported and may be overwritten during upgrade.

Tested backup rule

A configuration backup counts as valid only after a restore has been performed successfully; untested backups are an unverified assumption, not a safeguard.

Audit evidence value

Logs and configuration records answer who changed what and when; retaining them supports audits and shortens root-cause analysis during incident review.

Prerequisite verification

Before installation, confirm hardware, operating system, database, and network prerequisites; unmet prerequisites are the leading cause of failed deployments and aborted installs.

Sustained threshold alerting

Alert when a metric breaches a threshold across multiple samples rather than on a single reading, which reduces false positives caused by transient spikes.

Troubleshooting sequence

Confirm the symptom, read logs at the component reporting the error, verify connectivity and credentials, then escalate with collected evidence rather than guessing at remediation.

Upgrade deprecation review

Read release notes for deprecated and removed features before upgrading; removed configuration options can break silently and leave services misconfigured after the upgrade completes.

Capacity trend planning

Plan from growth trends over time, not current utilization alone; a system at sixty percent today may exceed ninety percent within one planning cycle.

Change control discipline

Record each change with its purpose, approver, and rollback plan; undocumented changes make later troubleshooting and audit reconstruction far more difficult.

Connectivity and credential check

When a component cannot reach a dependency, verify network reachability first, then credentials and permissions, before assuming a software defect in the component itself.

Configuration drift

Differences between documented and actual settings accumulate over time; periodic comparison against a known baseline detects drift before it causes an outage.

Role-based access assignment

Assign permissions through roles rather than per-user grants, so access reviews stay manageable and staff changes do not leave orphaned privileges behind.

Restore validation schedule

Perform restore tests on a defined schedule, not only after an incident; a backup whose restore path has never been exercised is unproven when it matters.

Log level adjustment

Raise logging verbosity temporarily when diagnosing an intermittent fault, then return it to the normal level to control storage use and preserve performance.

Stem qualifier reading

Read the whole question before the options; qualifiers such as first, least privilege, or most likely cause determine which technically true option is correct.

Supported procedure preference

When two options are both technically true, choose the documented supported procedure over a workaround, because the exam rewards standard administrative practice.

Workaround elimination

Options requiring unsupported direct edits, disabled security controls, or service restarts as a first diagnostic step are usually wrong and can be eliminated quickly.

Stated-facts-only answering

Answer from information given in the stem; assuming unstated environment details such as cluster size or network topology is a common source of incorrect choices.

First-step preference

When a question asks for the first step, prefer verification and evidence gathering over remediation, since remediation before diagnosis risks masking the actual cause.

Question flagging strategy

Answer confident items first, flag uncertain ones, and return at the end; this protects time for items that reward careful rereading rather than blocking on one hard question.

Average time per item

Budget roughly one minute per question on average, leaving time to revisit flagged items; spending several minutes on one item usually costs more than it gains.

Asker role identification

Identify whether the scenario involves an administrator, auditor, or end user, because the correct action and the responsible party differ by that role.

Distractor pattern recognition

Common distractors swap a correct tool for a related one, reverse a sequence, or overstate a setting's effect; checking each option against the stem exposes these swaps.

Appointment logistics check

Confirm appointment time zone and testing-environment requirements before exam day; arriving late or unprepared for the environment can forfeit the seat.

Negative wording caution

Questions phrased as except or not require selecting the odd option out; misreading negation is a frequent error and warrants a second pass over the stem.

Guessing discipline

If time runs short, answer every item rather than leaving blanks, and prefer options consistent with supported procedure and least privilege when reasoning is incomplete.