ANALYTICS-ARCH-201 practice question 1 of 30

What is the best practice for setting up a log analysis strategy for a large Tableau Server deployment to ensure optimal performance?

Full set: 200 questions
Answer options
A: Implement a strategy where logs are only analyzed in response to user-reported issues to prioritize critical problems
B: Set up automated log aggregation and analysis using tools that can handle large volumes of data, with alerts for anomalies Correct answer
C: Analyze logs only during scheduled maintenance periods to avoid impacting server performance
D: Delegate log analysis tasks to different team members based on server components, such as data sources or visualizations
Correct Answer:
B. Set up automated log aggregation and analysis using tools that can handle large volumes of data, with alerts for anomalies
Explanation

For a large-scale Tableau Server deployment, a proactive and automated approach to log analysis is critical for maintaining optimal performance. Such deployments generate vast quantities of log data across multiple nodes and processes. Option B describes the best practice: using specialized tools (e.g., ELK Stack, Splunk, or Tableau's Resource Monitoring Tool) to aggregate logs centrally and analyze them automatically. This strategy enables the system to detect anomalies, performance bottlenecks, and potential failures in near real-time. Setting up alerts ensures that administrators are notified proactively, allowing them to address issues before they escalate and impact the user community, thereby ensuring high availability and performance.

Why Incorrect

A. A reactive strategy that waits for user reports is inefficient for large deployments. By the time users report an issue, performance has already degraded, and the problem may be widespread.
C. Limiting log analysis to maintenance windows means performance issues can go undetected for long periods, directly contradicting the goal of ensuring continuous optimal performance.
D. While delegating tasks is a valid organizational practice, it is not a technical strategy for log analysis. It does not address the core requirements of aggregation, automation, and proactive alerting.

References

1. Official Vendor Documentation: Tableau Server Management Add-on documentation describes the Resource Monitoring Tool

which embodies the principles of option B. It states

"The Resource Monitoring Tool provides a comprehensive look at the health of Tableau Server... by parsing and analyzing the logs... to provide insights into performance." This tool is specifically designed for large deployments to enable proactive monitoring and alerting.

Source: Tableau Help

"Tableau Resource Monitoring Tool

" Introduction section.

2. Official Vendor Documentation: Tableau's guidance on monitoring performance emphasizes a continuous approach. The documentation outlines methods for collecting and analyzing performance data

which

for a large environment

necessitates automation to be effective. The goal is to "understand performance bottlenecks" and "tune server performance

" which is best achieved through constant

automated analysis rather than periodic or reactive checks.

Source: Tableau Help

"Monitor Server Performance

" Overview section.

3. Peer-Reviewed Academic Publication: Research in large-scale system administration confirms that automated log analysis is superior to manual methods for maintaining system health. Automated systems can process massive data volumes and use algorithms to detect anomalies that a human analyst would miss. This proactive approach is essential for the reliability of complex enterprise systems like a large Tableau deployment.

Source: He

P.

et al. (2017). "A survey on automated log analysis for reliability engineering." ACM Computing Surveys (CSUR)

50(3)

Article 43

Section 1 (Introduction). DOI: https://doi.org/10.1145/3092468

4. University Courseware: Course materials on distributed systems and cloud computing consistently teach that robust monitoring and logging are fundamental for managing performance and reliability at scale. The principles include centralized log aggregation

automated parsing

and proactive alerting on key metrics and anomalous events

as this is the only feasible way to manage the complexity and data volume of large systems.

Source: MIT OpenCourseWare

6.824 Distributed Systems

Spring 2020

Lecture 2: "Infrastructure: RPCs and Threads

" which discusses the necessity of robust debugging and monitoring infrastructure for scalable systems.

Scroll to Top