An OffSec-style wireless practice workflow states that when a dictionary is required, only default Kali wordlists may be used. How should the assessor plan?

When an OffSec-style wireless practice workflow states that only default Kali wordlists may be used when a dictionary is required, the assessor should choose techniques and expectations that fit the allowed default lists rather than depending on custom mega-lists. Exam culture and timed labs reward methodology inside constraints. Municipal practice drills that mirror those constraints teach realistic triage.

'Ignore the constraint and import commercial multi-gigabyte lists for every SSID' fails because ignoring the constraint to import commercial multi-gigabyte lists violates the stated workflow rules. 'Skip all PSK testing because default lists never contain any English words' fails because default lists do contain common English and patterned words—skipping all PSK testing is unjustified. 'Replace dictionary work with unauthorized deauthentication against out-of-scope neighbors' fails because replacing dictionary work with unauthorized deauthentication against out-of-scope neighbors is both unethical and out of scope.

Exam caveat: constraints change the expected outcome distribution—they do not authorize cheating or neighbor attacks. Operational check: confirm which lists the civic practice drill allows, stage only those files, set timeboxes, and grade process quality including when to stop. Document compliance with the list rule in the lab worksheet. In municipal wireless operations, record the rationale in the engagement notes so future assessors know which control or technique class was chosen and which failure modes the rejected options would create for city services.