[2024年08月05日] 合格させるCisco 500-425試験情報と無料練習テスト
500-425試験問題集PDF更新された問題集にはFast2test試験合格保証付き
質問 # 27
Your organization has defined a set of health rules that accurately represent the business functions of its applications. Which two ways should you help the organization see the current status of health rules and events of the business process? (Choose two.)
- A. Leave the mam applications page open for all to see
- B. Create a report that runs every night and sends out the status.
- C. Set up a policy to send an email or text when a health rule status changes.
- D. Create a dashboard with health and events widgets displayed.
正解：C、D
解説：
Explanation
Health rules are the criteria that AppDynamics uses to evaluate the performance and availability of your applications and their components. Health rules can trigger alerts and actions when the conditions are violated or cleared. Events are the occurrences that AppDynamics records when something significant happens in your monitored environment, such as a health rule violation, a policy execution, a deployment, or a custom event.
According to the Health Rules - AppDynamics, the following two ways can help you see the current status of health rules and events of the business process:
Set up a policy to send an email or text when a health rule status changes: This way, you can get notified in real time when a health rule condition is met or cleared, and take appropriate actions to resolve or prevent issues. You can configure policies to send emails, texts, or other notifications to specific recipients or groups, and include relevant information such as the health rule name, the affected entity, the severity level, and the time range.
Create a dashboard with health and events widgets displayed: This way, you can visualize the health and performance of your applications and their components in a single view, and drill down to the details of each health rule or event. You can create custom dashboards with various widgets that show the health status, the event list, the event summary, the event correlation, and the event timeline of your applications and their components.
Therefore, A (Set up a policy to send an email or text when a health rule status changes) and D (Create a dashboard with health and events widgets displayed) are two ways that can help you see the current status of health rules and events of the business process. References:
Cisco AppDynamics Associate Administrator Certification
Health Rules - AppDynamics
[Policies and Actions - AppDynamics]
[Events - AppDynamics]
[Custom Dashboards - AppDynamics]
質問 # 28
What gives administrators the ability to test and debug policy execution?
- A. Event Simulation Tool
- B. Action and Policy Execution Tool
- C. Alert Simulation Environment
- D. Policy Test Bench
正解：D
解説：
Explanation
The Policy Test Bench gives administrators the ability to test and debug policy execution. It allows you to simulate events and see how the policies and actions respond to them. You can also view the policy execution logs and troubleshoot any issues1 References: 1: Policy Test Bench
質問 # 29
Which two types of standard controller Actions are available to be created? (Choose two.)
- A. Email
- B. Undeploy
- C. Thread Dump
- D. Close Incident
- E. Resolve
正解：A、C
解説：
Explanation
According to the Actions document1, there are four types of standard controller actions that are available to be created: Notification, Diagnostic, Remediation, and JIRA. Each type of action has different subtypes that perform specific tasks. For example, the Notification type includes Email, SMS, and HTTP Request subtypes, while the Diagnostic type includes Thread Dump, Heap Dump, and Diagnostic Session subtypes. Therefore, the correct answer is D and E, as Email and Thread Dump are subtypes of standard controller actions. Resolve, Close Incident, and Undeploy are not standard controller actions, but they may be custom actions that are created by the user or the administrator. References:
Actions
質問 # 30
What minimum details are required to properly configure a database agent from a zip file?
- A. Controller Host Database Agent Name. Account Access Key. Account Name
- B. Database Host Database Port Login Credentials
- C. Database Host Login Credentials
- D. Controller Host Controller Port, Account Access Key. Account Name
正解：D
解説：
Explanation
https://docs.appdynamics.com/display/PRO45X/Install+the+Database+Agent
To properly configure a database agent from a zip file, you need to provide the following minimum details:
Controller Host: This is the hostname or IP address of the machine where the Controller is installed. You need to specify this so that the Database Agent can communicate with the Controller and send the collected data1 Controller Port: This is the port number that the Controller listens on for incoming connections. You need to specify this so that the Database Agent can connect to the Controller using the correct protocol. The default ports are 8090 for HTTP and 8181 for HTTPS for on-premise Controllers, and 80 for HTTP and 443 for HTTPS for SaaS Controllers1 Account Access Key: This is the key that authenticates the Database Agent with the Controller. You need to specify this so that the Database Agent can register itself with the Controller and access the license. You can find the account access key in the Controller UI under Settings > License > Account1 Account Name: This is the name of the account that the Database Agent belongs to. You need to specify this so that the Database Agent can associate itself with the correct application and user permissions. You can find the account name in the Controller UI under Settings > License > Account1 References: 1: Install the Database Agent
質問 # 31
What is the result of starting a Diagnostic Session?
- A. Snapshots are captured at an accelerated rate for all Business Transactions configured
- B. Snapshots are captured at an accelerated rate for the Business Transaction specified
- C. A snapshot is captured for every transaction flowing through the application until the Diagnostic Session is ended
- D. A single snapshot is captured for the next Business Transaction that occurs.
正解：B
解説：
Explanation
According to the Diagnostic Sessions document1, a diagnostic session is a timed session in which AppDynamics captures transaction snapshots for a business transaction at a more frequent interval that you set. In the session, AppDynamics captures full call graphs for the transactions. A diagnostic session can be triggered manually or automatically based on a health rule violation or a threshold of slow or error transactions. A diagnostic session is always associated with a specific business transaction, not all business transactions configured. Therefore, the correct answer is B. References:
Diagnostic Sessions
質問 # 32
Which statement about assigning users to a group is true?
- A. You can list all users in a group that are logged into AppDynamics.
- B. When you assign a user to a group, they can only have the roles assigned to that group
- C. When you add a role to a group, every user in the group is assigned that role
- D. When the user logs in they can log in with the group credentials
正解：C
解説：
Explanation
When you assign users to a group in AppDynamics, you can manage their permissions and access levels more easily. A group is a collection of users who share the same roles and privileges. A role is a set of permissions that define what actions a user can perform on the Controller UI or the Events Service.
According to the System Configuration Guide for Cisco Unified Communications Manager - User Management, the following statement is true about assigning users to a group:
When you add a role to a group, every user in the group is assigned that role: This means that the users in the group inherit the permissions of the role that you add to the group. For example, if you add the Administrator role to a group, then all the users in that group can perform administrative tasks on the Controller UI or the Events Service.
The other statements are false because:
When you assign a user to a group, they can only have the roles assigned to that group: This is not true because a user can belong to multiple groups and have multiple roles. For example, a user can be in both the Administrator and the Operator groups and have the permissions of both roles.
You can list all users in a group that are logged into AppDynamics: This is not true because there is no such feature in AppDynamics that allows you to see thelogin status of the users in a group. You can only see the list of users and groups in the User Management page of the Controller UI or the Events Service.
When the user logs in they can log in with the group credentials: This is not true because a user cannot log in with the group credentials. A user can only log in with their own username and password. The group credentials are not used for authentication, but for authorization.
Therefore, D (When you add a role to a group, every user in the group is assigned that role) is the correct answer. References:
System Configuration Guide for Cisco Unified Communications Manager - User Management Cisco AppDynamics Associate Administrator Certification User Management - AppDynamics
質問 # 33
Which two would be marked as an exception in AppDynamics? (Choose two)
- A. a handled exception after the business transaction terminates
- B. any message that is logged with a severity of Error or Fatal
- C. a custom-configured error method and error message
- D. HTTP errors that do not occur in the context of a Business Transaction
正解：B、C
解説：
Explanation
An exception in AppDynamics is a code-level event that indicates a problem or abnormality in the execution of a business transaction. AppDynamics captures and presents information on exceptions in the monitored environment, and allows you to configure the rules and criteria for detecting and reporting exceptions.
According to the Errors and Exceptions - AppDynamics, the following two types of events would be marked as an exception in AppDynamics:
A custom-configured error method and error message: This is a type of event that you can define as an exception based on a specific method and message that indicate an error condition in your application code. You can configure the error detection rules to mark a business transaction as an error and capture the exception information when such a method and message are encountered. For example, you can configure a rule to mark a business transaction as an error and capture the exception when the method com.example.MyClass.myMethod returns the message Invalid input.
Any message that is logged with a severity of Error or Fatal: This is a type of event that AppDynamics automatically detects as an exception based on the log messages that are generated by your application code. AppDynamics scans the log messages for the keywords Error or Fatal, and marks the business transaction as an error and captures the exception information when such a message is found. For example, AppDynamics will mark a business transaction as an error and capture the exception when the log message contains Error: Null pointer exception.
Therefore, B (a custom-configured error method and error message) and C (any message that is logged with a severity of Error or Fatal) are two types of events that would be marked as an exception in AppDynamics.
References:
Cisco AppDynamics Associate Administrator Certification
Errors and Exceptions - AppDynamics
Error Detection - AppDynamics
質問 # 34
After agents are installed, and application data is flowing through a Java application, a user sees that a remote database has not been discoveredin a known Business Transaction.To determine and configure the exit call to the database where would you go?
- A. Configuration > Instrumentation > Backend Detection > Java
- B. Database Calls > Options > Backend Detection > JDBC
- C. Databases > Configuration > Collectors
- D. Configuration > Java > Backend Detection > JDBC
正解：A
解説：
Explanation
To determine and configure the exit call to the database, you need to go to Configuration > Instrumentation > Backend Detection > Java. An exit call is a call from an application component to an external service or system, such as a database, a web service, a message queue, or a cache. A backend is a logical representation of an external service or system that receives exit calls from an application component. AppDynamics automatically detects and identifies common types of backends, such as JDBC, HTTP, JMS, and so on.
According to the Exit Point Detection Rules - AppDynamics, the following steps are required to determine and configure the exit call to the database:
Go to Configuration > Instrumentation > Backend Detection > Java.
Select the application and the tier that contains the exit call to the database.
Click the Add button to create a new exit point detection rule.
Enter a name and description for the rule.
Select the type of exit call from the drop-down list, such as JDBC, HTTP, JMS, and so on.
Specify the class and method that make the exit call to the database.
Specify the match criteria for the exit call, such as the URL, the query, the host, the port, and so on.
Click Save.
Therefore, C (Configuration > Instrumentation > Backend Detection > Java) is the correct answer.
References:
Exit Point Detection Rules - AppDynamics
Cisco AppDynamics Associate Administrator Certification
Backends - AppDynamics
質問 # 35
A customer needs to understand how establishing standards for naming Applications. Tiers, and Nodes can help them determine the root of a problem when users are working with AppDynamics or receive an alert Which three statements about establishing naming conventions are true? (Choose three.)
- A. Node names must be unique across the entire business application
- B. Nodes that reside on different Tiers and different machines (hosts) can have duplicate Node names.
- C. Application Tier and Node values can be configured in the application agent startup script
- D. Application Tier and Node values can be configured in the controller-info.xml file
- E. Nodes that reside on the same Tier but on different machines (hosts) can have duplicate Node names.
正解：A、C、D
解説：
Explanation
According to the Tiers and Nodes document1, establishing standards for naming applications, tiers, and nodes can help you identify and organize the components of your monitored environment, as well as troubleshoot performance issues and health rule violations. Some of the statements about establishing naming conventions are true:
Application Tier and Node values can be configured in the application agent startup script: This is true for Java agents, as you can pass values to the agent that will be used as the application, tier, and node name for the system. For example, you can use the -Dappdynamics.agent.applicationName,
-Dappdynamics.agent.tierName, and -Dappdynamics.agent.nodeName properties to specify the names in the JVM startup script2.
Node names must be unique across the entire business application: This is true, as node names are used to identify the individual instances of the application components that are monitored by AppDynamics. Having duplicate node names can cause confusion and errors in the data collection and reporting. Therefore, you should use a naming convention that ensures uniqueness and clarity for each node1.
Application Tier and Node values can be configured in the controller-info.xml file: This is true for Java agents, as you can also configure the names in the controller-info.xml file, which is located in the
<agent_home>/conf directory. The controller-info.xml file contains the properties that define the agent identity and connection to the Controller. You can use the <application-name>, <tier-name>, and
<node-name> elements to specify the names in the file2.
Some of the statements about establishing naming conventions are false:
Nodes that reside on different Tiers and different machines (hosts) can have duplicate Node name:
This is false, as node names must be unique across the entire business application, regardless of the tier or the host they belong to. Having duplicate node names can cause confusion and errors in the data collection and reporting. Therefore, you should use a naming convention that ensures uniqueness and clarity for each node1.
Nodes that reside on the same Tier but on different machines (hosts) can have duplicate Node names: This is also false, as node names must be unique across the entire business application, regardless of the tier or the host they belong to. Having duplicate node names can cause confusion and errors in the data collection and reporting. Therefore, you should use a naming convention that ensures uniqueness and clarity for each node1.
References:
Tiers and Nodes
Name Business Applications, Tiers, and Nodes
質問 # 36
What kind of problems are detected with Infrastructure monitoring?(Choose One)
- A. slow method calls
- B. thread pool problems
- C. process level problems
- D. garbage collection problems
- E. blocked threads
正解：C
解説：
Explanation
Infrastructure monitoring is the feature in AppDynamics that allows you to monitor and troubleshoot the health and availability of the servers that host your applications and their components. Infrastructure monitoring includes metrics such as CPU utilization, memory usage, disk I/O, network traffic, and so on. You can use infrastructure monitoring to detect and resolve the problems that affect the performance and reliability of your servers and applications.
According to the Server Visibility - AppDynamics, the following kind of problem is detected with infrastructure monitoring:
Process level problems: These are the problems that occur at the process level of the server, such as high CPU consumption, memory leaks, excessive disk I/O, or network congestion. You can use infrastructure monitoring to identify the processes that are consuming the most resources, and drill down to the details of each process, such as the command line, the environment variables, the open files, the threads, and the sockets. You can also use infrastructure monitoring to correlate the process level problems with the application performance problems, such as slow response time, high error rate, or low throughput.
Therefore, E (process level problems) is the correct answer. References:
Server Visibility - AppDynamics
Cisco AppDynamics Associate Administrator Certification
Server Monitoring - AppDynamics
質問 # 37
After installing the standalone machine agent, how do you enable the agent to start collecting metrics?
- A. The machine agent requires an app agent to collect metrics
- B. The machine agent runs with the monitored application
- C. The machine agent starts collecting metrics as soon as it is installed
- D. The machine agent must be started and running
正解：D
解説：
Explanation
According to the Install the Standalone Machine Agent document1, the machine agent is a standalone Java program that collects performance statistics about your environment. It can be deployed on any machine that hosts application servers, database servers, messaging servers, Web servers, etc. However, the machine agent does not start collecting metrics as soon as it is installed. You need to start the machine agent manually or configure it to run as a service or a daemon. Therefore, the correct answer is D. The machine agent does not require an app agent to collect metrics, nor does it run with the monitored application. These are false statements. References:
Install the Standalone Machine Agent
質問 # 38
Which two methods are used for confirming the agent is communicating property to the controller? (Choose two.)
- A. Check if data is being written to the agent log in /logs
- B. Log in to the Controller Ul > Settings cog icon > AppDynamics Agents In the list look for the agent in the list by machine hostname.
- C. Use Grep for the agent process on the application server using the specific agent version name
- D. Select Application > Tiers and Nodes > Look for the Node.
正解：A、D
解説：
Explanation
To confirm that the agent is communicating properly to the controller, you can use the following methods:
Check if data is being written to the agent log in /logs. This indicates that the agent is able to send metrics and events to the controller. You can also look for any errors or warnings in the log file that might indicate a connection issue1 Select Application > Tiers and Nodes > Look for the Node. This shows you the list of nodes that are registered with the controller and their status. You can see if the node is up or down, the agent version, the last reported time, and the machine name2 References: 1: Troubleshoot Agent Connectivity 2
質問 # 39
Which two reasons would cause an organization to upgrade AppDynamics agents? (Choose two.)
- A. database issues
- B. new features
- C. application upgrade
- D. agent issues
正解：B、D
解説：
Explanation
According to the Upgrade the Java Agent document1, one of the reasons to upgrade AppDynamics agents is to resolve agent issues, such as bugs, performance problems, or compatibility issues withthe Controller or the monitored application. Another reason to upgrade AppDynamics agents is to take advantage of new features, such as enhanced metrics, dashboards, alerts, or integrations, that are introduced in newer agent versions.
Therefore, the correct answer is A and D. Database issues and application upgrade are not directly related to the agent upgrade, unless they affect the agent functionality or compatibility. References:
Upgrade the Java Agent
質問 # 40
A customer wants a dashboard that will show them the number of current database connections on their application in a Timeseries graph, and compare it to past averages for the same time What option would solve this the fastest for the customer?
- A. Create a report that shows the historical data they are looking for
- B. Include baseline data within widgets on the dashboard
- C. Open up the application and change the time range to show the time they want
- D. Create another dashboard and put them side by side.
正解：B
解説：
Explanation
The option that would solve this the fastest for the customer is to include baseline data within widgets on the dashboard. Baseline data is the data that represents the normal or expected behaviorof a metric, based on the historical data collected by the AppDynamics Cognition Engine. By including baseline data within widgets on the dashboard, the customer can easily compare the current value of the metric with the past average value for the same time. For example, if the customer wants to see the number of current database connections on their application in a Timeseries graph, and compare it to the past averages for the same time, they can create a Timeseries graph widget that shows the metric "Database Connections" and enable the option "Show Baseline Data" in the widget settings. This will display the current and the baseline values of the metric in the same graph, and allow the customer to see the trends and deviations over time1.
質問 # 41
Which three Operating Systems can be enabled in the Database Collector's Hardware Monitoring configuration? (Choose three.)
- A. Solaris
- B. HPUX
- C. Windows
- D. OSX
- E. Linux
正解：A、C、E
解説：
Explanation
The Database Collector's Hardware Monitoring configuration allows you to enable the Database Agent to monitor the server hardware in addition to the database. You can choose from the following operating systems:
Linux, Windows, and Solaris1 You need to provide the credentials and the connection details for the server that hosts the database1 References: 1: Configure the Database Agent to Monitor Server Hardware
質問 # 42
What are two situations where the UniqueHostID agent property is recommended to be used? (Choose two.)
- A. when the machine agent is with multiple app agents on the same machine
- B. when the machine agent is with an app agent on different machines
- C. when the machine agent is on multiple machines
- D. when the machine agent is with an app agent on the same machine
正解：A、D
解説：
Explanation
The UniqueHostID agent property is recommended to be used when the machine agent is with multiple app agents on the same machine or when the machine agent is with an app agent on the same machine. This property allows you to specify a unique identifier for the host machine that overrides the default hostname resolution. This helps to avoid conflicts or confusion when multiple agents are running on the same host or when the hostname is not consistent across different agents1 References: 1: How are you able to associate the machine agent with application
質問 # 43
Which two options can be excluded using error configuration? (Choose two.)
- A. JavaScript errors
- B. Uncaught exceptions
- C. HTTP errors
- D. Database error return codes
正解：A、D
解説：
Explanation
Error configuration is a feature in AppDynamics that allows you to exclude certain types of errors and exceptions from being reported on the dashboard. You can use error configuration to filter out noise and focus on the most relevant and actionable issues.
According to the Error Configuration - AppDynamics, the following types of errors and exceptions can be excluded using error configuration:
Database error return codes: These are codes that indicate a problem with the database server, such as
0x80004005 (access denied) or 0x8000005E (access violation). You can exclude these errors from being reported on the dashboard by adding them to the error configuration list.
JavaScript errors: These are errors that occur in the browser due to invalid or malformed JavaScript code, such as syntax errors or reference errors. You can exclude these errors from being reported on the dashboard by adding them to the error configuration list.
Therefore, A (Database error return codes) and C (JavaScript errors) are two options that can be excluded using error configuration. References:
Error Configuration - AppDynamics
Cisco AppDynamics Associate Administrator Certification
[Create and Manage Error and Exception Configurations - AppDynamics]
質問 # 44
On a custom dashboard, which three types of information does a non-administrator user view? (Choose three.)
- A. the company logo
- B. the current weather in Seattle
- C. the number of AppDynamics licenses consumed
- D. the version of the AppDynamics Controller
- E. a Timeseries graph
正解：A、D、E
解説：
Explanation
On a custom dashboard, a non-administrator user can view the following types of information:
The company logo: A custom dashboard can display the company logo in the upper left corner of the dashboard. This can help to brand the dashboard and make it more recognizable for the intended audience. The logo can be configured by the dashboard owner or administrator from the dashboard settings1.
The version of the AppDynamics Controller: A custom dashboard can display the version of the AppDynamics Controller in the upper right corner of the dashboard. This can help to identify the Controller that is hosting the dashboard and the features that are available. The version can be configured by the dashboard owner or administrator from the dashboard settings1.
A Timeseries graph: A custom dashboard can display a Timeseries graph widget that shows the trend of a metric over time. This can help to visualize the performance and behavior of the application, server, or database that is being monitored. A Timeseries graph can be configured by the dashboard owner or administrator from the widget settings2.
A non-administrator user cannot view the following types of information on a custom dashboard:
The current weather in Seattle: A custom dashboard cannot display the current weather in Seattle or any other location, as this is not a metric or data point that is reported by AppDynamics agents or the analytics platform. A custom dashboard can only display the data that is collected and stored by AppDynamics2.
The number of AppDynamics licenses consumed: A custom dashboard cannot display the number of AppDynamics licenses consumed, as this is a Controller-level information that is only accessible by the Controller administrator. A custom dashboard can only display the data that is scoped by the dashboard owner's permissions1 .
https://docs.appdynamics.com/accounts/en/cisco-appdynamics-saas-deployment-user-management/m
質問 # 45
Capacity planning for a regionally partitioned application requires that the administrator monitors the number of users and orgs mapped to a database. How does the administrator meet this requirement?
- A. Write code in a custom action that alerts when a region has reached capacity
- B. Schedule an analytics query to check and report on the result periodically
- C. Watch the size of the database and alert when it grows too much
- D. Use a custom metric for databases and alert when it approaches a specific level
正解：B
解説：
Explanation
Capacity planning is the process of estimating and allocating the resources needed to meet the current and future demands of an application. For a regionally partitioned application, where different users and organizations are assigned to different databases based on their location, capacity planning requires that the administrator monitors the number of users and orgs mapped to each database and ensures that they do not exceed the available resources.
According to the AppDynamics Analytics - AppDynamics, one way to meet this requirement is to schedule an analytics query to check and report on the result periodically. An analytics query is a SQL-like query that allows you to analyze and visualize the data collected by AppDynamics, such as business transactions, logs, metrics, events, and custom data. You can use analytics queries to create dashboards, widgets, reports, and alerts that provide insights into the performance and behavior of your applications and their components.
To schedule an analytics query to check and report on the number of users and orgs mapped to a database, the administrator can follow these steps:
Go to Analytics > Search.
Select the data source that contains the user and org information, such as Business Transactions, Logs, or Custom Data.
Enter the query that counts the number of users and orgs for each database, such as SELECT database, COUNT(DISTINCT user), COUNT(DISTINCT org) FROM data_source GROUP BY database.
Click the Save button and enter a name and description for the query.
Click the Schedule button and select the frequency, time range, and recipients for the query execution and report delivery.
Click Save.
Therefore, A (Schedule an analytics query to check and report on the result periodically) is the correct answer.
References:
AppDynamics Analytics - AppDynamics
Cisco AppDynamics Associate Administrator Certification
Analytics Queries - AppDynamics
質問 # 46
If you clear the "Mark Business Transaction as error" checkbox under Configuration > Instrumentation > Error Detection, which two statements are true? (Choose two)
- A. The transaction does not add to call count metrics.
- B. The transaction does not add to error count metrics.
- C. The transaction is included in Response Time metrics.
- D. The transaction is added to error count metrics
正解：C、D
解説：
Explanation
The Mark Business Transaction as Error checkbox under Configuration > Instrumentation > Error Detection allows you to control whether a business transaction is reported as an error or not. If you clear this checkbox, the business transaction will not be marked as an error and will not affect the error count metrics.
According to the Error Detection: Mark Business Transaction as Error - AppDynamics, the following statements are true when you clear this checkbox:
The transaction is included in Response Time metrics: This means that the transaction will still contribute to the response time metric, which measures the average time it takes for a request to be completed by AppDynamics. However, it will not affect other response time metrics, such as First Response Time or Average Time to First Byte.
The transaction is added to error count metrics: This means that the transaction will still count towards the error count metric, which measures the number of transactions that have failed due to errors.
However, it will not affect other error count metrics, such as Error Rate or Error Percentage.
Therefore, A (The transaction is included in Response Time metrics) and B (The transaction is added to error count metrics) are true. References:
Error Detection: Mark Business Transaction as Error - AppDynamics
Business Transaction - AppDynamics
Error Detection - AppDynamics
質問 # 47
The application agent starts but cannot connect to the controller. Which two things should you check to solve this problem? (Choose two.)
- A. Check if the agent is using the correct application name.
- B. Check if the agent has enough memory to run.
- C. Check that there are licenses available on the controller
- D. Check if the controller is using SSL or not.
正解：C、D
解説：
Explanation
According to the Cisco AppDynamics Associate Administrator Certification document1, one of the topics covered in the exam is "Monitor agent performance and connectivity". To do this, you need to ensure that the application agent can communicate with the controller, which may require SSL configuration if the controller is using SSL2. You also need to check that there are enough licenses available on the controller for the application agent to register and report data3. If the agent is using the wrong application name or does not have enough memory, it may not start at all or may crash, which are different problems from not being able to connect to the controller. References:
Cisco AppDynamics Associate Administrator Certification
Configure SSL for the Controller and the App Server Agent
License Rules and Restrictions
質問 # 48
......
Cisco 500-425 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
| トピック 6 |
|
あなたを合格させるCisco試験には500-425試験問題集：https://jp.fast2test.com/500-425-premium-file.html