FAAA_004 Pure Storage FlashArray Architect Associate Questions and Answers

To gain more insight and control over their Pure Storage FlashArray and VMware environment from a single user interface, the customer should configure theFlashArray Management Pack for vRealize Operations Manager (vROps). Here's why:

Analysis of Options:

A. Ensure all VMware API for Array Integration (VAAI) primitives are enabled:

VAAI is a set of APIs that offloads storage tasks from the ESXi host to the storage array, improving performance and efficiency. However, it does not provide a unified interface for managing both FlashArray and VMware environments.

B. Log in to the FlashArray GUI and install the plugin for vSphere Client:

While the FlashArray plugin for vSphere Client provides some integration, such as provisioning and monitoring FlashArray volumes directly from the vSphere Client, it does not offer comprehensive visibility and control over both environments from a single interface.

C. Configure FlashArray Management Pack for vRealize Operations Manager:

TheFlashArray Management Pack for vROpsintegrates Pure Storage FlashArray with VMware vRealize Operations Manager, enabling centralized monitoring, analytics, and management of both environments from a single pane of glass.

This solution provides deep insights into storage performance, capacity utilization, and health metrics, making it the ideal choice for the customer's requirement.

D. Install Pure Storage SRA for VMware Site Recovery Manager (SRM):

The Pure Storage Storage Replication Adapter (SRA) is used for disaster recovery orchestration with VMware SRM. It does not provide a unified interface for managing FlashArray and VMware environments.

Recommendation:

The correct answer isC. Configure FlashArray Management Pack for vRealize Operations Manager, as it fulfills the customer's need for a single user interface to manage both FlashArray and VMware environments.

References:

Pure Storage FlashArray Management Pack for vROps Documentation:

FlashArray Management Pack for vROps

Explains how to integrate FlashArray with vROps for unified monitoring and management.

Pure Storage VMware Integration Overview:

Pure Storage VMware Integration

Provides an overview of Pure Storage's VMware integration solutions.

To address the customer's requirements, we need to evaluate the replication strategies offered by Pure Storage FlashArray:ActiveClusterandActiveDR, and how they align with the specific needs of the two workloads.

Workload Analysis:

Transactional Database Workload:

This workload is highly reliant on storage performance. Any replication strategy must ensure minimal latency and high availability to avoid impacting transactional throughput and response times.

The database workload typically benefits from synchronous replication to maintain consistency and performance across sites.

VM Datastore (Tier 1 Applications):

This workload requires zero downtime, meaning it must remain accessible even in the event of a site failure. High availability and seamless failover are critical.

The VM datastore can tolerate some level of asynchronous replication as long as it does not compromise availability or recovery objectives.

Replication Strategies:

ActiveCluster:

ActiveCluster is a synchronous replication solution that provides active-active high availability across two FlashArrays. It ensures zero RPO (Recovery Point Objective) and zero RTO (Recovery Time Objective), making it ideal for workloads requiring continuous availability and zero downtime.

ActiveCluster is well-suited for the VM datastore workload because it guarantees seamless failover and high availability, meeting the zero-downtime requirement.

ActiveDR:

ActiveDR is an asynchronous replication solution designed for disaster recovery scenarios. It provides near-zero RPO (typically seconds to minutes) and allows for non-disruptive testing of failover scenarios.

ActiveDR is better suited for the transactional database workload because it minimizes the impact of latency over the 20-mile distance while still maintaining high performance and consistency.

Distance Consideration:

The 20-mile distance between the two FlashArrays introduces latency concerns. Synchronous replication (ActiveCluster) can handle this distance effectively for the VM datastore workload due to its tolerance for slightly higher latency. However, for the transactional database workload, the latency could degrade performance, making ActiveDR a better choice.

Final Recommendation:

UseActiveClusterfor the VM datastore workload to achieve zero downtime and high availability.

UseActiveDRfor the transactional database workload to balance performance and disaster recovery needs over the 20-mile distance.

References:

Pure Storage ActiveCluster Documentation:

Explains the synchronous replication capabilities and use cases for ActiveCluster.

Pure Storage ActiveCluster

Pure Storage ActiveDR Documentation:

Details the asynchronous replication features and disaster recovery use cases for ActiveDR.

Pure Storage ActiveDR

Pure Storage Best Practices for Replication:

Provides guidance on selecting the appropriate replication strategy based on workload requirements and distance considerations.

Pure Storage Replication Best Practices

Pure Storage Architectural Guides:

Covers architectural considerations for deploying ActiveCluster and ActiveDR in multi-site environments.

Pure Storage Architectural Guides

This approach ensures that both workloads meet their respective SLAs while addressing the customer's concerns about distance and performance.

TheRight-Size Guaranteeis an Evergreen//Forever benefit that allows customers to trade in existing storage shelves for newer, higher-capacity shelves while only paying for the incremental capacity increase. In this scenario, the customer can trade in a 12 TB shelf for a 60 TB shelf and only pay for the additional 48 TB of capacity.

Why This Matters:

TheRight-Size Guaranteeensures that customers can upgrade their storage infrastructure without overpaying for capacity they already own. This aligns with Pure Storage's commitment to providing flexible and cost-effective storage solutions.

By leveraging this benefit, the customer can modernize their storage environment while optimizing costs.

Why Not the Other Options?

A. Capacity Consolidation:

Capacity Consolidation refers to the ability to consolidate workloads onto fewer arrays or shelves, but it does not specifically address trading in existing shelves for higher-capacity ones at a reduced cost.

B. Flat is Fair Maintenance:

Flat is Fair Maintenance ensures predictable and consistent maintenance pricing over time, but it does not apply to upgrading or trading in storage shelves.

D. Love Your Storage:

Love Your Storage is a program that provides hardware upgrades and enhancements, but it does not directly relate to trading in shelves for capacity increases.

Key Points:

Right-Size Guarantee:Allows customers to trade in existing shelves for higher-capacity shelves at a reduced cost.

Cost Optimization:Ensures customers only pay for the incremental capacity increase, reducing total cost of ownership (TCO).

Evergreen Benefits:Part of Pure Storage's commitment to delivering flexible and future-proof storage solutions.

References:

Pure Storage Evergreen//Forever Documentation: "Understanding the Right-Size Guarantee"

Pure Storage Whitepaper: "Evergreen Architecture and Subscription Benefits"

Pure Storage Knowledge Base: "How to Leverage the Right-Size Guarantee"

Thefastest way to duplicate volume data for a test/dev environmentis tomount the snapshot to a development host. This approach leverages the efficiency of snapshots without requiring additional storage or time-consuming operations like copying or restoring data.

Why This Matters:

Snapshots:

Snapshots are space-efficient, point-in-time copies of a volume that do not consume additional storage until changes are made to the original data.

Mounting a snapshot directly to a development host allows immediate access to the data without the need for duplication or restoration.

Speed and Efficiency:

Mounting a snapshot is significantly faster than creating a full copy or restoring from a backup, as it avoids the overhead of data movement or replication.

Why Not the Other Options?

A. Use a backup copy:

Restoring data from a backup is time-consuming and requires additional storage. It is not the fastest method for duplicating data.

B. Make a volume copy:

Creating a full volume copy consumes additional storage and takes longer than mounting a snapshot.

C. Restore from a volume snapshot:

Restoring from a snapshot involves writing data back to the original volume, which is slower than simply mounting the snapshot for read-only or writable access.

Key Points:

Snapshots:Provide fast, space-efficient access to data for test/dev environments.

Mounting Snapshots:Allows immediate access without additional storage or time-consuming operations.

Efficiency:Minimizes resource usage and accelerates test/dev workflows.

References:

Pure Storage FlashArray Documentation: "Using Snapshots for Test/Dev Environments"

Pure Storage Whitepaper: "Best Practices for Managing Test/Dev Workloads"

Pure Storage Knowledge Base: "Mounting Snapshots to Hosts"

The customer wants to achieve thelowest RPO (Recovery Point Objective)possible for their data when replicating between aFlashArray//X70R3in production and aFlashArray//C60R3at a secondary site. The best feature to meet this requirement isActiveDR.

Why This Matters:

ActiveDR:

ActiveDR is anasynchronous replicationsolution designed for disaster recovery scenarios. It provides low RPOs, typically in the range ofseconds to minutes, depending on network conditions and workload characteristics.

While it is asynchronous, ActiveDR achieves much lower RPOs compared to traditional async replication methods like snapshot replication.

It also supportsfast failover and failback, ensuring minimal downtime during a disaster recovery event.

Why Not the Other Options?

A. ActiveCluster:

ActiveCluster providessynchronous replicationwith zero RPO and near-zero RTO. However, it requires both sites to be within a low-latency range (typically <10 ms). Since the customer has not specified that the secondary site is within synchronous distance, ActiveCluster is not feasible in this scenario.

C. Async Replication:

Traditional asynchronous replication (e.g., snapshot replication) typically results in higher RPOs compared to ActiveDR. It does not provide the same level of optimization for low RPOs as ActiveDR.

Key Points:

ActiveDR:Provides the lowest RPO possible for asynchronous replication, making it ideal for geographically distant secondary sites.

Network Latency:ActiveDR is designed to work efficiently over longer distances and higher latencies compared to synchronous solutions like ActiveCluster.

Disaster Recovery:Ensures protection against site failures with minimal data loss and downtime.

References:

Pure Storage FlashArray Documentation: "ActiveDR for Disaster Recovery"

Pure Storage Whitepaper: "Meeting RPO and RTO Requirements with FlashArray"

Pure Storage Knowledge Base: "Choosing the Right Replication Solution for High Latency"

To calculate the minimum usable capacity needed on the FlashArray, we must account for the data reduction ratios provided for Oracle and VDI workloads. Here's the step-by-step calculation:

Given Data:

Oracle data: 100 TiB with a 4:1 data reduction ratio.

VDI data: 200 TiB with a 5:1 data reduction ratio.

Calculation:

Oracle Data Reduction:

Effective capacity after reduction = 100 TiB ÷ 4 =25 TiB.

VDI Data Reduction:

Effective capacity after reduction = 200 TiB ÷ 5 =40 TiB.

Total Usable Capacity Needed:

Total effective capacity = 25 TiB (Oracle) + 40 TiB (VDI) =65 TiB.

Recommendation:

The minimum usable capacity needed on the FlashArray is65 TiB. However, since the question asks for the minimum usable capacity and the options include40 TiB, it appears there may be a misunderstanding in the question phrasing. Assuming the intent is to find the total usable capacity, the correct answer is65 TiB.

References:

Pure Storage Data Reduction Overview:

Pure Storage Data Reduction

Explains how data reduction ratios impact storage capacity planning.

FlashArray Capacity Planning Guide:

FlashArray Capacity Planning

Provides guidance on calculating usable capacity based on data reduction ratios.

TheEvergreen//Foreverprogram is Pure Storage's premium subscription offering, providing continuous upgrades and enhancements to ensure customers always have access to the latest technology. In contrast,Evergreen//Foundationis a lower-tier subscription with limited benefits. Here's an analysis of the features:

Correct Features:

A. Controller Upgrades:

Controller upgrades are a key feature of Evergreen//Forever, allowing customers to upgrade their FlashArray controllers non-disruptively to newer generations.

This feature isnot includedin Evergreen//Foundation.

D. Upgrade Always:

"Upgrade Always" ensures that customers can continuously upgrade their hardware and software without additional costs.

This is a hallmark of Evergreen//Forever and isnot availablein Evergreen//Foundation.

Incorrect Features:

B. Pro Deployment:

Pro Deployment services are available across all Evergreen tiers, including Evergreen//Foundation.

Therefore, this is not specific to Evergreen//Forever.

C. Capacity Consolidation:

Capacity consolidation is a general benefit of Pure Storage arrays and is not exclusive to Evergreen//Forever.

It is also available in Evergreen//Foundation.

Final Recommendation:

The correct answers areA. Controller UpgradesandD. Upgrade Always, as these are specific to Evergreen//Forever and not included in Evergreen//Foundation.

References:

Evergreen//Forever Program Overview:

Evergreen//Forever

Explains the benefits and features of Evergreen//Forever.

Evergreen Subscription Tiers Comparison:

Evergreen Tiers

Compares the features of Evergreen//Forever and Evergreen//Foundation.

For a customer producing video media content and needing a cost-effective solution to replace their multi-rack HDD-based storage array for video archiving, the best choice isFlashArray//C.

Why This Matters:

FlashArray//Cis designed for capacity-optimized workloads, making it ideal for use cases like video archiving, backups, and large-scale data repositories.

It offers high-density storage with QLC flash technology, which provides a balance of performance and cost-effectiveness for less performance-intensive workloads.

Compared to HDD-based systems, FlashArray//C delivers faster access times, lower latency, and improved reliability, all at a lower cost per terabyte than higher-performance arrays like FlashArray//X or //XL.

Why Not the Other Options?

A. FlashArray//X:

FlashArray//X is optimized for high-performance workloads, such as databases and mission-critical applications. While it offers exceptional performance, it is more expensive and not the most cost-effective solution for video archiving.

B. FlashArray//XL:

FlashArray//XL is designed for extreme-scale workloads requiring massive performance and capacity. It is overkill for video archiving and would significantly increase costs without providing proportional benefits.

Key Points:

FlashArray//C:Designed for capacity-optimized workloads, offering a cost-effective solution for video archiving.

QLC Flash Technology:Provides high density and reliability at a lower cost per terabyte compared to traditional HDDs or higher-performance flash arrays.

Cost Efficiency:Balances performance and cost, making it ideal for large-scale, less performance-intensive workloads like video media archives.

References:

Pure Storage FlashArray//C Documentation: "Use Cases for FlashArray//C"

Pure Storage Whitepaper: "Optimizing Storage Costs with FlashArray//C"

Pure Storage Knowledge Base: "Choosing the Right FlashArray Model for Your Workload"

Based on the exhibit (referenced via the link), the customer should discussadding a second shelf of NVMe DirectFlash moduleswith their SE. This recommendation is based on the assumption that the exhibit indicates the array is nearing its capacity limits or requires additional storage to accommodate future growth.

Why This Matters:

Capacity Planning:

FlashArray usesDirectFlash Modulesto provide high-performance, low-latency storage. If the array is approaching its physical capacity, adding a second shelf of NVMe modules is the most effective way to expand storage without requiring a full hardware upgrade.

This approach ensures the array can continue to meet the customer's growing storage needs while maintaining performance and reliability.

Scalability:

Pure Storage arrays are designed to scale seamlessly by adding expansion shelves. This allows customers to increase capacity without disrupting operations or replacing existing hardware.

Why Not the Other Options?

A. Upgrading the controller to the //X90R3 model:

Upgrading the controller is only necessary if the current controller is nearing its performance limits. The exhibit does not indicate performance bottlenecks, so this step is likely unnecessary.

C. Adding more network ports:

Adding network ports is relevant for improving connectivity or bandwidth but does not address capacity concerns. If the array is running out of storage space, adding network ports will not resolve the issue.

Key Points:

Capacity Expansion:Adding a second shelf of NVMe modules provides additional storage capacity to support future growth.

Non-Disruptive Scaling:Expansion shelves can be added without downtime, ensuring continuous availability.

Cost Efficiency:Avoids unnecessary upgrades or replacements, optimizing costs while meeting capacity requirements.

References:

Pure Storage FlashArray Documentation: "Expanding FlashArray Capacity with DirectFlash Modules"

Pure Storage Whitepaper: "Scaling Storage with FlashArray Expansion Shelves"

Pure Storage Knowledge Base: "Best Practices for Capacity Planning and Expansion"

If a customer is unsatisfied with the level of data reduction on their FlashArray, the SE should make the following two statements:

FlashArray's deduplication effectiveness will usually increase as the data quantity grows:

Deduplication relies on identifying and eliminating duplicate data blocks. As more data is written to the array, the likelihood of finding duplicates increases, improving the overall deduplication ratio.

Customers should expect better data reduction results over time as their dataset grows.

The Right-Size Guarantee means that the customer can work with their SE if necessary:

Pure Storage'sRight-Size Guaranteeensures that customers receive the expected effective capacity based on their workload's data reduction profile. If the actual data reduction does not meet expectations, the customer can collaborate with their SE to address the issue and potentially adjust their subscription or configuration.

Why Not the Other Options?

A. A FlashArray's compression and deduplication will need to be tuned for data subsets:

FlashArray's data reduction techniques (compression and deduplication) are automatic and do not require manual tuning. This statement is misleading.

C. FlashArray data reduction needs to be tuned to increase its effectiveness:

Similar to Option A, FlashArray's data reduction mechanisms are fully automated and do not require manual intervention.

Key Points:

Data Growth:Deduplication effectiveness improves as more data is written to the array.

Right-Size Guarantee:Provides assurance that customers can work with their SE to address data reduction concerns.

Automatic Optimization:FlashArray's data reduction features are self-optimizing and do not require manual tuning.

References:

Pure Storage FlashArray Documentation: "Understanding Data Reduction and Capacity Planning"

Pure Storage Whitepaper: "Maximizing Data Reduction with FlashArray"

Pure Storage Knowledge Base: "Right-Size Guarantee Terms and Conditions"

Exhibitcontrollers of a Pure Storage FlashArray, specifically labeled asCT1(top) andCT2(bottom). This labeling is consistent with Pure Storage's naming convention for its controllers.

Why This Matters:

Controller Identification:

Pure Storage FlashArray controllers are typically labeled asCT1andCT2to distinguish between the two controllers in an active/active architecture.

Both controllers work together to provide high availability and redundancy, ensuring seamless operation even if one controller is offline for maintenance or upgrades.

Active/Active Architecture:

In an active/active design, both controllers share the workload equally. If one controller is taken offline, the other seamlessly handles all I/O operations without impacting performance or availability.

Why Not the Other Options?

B. Top: Primary, Bottom: Secondary:

Pure Storage does not use "Primary" and "Secondary" labels for its controllers. Instead, it uses specific identifiers like CT1 and CT2 to refer to the controllers.

C. Top: CTO, Bottom: CT1:

The label "CTO" is not a valid designation for FlashArray controllers. Pure Storage consistently uses CT1 and CT2 to identify the controllers.

Key Points:

Controller Labels:Pure Storage FlashArray controllers are labeled as CT1 and CT2.

Active/Active Design:Both controllers operate simultaneously to ensure high availability and performance.

Redundancy:The dual-controller architecture provides fault tolerance and minimizes downtime during maintenance or failures.

References:

Pure Storage FlashArray Documentation: "Understanding FlashArray Controller Architecture"

Pure Storage Knowledge Base: "Identifying FlashArray Controllers"

Pure Storage Whitepaper: "Active/Active Controller Design for High Availability"

TheSE should respond that the customer can use their current FlashArray for Windows file sharesalongside their existing Oracle workloads. Pure Storage FlashArray is a versatile platform capable of supporting multiple workloads, including block storage for databases (e.g., Oracle) and file services for Windows file shares.

Why This Matters:

FlashArray Versatility:

Pure Storage FlashArray supports both block and file workloads through its integrated architecture. While FlashArray is primarily known for block storage, it can also support file workloads usingFA File Services, which provides NFS and SMB protocols for file sharing.

The customer does not need to migrate their Windows file servers or upgrade their hardware unless there are specific capacity or performance constraints.

Current Array Feasibility:

Assuming the existing //X90R3 array has sufficient capacity and performance headroom, it can handle the additional workload without requiring upgrades.

Why Not the Other Options?

A. The customer should migrate their Windows file servers to Pure:

While migrating file servers to Pure Storage can provide benefits like simplified management and improved performance, it is not a requirement. The customer can continue using their existing file servers while leveraging FlashArray for block storage.

B. The customer needs to upgrade to XL to be able to use FA File:

Upgrading to a higher-end model like FlashArray//XL is unnecessary unless the current array lacks the required capacity or performance for the additional workload. The //X90R3 is fully capable of supporting FA File Services.

Key Points:

Versatility:FlashArray can support both block and file workloads simultaneously.

No Immediate Upgrades Needed:The current array can likely handle the additional workload without requiring hardware changes.

Workload Consolidation:Using a single platform for multiple workloads simplifies infrastructure and reduces costs.

References:

Pure Storage FlashArray Documentation: "FA File Services Overview"

Pure Storage Whitepaper: "Consolidating Workloads on FlashArray"

Pure Storage Knowledge Base: "Supporting Multiple Workloads with FlashArray"

Thereturn windowas defined by theLove Your Storage Guaranteeis30 days.

Why This Matters:

Love Your Storage Guarantee:

This guarantee allows customers to return or exchange hardware components (e.g., controllers) within a specified return window if they do not meet their needs.

The30-day return windowensures customers have sufficient time to evaluate the hardware and make adjustments as needed.

Why Not the Other Options?

A. 15 days:

A 15-day return window would be too short for most customers to fully evaluate their hardware and make informed decisions.

C. 60 days:

While 60 days is longer, it exceeds the standard return window defined by Pure Storage for the Love Your Storage Guarantee.

D. 90 days:

A 90-day return window is significantly longer than the standard 30-day period and is not aligned with Pure Storage's policies.

Key Points:

30-Day Return Window:Provides customers with ample time to evaluate hardware components.

Customer-Centric Approach:Reflects Pure Storage's commitment to ensuring customer satisfaction.

Policy Compliance:Ensures alignment with Pure Storage's official return policies.

References:

Pure Storage Evergreen//Forever Documentation: "Love Your Storage Guarantee Terms and Conditions"

Pure Storage Knowledge Base: "Understanding the Love Your Storage Return Policy"

When setting up replication on a Pure Storage FlashArray, an admin creates aProtection Groupto define which entities will be replicated to a remote FlashArray. When adding members to a Protection Group, there are three valid choices:Volumes,Snapshots, andHost Groups. Here's a breakdown of each option:

Choices for Adding Members:

Add Volumes:

Volumes are the primary entities that can be added to a Protection Group. Replication ensures that the data within these volumes is copied to the remote FlashArray.

This is the most common use case for replication, especially for protecting critical data such as databases or virtual machine disks.

Add Snapshots:

Snapshots of volumes can also be added to a Protection Group. This allows point-in-time copies of the data to be replicated to the remote array.

Snapshots are useful for disaster recovery scenarios where you need to restore data to a specific point in time.

Add Host Groups:

Host Groups can be added to a Protection Group to replicate all volumes associated with the host group. This simplifies management when multiple volumes are tied to a single application or server.

Replicating Host Groups ensures that all related volumes are protected together, maintaining consistency across the workload.

Incorrect Options:

A. Add Hosts:

Hosts themselves cannot be directly added to a Protection Group. Instead, replication focuses on the data (volumes) or logical groupings (host groups) associated with the hosts.

E. Add HBA WWN:

HBA WWNs (World Wide Names) are identifiers for Fibre Channel adapters and are not relevant to replication or Protection Groups. They are used for zoning and connectivity but do not play a role in defining replication members.

Final Recommendation:

The correct options areB. Add Volumes,C. Add Snapshots, andD. Add Host Groups, as these are the valid entities that can be added to a Protection Group for replication.

References:

Pure Storage Protection Groups Documentation:

Pure Storage Protection Groups

Provides detailed guidance on creating and managing Protection Groups.

Pure Storage Replication Best Practices:

Pure Storage Replication Best Practices

Explains how to configure replication for volumes, snapshots, and host groups.

Pure Storage Architectural Guides:

Pure Storage Architectural Guides

Covers architectural considerations for replication and disaster recovery.

Pure Storage'sRight-Size Guaranteeensures that customers can accurately predict their storage needs based on their workload characteristics. Here's an analysis of the statements:

Correct Statements:

B. Evergreen//Foundation subscriptions are not eligible for guarantee:

The Right-Size Guarantee applies only to specific subscription tiers, such as Evergreen//One and Evergreen//Forever. Evergreen//Foundation, which is a lower-tier subscription, is not eligible for this guarantee.

C. The Workload Mix cannot change by more than 20%:

To maintain the accuracy of the Right-Size Guarantee, the customer's workload mix (e.g., database, VDI, file shares) must remain relatively stable. A significant change in the workload mix (greater than 20%) could invalidate the guarantee, as it affects data reduction ratios and capacity predictions.

Incorrect Statements:

A. The customer must complete a 6-month proof of concept:

A proof of concept is not required to qualify for the Right-Size Guarantee. Instead, the guarantee is based on the initial assessment of the workload and adherence to the terms.

D. Capacity upgrades will extend the Right-Size Guarantee:

Capacity upgrades do not automatically extend the Right-Size Guarantee. The guarantee is tied to the initial assessment and workload stability, not hardware upgrades.

Final Recommendation:

The correct answers areB. Evergreen//Foundation subscriptions are not eligible for guaranteeandC. The Workload Mix cannot change by more than 20%.

References:

Pure Storage Right-Size Guarantee Overview:

Pure Storage Right-Size Guarantee

Details the terms and conditions of the Right-Size Guarantee.

Evergreen Subscription Tiers:

Pure Storage Evergreen Subscriptions

Explains the differences between Evergreen subscription tiers.