B) Each chassis cluster member requires a unique cluster ID value: This statement is true. Each chassis cluster member must have a unique cluster ID assigned, which is used to identify each device in the cluster.
C) Each chassis cluster member device can host active redundancy groups: This statement is true. Both devices in a chassis cluster can host active redundancy groups, allowing for load balancing and failover capabilities.
The two statements about SRX Series device chassis clusters that are true are that each chassis cluster member requires a unique cluster ID value, and that each chassis cluster member device can host active redundancy groups. A unique cluster ID value is necessary so that all members of the cluster can be identified, and each chassis cluster member device can host active redundancy groups to ensure that the cluster is able to maintain high availability and redundancy. Additionally, it is not necessary for all chassis cluster member devices to be the same model, as long as all devices are running the same version of Junos software.

SRX does not identify the iot device. It streams the metadata to Juniper ATP cloud and Junipe ATP cloud identifies the device.
https://www.juniper.net/documentation/us/en/software/junos/security-iot/topics/topic-map/security- iot-overview.html

Explanation
vSRX is a virtual firewall that provides security and networking services at the perimeter or edge of virtualized environments1. vSRX can be deployed in various cloud environments, such as AWS, Azure, Google Cloud Platform, and VMware2.
AWS is a cloud computing platform that offers a variety of services, such as compute, storage, networking, security, and analytics3. AWS enables customers to deploy vSRX instances in a virtual private cloud (VPC), which is a logically isolated section of the AWS cloud4.
AWS satisfies the requirements for a vSRX deployment as follows:
Globally distributed: AWS has a global infrastructure that spans 25 geographic regions and 81 availability zones3. Customers can deploy vSRX instances in any region or zone that meets their needs and preferences4.
Rapid provisioning: AWS allows customers to launch vSRX instances in minutes using the AWS Marketplace, which is an online store that offers software products and solutions5. Customers can also use automation tools, such as CloudFormation, Terraform, and Ansible, to provision vSRX instances in a consistent and scalable manner.
Scale based on demand: AWS supports horizontal and vertical scaling of vSRX instances based on the changing traffic and performance demands. Customers can use AWS Auto Scaling, which is a service that automatically adjusts the number of vSRX instances, or AWS Elastic Load Balancing, which is a service that distributes the traffic across multiple vSRX instances.
Low CapEx: AWS operates on a pay-as-you-go model, which means that customers only pay for the resources they use, such as the vSRX instance type, the storage volume, the data transfer, and the license. Customers can also benefit from the AWS Free Tier, which offers a limited amount of free resources for 12 months.
References:
1: vSRX Overview | Junos OS | Juniper Networks
2: vSRX Deployment Guide | Junos OS | Juniper Networks
3: What is AWS? - Amazon Web Services
4: Configure an Amazon Virtual Private Cloud for vSRX Virtual Firewall | Junos OS | Juniper Networks
5: Juniper Networks vSRX - Amazon Web Services (AWS)
[6]: Deploying Juniper Security in AWS and Azure Education Services
[7]: Scaling vSRX Virtual Firewall Instances on AWS | Junos OS | Juniper Networks
[8]: Load Balancing vSRX Virtual Firewall Instances on AWS | Junos OS | Juniper Networks
[9]: Juniper Networks vSRX Pricing - Amazon Web Services (AWS)
[10]: AWS Free Tier - Amazon Web Services (AWS)