Professional Practice and Ethics
What this domain tests
Professional Practice and Ethics tests judgment under pressure: competence boundaries, conflicts of interest, confidentiality, data integrity, accurate reporting, intellectual property, and the duty to protect the public. Expect scenario questions where the technically correct answer and the politically convenient answer differ.
Core rules and concepts
- Protect public safety and health above client, employer, or schedule pressure. If you find an unacceptable risk, document it and escalate through the proper channel.
- Practice only within your competence. Bring in a qualified specialist for safety validation, cybersecurity architecture, or regulatory interpretation when needed.
- Disclose conflicts of interest before accepting work or making recommendations. Gifts, vendor hospitality, and side work can all create conflicts.
- Keep client and employer information confidential, but do not use confidentiality to hide a safety or legal violation.
- Record and report data honestly. Never alter, selectively omit, or backdate test results. Negative results are data.
- Respect intellectual property and software licenses. Do not copy code, drawings, or configuration from another project without rights.
- Maintain traceable records: who approved what, when, with what evidence.
Worked example
During FAT, a safety interlock responds in 2.8 s against a 2.0 s requirement. The project manager says, Mark it pass; we will fix it at site. The ethical response is to record the actual result as a deviation, refuse to sign a false pass, and escalate the risk. Proposed path: log the deviation, assess whether the slower response creates an unacceptable risk, require a corrected design and retest before shipment, or obtain a documented, authorized concession with risk acceptance. Reasoning: a false pass transfers an unknown risk to operators and violates the integrity of the test record. Schedule pressure is not a technical justification.
Traps that cost marks
- Treating the client asked me to as an ethical justification.
- Signing off outside your expertise because a manager asked.
- Using confidentiality to avoid reporting a safety defect.
- Accepting gifts or hospitality that could bias a vendor selection.
- Copying licensed software or another project's code.
- Reporting only successful tests and hiding deviations.