# Investment Feed Insights #9

Page: https://stenobird.com/podcast/ensombl-advice-australia-445733/investment-feed-insights-9
Text version: https://stenobird.com/podcast/ensombl-advice-australia-445733/investment-feed-insights-9.md
Podcast: [Ensombl Advice Australia](https://stenobird.com/podcast/ensombl-advice-australia-445733)
Published: 2026-04-15T06:28:00+00:00
Episode link: https://episode.flightcast.com/01KP7X1TPPK6QKXABZR800W5TS.mp3
Audio file: https://episode.flightcast.com/01KP7X1TPPK6QKXABZR800W5TS.mp3
Processing state: not_requested
JSON: https://stenobird.com/v1/public/podcasts/ensombl-advice-australia-445733/episodes/investment-feed-insights-9
Duration seconds: 1124

## Resource

Earn 0.25 CPD here: https://quiz.ensombl.com/CPDC-26041506-25190001 0.25 Technical Competence Neil is joined by Alex Zaika, Chief Executive Officer at Global X Australia, as they discuss how Australian ETF investors responded to recent Middle East–driven volatility, highlighting strong net inflows, sector and regional rotations (including oil, defense, Australian and ex‑US equities), muted gold demand despite turmoil, growing interest in crypto, and the emerging “halo” trade focused on AI-related, low‑obsolescence infrastructure assets. Neil Rogan LinkedIn: https://www.linkedin.com/in/roganneil/ Russell Investments Website: https://russellinvestments.com/ Alex Zaika LinkedIn: https://www.linkedin.com/in/alex-zaika-caia-a1a85612/ Global X Australia Website: https://www.globalxetfs.com.au/ General Disclaimer – https://www.ensombl.com/disclaimer/

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/ensombl-advice-australia-445733/episodes/investment-feed-insights-9/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/ensombl-advice-australia-445733/investment-feed-insights-9.md` — Read the agent-friendly Markdown representation of this episode resource.

A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed.

## Transcript

Full transcripts are not published on public pages unless there is a clear rights basis.