A developer is given a task to implement a new Page Designer layout component that doesn't accept certain asset components.
How should the developer achieve the above task?

A Digital Developer is working on a multi-site realm. A new site requires a different layout for the account landing page. The business logic and data model remain the same. The existing code is in AccountCoatrol.-s and accountlanding.isul in the app_at storefront cartridge The app_3torefront cartridge contains code for all other business functions. The cartridge path for the new site is currently int_cybersource:
mc_];aypal:app_storefront.
The Developer creates a new cartridge named app_newsire that contains only the accountlanding.isml template for the new site.
Which modification should be made to the new cartridge path?

A developer needs to perform the same additional checks before completing multiple routes in a custom controller, in order to decide whether to render a template or redirect the user to a different page.
According to SFRA best practices, what is the correct approach to improve code reusability in this scenario7

A Storefront is designed so that multiple pages share a common header and footer layout.
Which ISML tag should a developer use on the templates for these pages to avoid code repetition in the most effective way?

A developer wants to add a link to the My Account Page.
What is the correct code to accomplish this?