The code you show is ASP.Net source which gets compiled on the server, so the HTML in the browser (the HTML your test needs to work with) will be different.
i.e @foreach (var att in Model) gives you a row for each item in Model and @Html.DisplayFor(modelItem => att.2) will be translated into some concrete content for column 2.
Therefore, it would be easier to answer if you run the app in a browser and copy and paste that HTML from the console.
Since you want to search on column 2, that can go two ways.
If the content in column 2 is very unique, e.g names that do not appear in other columns, you can target it just by looking for the text
cy.contains('td', 'text-to-search-for') // gives you the cell
.parent() // gives you the row
.within($tr => { // filters just that row
.get('td a') // finds the buttons cell of that row
.contains('DELETE') // finds the delete button
.click()
OR
cy.contains('td', 'text-to-search-for') // gives you the cell
.siblings() // gives you all the other cells in the row
.contains('a', 'DELETE') // finds the delete button
.click()
If text you want to search for can appear in columns other than column 2, it becomes more difficult, but chances are the above will suffice.
The other thing to note, if your test scenario always uses the same data, e.g from a fixture file, you can target specific row numbers but that's a fragile test which will need re-writing if the structure of the page changes.
Hi Marion Morrison I am really grateful for your help. It works for me.