Anthropic CCA-F Exam Dumps, Practice Test Questions

Rule metadata validation detects whether conditional settings parse, but it does not establish that the requirement is restricted to test files. A syntactically valid global rule can still incorrectly affect production changes. Scope the instruction to the specified test-file glob.

Excluding generated code is an independent hygiene rule, but the stated boundary is between test files and production source. Generated-file exclusions do not keep a strict test assertion from being applied to maintained application modules outside tests/.

Normalized glob syntax helps conditional rule matching work correctly, yet a correct matcher alone requires the intended content and location. The key design is to place the convention in a path-scoped rule applying to tests/**/*.py and validate examples.

Updating a stale glob would be necessary if tests had moved, but no move is described. The stated problem is unwanted application of test rules to production code. Add a scoped rule with the exact test-tree pattern instead of relying on universal instructions.

Narrowing a rule to API documentation is unrelated to a security policy intended for configuration files; it would miss even more relevant YAML locations.

Adding an extension alternative to a glob rooted in the wrong directory still misses the protected nested configuration files. Both path and suffix must be covered by the effective rule.

A recursive pattern helps match nested directories, but without adding .yml it still excludes files with that actual extension.

Including TypeScript and Python extensions in one formatting rule would apply the TypeScript convention to Python code, which is exactly the mistake being observed. Keep the language-specific instruction limited to matching TypeScript paths, not a wider extension set.

A root rule forced onto all source languages repeats the configuration error. General architecture guidance may belong globally, but TypeScript syntax and formatting tools do not. The language-specific convention needs conditional activation.

Testing one TypeScript file can demonstrate that a rule activates but does not prove it stays inactive for Python files. Include negative path tests and correct the glob itself. The control is a path-restricted rule, not merely a successful positive match.

Adding extensions or directory names is useful when those are missing, but the present issue is depth: a one-level components/* selector does not cover nested subdirectories.

Updating the pattern only for src/components/* leaves deeper directories excluded, even if a test of immediate files succeeds. The fix must actually extend the matched path depth.

A docs-only glob serves documentation policies, not frontend component rules. Narrowing to API documentation would remove coverage from the intended source tree.

Narrowing to API documentation would exclude the requested test directories and could accidentally drop the rule from both sites.

A recursive glob solves depth coverage inside one subtree, but need not include the second distinct test directory unless both explicit path roots are represented.

Normalizing glob syntax prevents matcher bugs, but does not by itself express the desired inclusion of two distinct directories with one policy.

A root CLAUDE.md file loads broad guidance for the project; storing migration-only constraints there repeats the reported scope problem. Frontend and documentation tasks then inherit irrelevant database instructions, consuming attention and causing inconsistent behavior. Move migration conventions into matching conditional rules.

A path-scoped test convention is a valid pattern for test files, but it does not target the migration paths specified in this case. The schema and review requirements for database migrations need their own conditional rule. Define the matching migration glob instead of solving an unrelated test-rule placement issue.

A TypeScript-only rule can apply narrowly to source files but does not necessarily match SQL, migration scripts or database directories. The scenario is about DB migration constraints being loaded everywhere, not a TypeScript coding style problem. Scope rules to actual migration file paths.

Checking metadata and globs is important because a rule placed in .claude/rules is useful only when its path patterns match. Validation alone cannot solve the issue if the substantive rule still resides in root CLAUDE.md. Relocate the migration instruction and then test matching and nonmatching files.

Moving a convention into path-scoped rules can be appropriate, but an incorrectly escaped backslash pattern remains broken even in a different instruction file.

Changing the glob without testing representative matches risks assuming the fix worked. The specific error is path syntax incompatibility, so normalize it and run effective-rule checks.

Adding extensions and directories is useful only after the matcher syntax is correct. A Windows backslash might continue preventing matches regardless of target extension.

Global architecture advice can coexist with narrower path rules, but moving a universal secrets policy into a conditional file rule allows other file types to bypass it.

A TypeScript glob can be appropriate for TypeScript-only formatting, but the rule here protects secrets in *all* files. Reinforcing the same narrow scope perpetuates the gap.

A recursive glob could cover nested TypeScript files, but it still excludes non-TypeScript files carrying secrets. Universal requirements must not depend on that language-specific match.

A targeted configuration test can confirm activation when a path matches, but it does not change the trigger behavior for a broad discussion without file access. The instruction must move into an always-applicable scope if it is required independent of touched files.

Scoping a TypeScript convention is useful for language-specific edits, but the current question concerns guidance expected during a general discussion. Narrowing scope further would make the instruction even less likely to load when no file is touched.

Validating syntax and path matching can prove the conditional rule works as designed, but the team’s expectation is inconsistent with that design. A correctly working scoped rule still need not appear in a path-free conversation. Separate truly global guidance from conditional details.

Generated bundles are downstream outputs, so manually editing them is usually lost on the next build and may diverge from version-controlled source. Widening the style rule aggravates the inappropriate hand-edit instruction.

Test-specific scoping may be worthwhile independently, but it does not prevent the broad existing rule from matching dist/ and demanding edits to generated files.

Extending the match into compiled outputs produces more false work and risks altering artifacts that should come from the build process. The source-focused rule needs narrower applicability, not a larger generated-file scope.

Excluding generated artifacts is a valid way to avoid applying source conventions to build output, but no generated-code confusion is described. The problem is an obsolete path root. Correct the path selector rather than changing generated-file handling.

An unchanged matcher anchored to lib/ cannot apply to packages/core/ even if the new directory is nested elsewhere. Leaving the path unchanged means the rule silently misses moved files. The rule needs an updated location pattern and a real activation test.

Placing a convention in a scoped rule is appropriate, but the question says a scoped rule already exists and its paths are stale. Recreating another rule with the old glob would not load for the new source. Update the existing matcher.

File extension matching controls language-specific applicability and may matter after a migration, but the failure is the directory root being renamed. An extension-only change cannot make a lib/-anchored pattern reach packages/core/. Check the actual relocated paths.