When you sign up for Zscaler Internet Access - and enable TLS/SSL inspection - you enter into Zscaler's Data Processing Agreement, which governs how customer data (including decrypted TLS traffic) is handled in compliance with privacy laws.

In the Zero Trust Exchange functional services view, Antivirus belongs to the Security Services layer. That layer contains protective inspection capabilities such as antivirus, sandbox, firewall/security inspection, and related threat controls. Option C (Security Services) is correct because Antivirus is a security service, not a platform, access-control, or pure ATP-only category.
Why the other options are incorrect:
A). Platform Services: Platform Services provide shared foundations such as policy, identity, and logging.
Antivirus belongs under the security-services protection layer.
B). Access Control Services: Access Control Services handle access, segmentation, and conditional controls.
Antivirus is a threat inspection capability under Security Services.
D). Advanced Threat Prevention Services: Advanced Threat Prevention is a specific threat capability family. In the functional diagram, Antivirus is grouped more broadly under Security Services.

Option D separates unmanaged BYOD access from higher-trust managed-device access. Zscaler's BYOD and ZTNA guidance supports agentless browser-based access to SaaS and private applications and uses Cloud Browser Isolation to restrict uploads, downloads, printing, and copy-and-paste actions. Zscaler also documents that unmanaged cloud-app sessions can be isolated through a remote browser. This prevents sensitive content from being stored directly on the personal endpoint. Managed devices can use Client Connector posture and identity signals for elevated workflows requiring stronger trust. Treating home Wi-Fi as trusted would weaken controls. Requiring corporate agents and posture enforcement on personal devices conflicts with the unmanaged-device constraint and may create privacy or support problems. URL rules and bandwidth shaping control destinations or throughput but cannot reliably prevent local data persistence.

Tenant Restrictionis the ZIA feature that enforces access control policies to prevent access to certain SaaS applications from unmanaged or non-compliant devices. This ensures that only authorized and managed devices can access sensitive corporate SaaS resources, enhancing security posture.
The study guide highlights Tenant Restriction as an essential control for enforcing device compliance in SaaS access policies.

Zscaler alerting is not limited to email. Alert Rules and detection/response notifications can be sent through webhooks or integrated with collaboration, ITSM, UCaaS, and other third-party tools depending on configuration. Option D (In addition to email, notifications, based on Alert Rules, can be shared with leading ITSM or UCAAS tools over Webhooks) is correct because email and webhook-based integrations support external notification workflows.
Why the other options are incorrect:
A). Email is the only method for notifications as that is universally applicable and no other way of sending them makes sense: Email and webhooks forward alerts to people or third-party systems for response workflows.
B). In addition to email, text messages can be sent directly to one cell phone to alert the CISO who is then coordinating the work on the incident: Email and webhooks forward alerts to people or third-party systems for response workflows.
C). Leading ITSM systems can be connected to the Zero Trust Exchange using a NSS server, which will then connect to ITSM tools and forwards the alert: NSS is for log streaming to analytics/SIEM destinations. Alert-rule notifications use email and webhook integrations, including ITSM or UCaaS tools.