FAQ-000267 - CSS and UI Security / CSS Exception and Justification Processes

For UX issues typically solved with fixed positioning, you can consider these alternatives: 1. **Relative Positioning**: Use relative positioning to ensure components stay within their intended context and avoid overlapping or obstructing other elements. 2. **Secure Component Exposure**: Set the `isExposed` attribute in the meta-xml file to `false` to prevent the component from being accessible outside its namespace, aligning with secure development practices. These approaches help maintain a clean and secure user experience.

The FAQ content is accurate and well-structured, so minimal changes are needed. The answer correctly addresses CSS positioning alternatives and component security practices. The second point about setting `isExposed` to `false` directly relates to the AvoidLmcIsExposedTrue security rule, which flags when Lightning Message Channel components have isExposed set to true. This rule is relevant because the FAQ specifically mentions setting `isExposed` to `false` as a security best practice, which aligns with what this security rule enforces - avoiding exposure of components outside their intended namespace for security reasons. The FAQ's recommendation to use `isExposed="false"` is exactly what this security rule promotes.