Answer: A, B and E

The steps are the same ones used for any static resource in an LWC:

B. Upload the SVG as a static resource: In Setup, go to Static Resources and upload the file.
A. Import the static resource and provide a JavaScript property for it: The component’s JavaScript imports it from @salesforce/resourceUrl and exposes it as a property.
E. Reference the property in the HTML template: The template uses the property, for example as an image src.
javascript
import { LightningElement } from 'lwc';
import MY_ICON from '@salesforce/resourceUrl/companyIcon';

export default class IconDisplay extends LightningElement {
iconUrl = MY_ICON; // property exposed to the template
}
html
<template>
<img src={iconUrl} alt="Company icon" />
</template>

The other options don’t fit:

C. Reference the import in the HTML template: A template can’t reference the import directly. It can only bind to a property defined on the component class, which is why A comes before E.
D. Import the SVG as a content asset file: Content assets can be imported with @salesforce/contentAssetUrl, so this is a real way to use files in an LWC. It is a different method from the static resource steps in A, B and E, and the question asks for the three steps of one workflow....

Correct Answer: A,B,E*